NamespaceReadonly_codeStaticAccessThe ethereum transaction specified an access list, which the network does not support.
StaticAccountAn AccountAmount token transfers list referenced a token type other than FUNGIBLE_COMMON
StaticAccountthe account has been marked as deleted
StaticAccountAn account did not own the NFT to be wiped
StaticAccountThe transaction references an account which has passed its expiration without renewal funds available, and currently remains in the ledger only because of the grace period given to expired entities
StaticAccountAccount is frozen and cannot transact with the token
StaticAccountStaticAccountthe account id passed has not yet been created.
StaticAccountThe account cannot be modified. Account's key is not set
StaticAccountaccount is linked to a node
StaticAccountSpecial Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account
StaticAccountAn attempted operation is invalid because the account is a treasury
StaticAccountKYC must be granted and account does not have KYC granted
StaticAccountsame accounts repeated in the transfer account list
StaticAccountAn account cannot be dissociated from a unique token if it owns NFTs for the token
StaticAccountThe update of the account failed
StaticAirdropToken airdrop transactions can not contain multiple senders for a single token.
StaticAliasAn alias that is assigned to an account or contract cannot be assigned to another account or contract.
StaticAliasThe alias already set on an account cannot be updated using CryptoUpdate transaction.
StaticAmountThe transfer amount exceeds the current approved allowance for the spender account.
StaticAmountThe establishment or adjustment of an approved allowance cause the token allowance to exceed the token maximum supply.
StaticAuthorizationViolating one of these rules: 1) treasury account can update all entities below 0.0.1000, 2) account 0.0.50 can update all entities from 0.0.51 - 0.0.80, 3) Network Function Master Account A/c 0.0.50 - Update all Network Function accounts & perform all the Network Functions listed below, 4) Network Function Accounts: i) A/c 0.0.55 - Update Address Book files (0.0.101/102), ii) A/c 0.0.56 - Update Fee schedule (0.0.111), iii) A/c 0.0.57 - Update Exchange Rate (0.0.112).
StaticAutorenewAn adminKey was not specified on the topic, so there must not be an autoRenewAccount.
StaticAutorenewthe duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION]
StaticBadUnsupported algorithm/encoding used for keys in the transaction
StaticBadbad hook request
StaticBatchThe batch key is set for a non batch transaction
StaticBatchThe list of batch transactions contains duplicated transactions
StaticBatchThe list of batch transactions is empty
StaticBatchRepeated operations count exceeds the limit
StaticBatchThe list of batch transactions contains a transaction type that is in the AtomicBatch blacklist as configured in the network.
StaticBucketThe capacity needed to satisfy all opsPerSec groups in a bucket overflowed a signed 8-byte integral type
StaticBucketA bucket was defined without any throttle groups
StaticBusyIf API is throttled out
StaticCannotThe approveForAll flag cannot be set for a fungible token.
StaticCannotcannot set hooks and approval
StaticCannotThe target of a wipe operation was the token treasury account
StaticConsensusConsensus throttle did not allow execution of this transaction. System is throttled at consensus level.
StaticContractBytecode for smart contract is of length zero
StaticContractContract is marked as deleted
StaticContractFor any contract execution related error not handled by specific error codes listed above.
StaticContractA contract referenced by a transaction is "detached"; that is, expired and lacking any hbar funds for auto-renewal payment---but still within its post-expiry grace period.
StaticContractFile to create a smart contract was of length zero
StaticContractA ContractUpdate requested removal of a contract's auto-renew account, but that contract has no auto-renew account.
StaticContractA selfdestruct or ContractDelete targeted a contract with non-zero token balances.
StaticContractA selfdestruct or ContractDelete targeted a contract that is a token treasury.
StaticContractNegative gas was offered in smart contract call
StaticContractNegative value / initial balance was specified in a smart contract call / create
StaticContractContract REVERT OPCODE executed
StaticContractcontract byte code size is over the limit
StaticContractupdate of the contract failed
StaticCreatingCreating system entities
StaticCurrentThe treasury for a unique token cannot be changed until it owns no NFTs
StaticCustomMore than 20 balance adjustments were to satisfy a CryptoTransfer and its implied custom fee payments
StaticCustomThe reference chain of custom fees for a transferred token exceeded the maximum length of 2
StaticCustomOnly tokens of type FUNGIBLE_COMMON can be used to as fee schedule denominations
StaticCustomOnly positive fees may be assessed at this time
StaticCustomA custom fee schedule entry did not specify either a fixed or fractional fee
StaticCustomA fractional custom fee exceeded the range of a 64-bit signed integer
StaticCustomMore than 10 custom fees were specified
StaticCustomOnly tokens of type FUNGIBLE_COMMON can have fractional fees
StaticCustomOnly tokens of type NON_FUNGIBLE_UNIQUE can have royalty fees
StaticCustomA fee schedule update tried to clear the custom fees from a token whose fee schedule was already empty
StaticDelegatingThe delegating Spender cannot grant approveForAll allowance on a NFT token type for another spender.
StaticDelegatingThe delegating Spender cannot grant allowance on a NFT serial for another spender as it doesnt not have approveForAll granted on token-owner.
StaticDuplicateThe provided max custom fee list contains fees with duplicate account id.
StaticDuplicateThe provided max custom fee list contains fees with duplicate denominations.
StaticDuplicateThis transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period)
StaticEmptyNo allowances have been specified in the approval/adjust transaction.
StaticEmptyempty lambda storage update
StaticEmptythe livehash data is missing
StaticEmptythe livehash body is empty
StaticEmptythe keys for a livehash are missing
StaticEmptythe crypto livehash query is empty
StaticEmptyThe transaction attempted to the use an empty List of PendingAirdropId.
StaticEmptythe query body is empty
StaticEmptyThe transaction attempted to use empty TokenReference list.
StaticEmptyTokenTransfersTransactionBody has a TokenTransferList with no AccountAmounts
StaticEmptyTokenTransfersTransactionBody has no TokenTransferList
StaticEmptyTransaction body provided is empty
StaticEntityEntities with Entity ID below 1000 are not allowed to be deleted
StaticErrorDecoding the smart contract binary to a byte array failed. Check that the input is a valid hex string.
StaticEvmevm hook gas throttled
StaticExchangeThe change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage
StaticExistingAlready existing automatic associations are more than the new maximum automatic associations.
StaticExpirationThe expiration date/time on a smart contract may not be reduced
StaticFailThere was a system error while performing balance checks, reserved for future.
StaticFailThere was a system error while performing fee calculation, reserved for future.
StaticFailThere was a system error and the transaction failed because of invalid request parameters.
StaticFeeThe provided fee exempt key list contains duplicated keys.
StaticFeeFee Schedule Proto File Part uploaded
StaticFeeIf a fee schedule key is not set when we create a topic we cannot add it on update.
StaticFeeIf the topic's custom fees are updated the topic SHOULD have a fee schedule key
StaticFileThe contents of file are provided as empty.
StaticFilethe file has been marked as deleted
StaticFileUnexpected exception thrown by file system functions
StaticFileFee Schedule Proto uploaded but not valid (append or update is required)
StaticFileFee Schedule Proto uploaded but not valid (append or update is required)
StaticFqdnIn ServiceEndpoint, domain_name size too large
StaticFractionalEach fractional custom fee must have its maximum_amount, if specified, at least its minimum_amount
StaticFractionA custom fractional fee set a denominator of zero
StaticFreezeOnce a freeze is scheduled, it must be aborted before any other type of freeze can can be performed.
StaticFreezeThe given freeze start time was in the (consensus) past.
StaticFreezeFreezeTransactionBody does not exist
StaticFreezeThe update file in a freeze transaction body must exist.
StaticFreezeThe hash of the update file in a freeze transaction body must match the in-memory hash.
StaticFreezeIf an NMT upgrade has been prepared, the following operation must be a FREEZE_UPGRADE. (To issue a FREEZE_ONLY, submit a FREEZE_ABORT first.)
StaticFungibleFungible common token used in NFT allowances
StaticGossipFully qualified domain name is not allowed in gossip_endpoint
StaticGossipThe number of gossip endpoints exceeds the limit
StaticGrpcThe GRPC proxy endpoint is set in the NodeCreate or NodeUpdate transaction, which the network does not support.
StaticHookhook creation bytes must use minimal representation
StaticHookhook creation bytes too long
StaticHookhook deleted
StaticHookhook deletion requires zero storage slots
StaticHookhook extension empty
StaticHookhook id in use
StaticHookhook id repeated in creation details
StaticHookhook is not a lambda
StaticHookhook not found
StaticHookshooks are not supported in airdrops
StaticHookshooks executions require top level crypto transfer
StaticHookshooks not enabled
StaticIdenticalA schedule already exists with the same identifying fields of an attempted ScheduleCreate (that is, all fields other than scheduledPayerAccountID)
StaticInnerThe inner transaction of a batch transaction failed
StaticInsufficientWhen the account balance is not sufficient for the transfer
StaticInsufficientThe combined balances of a contract and its auto-renew account (if any) or balance of an account did not cover the auto-renewal fees in a transaction.
StaticInsufficientThe combined balances of a contract and its auto-renew account (if any) did not cover the rent charged for net new storage used in a transaction.
StaticInsufficientNot enough gas was supplied to execute transaction
StaticInsufficientPayment tendered for contract local call cannot cover both the fee and the gas
StaticInsufficientThe payer account has insufficient cryptocurrency to pay the transaction fee
StaticInsufficientThe transaction payer could not afford a custom fee
StaticInsufficientThe sender account in the token transfer transaction could not afford a custom fee
StaticInsufficientToken balance is not sufficient for the transaction
StaticInsufficientThe fee provided in the transaction is insufficient for this type of transaction
StaticInvalidThe crypto transfer credit and debit do not sum equal to 0
StaticInvalidThe account id is invalid or does not exist
StaticInvalidA provided admin key was invalid.
StaticInvalidAn alias used in a CryptoTransfer transaction is not the serialization of a primitive Key message--that is, a Key with a single Ed25519 or ECDSA(secp256k1) public key and no unknown protobuf fields.
StaticInvalidThe account id specified as the owner is invalid or does not exist.
StaticInvalidThe account id specified as the spender is invalid or does not exist.
StaticInvalidThe autoRenewAccount specified is not a valid, active account.
StaticInvalidThe batch key is not valid
StaticInvalidchunk number must be from 1 to total (chunks) inclusive.
StaticInvalidFor every chunk, the payer account that is part of initialTransactionID must match the Payer Account of this transaction. The entire initialTransactionID should match the transactionID of the first chunk, but this is not checked or enforced by Hedera except when the chunk number is 1.
StaticInvalidThe contract id is invalid or does not exist
StaticInvalidAny of the feeCollector accounts for customFees is invalid
StaticInvalidThe provided custom fee schedule key was invalid
StaticInvalidIf the account Id specified as the delegating spender is invalid or does not exist.
StaticInvalidServiceEndpoint is invalid
StaticInvalidThe ethereum transaction either failed parsing or failed signature validation, or some other EthereumTransaction error not covered by another response code.
StaticInvalidFailed to update exchange rate file
StaticInvalidExpiration time provided in the transaction was invalid.
StaticInvalidThe fee collector account id in TokenFeeScheduleUpdate is invalid or does not exist.
StaticInvalidFailed to update fee file
StaticInvalidThe provided fee schedule key contains an invalid key.
StaticInvalidInvalid fee submitted
StaticInvalidThe file id is invalid or does not exist
StaticInvalidFile WACL keys are invalid
StaticInvalidThe provided freeze key was invalid.
StaticInvalidFreezeTransactionBody is invalid
StaticInvalidThe full prefix signature for precompile is not valid
StaticInvalidgossip_ca_certificate is invalid
StaticInvalidgossip_endpoint has a fully qualified domain name instead of ip
StaticInvalidgrpc_certificate_hash is invalid
StaticInvalidThe provided gRPC certificate hash is invalid.
StaticInvalidinvalid hook admin key
StaticInvalidinvalid hook call
StaticInvalidinvalid hook creation spec
StaticInvalidinvalid hook id
StaticInvalidAttempt to set negative initial balance
StaticInvalidStaticInvalidProvided key encoding was not supported by the system
StaticInvalidThe provided fee exempt key list contains an invalid key.
StaticInvalidThe provided KYC key was invalid.
StaticInvalidthe livehash data is not the output of a SHA-384 digest
StaticInvalidThe maximum automatic associations value is not valid.
The most common cause for this error is a value less than -1.
StaticInvalidThe provided list contains invalid max custom fee.
StaticInvalidA provided metadata key was invalid. Verification includes, for example, checking the size of Ed25519 and ECDSA(secp256k1) public keys.
StaticInvalidInvalid nft id
StaticInvalidNode Account provided does not match the node account of the node the transaction was submitted to.
StaticInvalidThe node account_id is invalid
StaticInvalidThe node description is invalid
StaticInvalidA node is not found during update and delete node transaction
StaticInvalidThe account id specified as the owner in TokenReject is invalid or does not exist.
StaticInvalidThe provided pause key was invalid
StaticInvalidthe response code when a smart contract id is passed for a crypto API request
StaticInvalidPayer signature is invalid
StaticInvalidThe provided pending airdrop id is invalid.
This pending airdrop MAY already be claimed or cancelled.
The client SHOULD query a mirror node to determine the current status of the pending airdrop.
StaticInvalidThe range provided in PRNG transaction is negative.
StaticInvalidThe proxy account id is invalid or does not exist.
StaticInvalidthe query header is invalid
StaticInvalidThe range of data to be gathered is out of the set boundaries
StaticInvalid[Deprecated]. attempt to set negative receive record threshold
StaticInvalidIn Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list
StaticInvalidauto renewal period is not a positive number of seconds
StaticInvalidThe Schedule Create Transaction TransactionID account does not exist
StaticInvalidThe Scheduled entity does not exist; or has now expired, been deleted, or been executed
StaticInvalidThe provided Scheduled Payer does not exist
StaticInvalid[Deprecated]. attempt to set negative send record threshold
StaticInvalidinvalid serialized tx message hash algorithm
StaticInvalidservice_endpoint is invalid
StaticInvalidThe transaction signature is not valid
StaticInvalidthe number of key (KeyList, or ThresholdKey) does not match that of signature (SignatureList, or ThresholdKeySignature). e.g. if a keyList has 3 base keys, then the corresponding signatureList should also have 3 base signatures.
StaticInvalidthe type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature)
StaticInvalidDuring an update transaction when the system is not able to find the Users Solidity address
StaticInvalidThe solidity id is invalid or entity with this solidity id does not exist
StaticInvalidThe staking account id or staking node id given is invalid or does not exist.
StaticInvalidA provided submit key was invalid.
StaticInvalidThe provided supply key was invalid.
StaticInvalidThe new throttle definitions system file were invalid, and no more specific error could be divined
StaticInvalidThe requested token burn amount would cause an invalid total supply
StaticInvalidThe requested token burn metadata was invalid
StaticInvalidInvalid token decimals
StaticInvalidThe token is invalid or does not exist
StaticInvalidAny of the token Ids in customFees is invalid
StaticInvalidInvalid token initial supply
StaticInvalidThis airdrop claim is for a pending airdrop with an invalid token.
The token might be deleted, or the sender may not have enough tokens
to fulfill the offer.
The client SHOULD query mirror node to determine the status of the pending airdrop and whether the sender can fulfill the offer.
StaticInvalidInvalid token max supply
StaticInvalidThe requested token mint amount would cause an invalid total supply
StaticInvalidThe requested token mint metadata was invalid
StaticInvalidInvalid token nft serial number
StaticInvalidToken Symbol is not UTF-8 capitalized alphabetical string
StaticInvalidThe Topic ID specified is not in the system.
StaticInvalidA ConsensusService message is empty.
StaticInvalidFor any error not handled by specific error codes listed below.
StaticInvalidInvalid transaction body provided
StaticInvalidThe given transactionValidDuration was either non-positive, or greater than the maximum valid duration of 180 secs.
StaticInvalidTransaction id is not valid
StaticInvalidTransaction start time is greater than current consensus time
StaticInvalidThe transfer account id in CryptoDelete transaction is invalid or does not exist.
StaticInvalidTreasury Account does not exist or is deleted
StaticInvalidThe provided wipe key was invalid.
StaticInvalidThe provided wipe amount must not be negative, zero or bigger than the token holder balance
StaticInvalidA string field in the transaction has a UTF-8 encoding with the prohibited zero byte
StaticIpIn ServiceEndpoint, domain_name and ipAddressV4 are mutually exclusive
StaticKeyThe keys were not provided in the request.
StaticKeyone public key matches more than one prefixes on the signature map
StaticKeyKey not provided in the transaction body
StaticLambdalambda storage update bytes must use minimal representation
StaticLambdalambda storage update bytes too long
StaticLivethe livehash already exists for a given account
StaticLivethe livehash is not present
StaticLocallocal execution (query) is requested for a function which changes state
StaticMaxThe payer account of an approveAllowances or adjustAllowance transaction is attempting to go beyond the maximum allowed number of allowances.
StaticMaxA contract transaction tried to use more than the allowed number of child records, via either system contract records or internal contract creations.
StaticMaxContract permanent storage exceeded the currently allowable limit
StaticMaxThe fee amount is exceeding the amount that the payer is willing to pay.
StaticMaxMax custom fees list is not supported for this operation.
StaticMaxThe maximum number of entities allowed in the current price regime have been created.
StaticMaxThe provided fee exempt key list size exceeded the limit.
StaticMaxFile size exceeded the currently allowable limit
StaticMaxGas exceeded currently allowable gas limit per transaction
StaticMaxAll the NFTs allowed in the current price regime have already been minted
StaticMaxThe maximum number of nodes allowed in the address book have been created.
StaticMaxThe transaction attempted to use more than the allowed number of PendingAirdropId.
StaticMaxAll contract storage allocated to the current price regime has been consumed.
StaticMemoTransaction memo size exceeded 100 bytes
StaticMessageConsensusSubmitMessage request's message size is larger than allowed.
StaticMetadataNft metadata is too long
StaticMissingThe inner transaction of a batch transaction is missing a batch key
StaticMissingA scheduled transaction configured to wait for expiry to execute was not given an explicit expiration time.
StaticMissingHeader is missing in Query request
StaticMissingNFT serial numbers are missing in the TokenUpdateNftsTransactionBody
StaticMissingToken Metadata is not provided
StaticMissingToken Name is not provided
StaticMissingA token symbol was not provided
StaticModifyingattempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key)
StaticNegativeThe specified amount for an approved allowance cannot be negative.
StaticNftNon fungible token used in fungible token allowances
StaticNftAn NFT transfers list referenced a token type other than NON_FUNGIBLE_UNIQUE.
StaticNodenode account has zero balance
StaticNodeGiven the network size in the address book, the node-level capacity for an operation would never be enough to accept a single request; usually means a bucket burstPeriod should be increased
StaticNodeThe node has been marked as deleted
StaticNoA FREEZE_ABORT transaction was handled with no scheduled freeze.
StaticNoThe provided sig map did not contain any new valid signatures from required signers of the scheduled transaction
StaticNoThe account has reached the limit on the automatic associations count.
StaticNoA contract operation attempted to schedule another transaction after it had already scheduled a recursive contract call.
StaticNotThe payer account is not a special account(account 0.0.55)
StaticNotThe API is not currently supported
StaticNoA FREEZE_UPGRADE transaction was handled with no previous update prepared.
StaticNoThere are no corresponding custom fees.
StaticNoWriteAccess Control Keys are not provided for the file
StaticNullnull solidity address
StaticObtainertransferAccountId or transferContractId specified for contract delete does not exist
StaticObtainerwhen deleting smart contract that has crypto balance either transfer account or transfer smart contract is required
StaticObtainerwhen deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted
StaticOkThe transaction passed the precheck validations.
StaticOperationAn operation was assigned to more than one throttle group in a given bucket
StaticPayerThe payer account has been marked as deleted
StaticPayerPayer account does not exist.
StaticPayerThe fee payer account doesn't have permission to submit such Transaction
StaticPendingThe transaction attempted to the same PendingAirdropId twice.
StaticPendingStaticPermanentA delete transaction submitted via HAPI set permanent_removal=true
StaticPlatformthe platform node is either disconnected or lagging behind.
StaticPlatformtransaction not created by platform due to large backlog
StaticPreparedThe prepared update file cannot be updated or appended until either the upgrade has been completed, or a FREEZE_ABORT has been handled.
StaticProxyStaticReceiptReceipt for given transaction id does not exist
StaticReceiverWhen a valid signature is not provided for operations on account with receiverSigRequired=true
StaticRecordRecord for given transaction id does not exist
StaticRecursiveA contract can schedule recursive calls a finite number of times (this is approximately four million times with typical network configuration.)
StaticRejectedrejected by account allowance hook
StaticRepeatedIf the CryptoDeleteAllowance transaction has repeated crypto or token or Nft allowances to delete.
StaticRepeatedSerial numbers are repeated in nft allowance for a single spender account
StaticRequestedCannot set the number of automatic associations for an account more than the maximum allowed token associations tokens.maxPerAccount.
StaticResultSmart contract result size greater than specified maxResultSize
StaticRevertedA precompiled contract succeeded, but was later reverted.
StaticRoyaltyA royalty cannot exceed the total fungible value exchanged for an NFT
StaticScheduleA schedule being signed or deleted has already been deleted
StaticScheduleA schedule being signed or deleted has already been executed
StaticScheduledOnly whitelisted transaction types may be scheduled
StaticScheduleThe scheduled transaction could not be created because it's expiration_time was less than or equal to the consensus time.
StaticScheduleThe scheduled transaction could not be created because it's expiration_time was too far in the future.
StaticScheduleA scheduled transaction configured to wait for expiry to execute was given an expiry time at which there is already too many transactions scheduled to expire; its creation must be retried with a different expiry.
StaticScheduleThe schedule expiry is not configurable
StaticScheduleThe scheduled transaction could not be created because it would cause the gas limit to be violated on the specified expiration_time.
StaticScheduleThe scheduled transaction could not be created because it would cause throttles to be violated on the specified expiration_time.
StaticScheduleThe Scheduled entity cannot be modified. Admin key not set
StaticScheduleThe scheduled transaction is pending expiration.
StaticSelfAn account set the staked_account_id to itself in CryptoUpdate or ContractUpdate transactions.
StaticSenderThe transaction attempted to move an NFT serial number from an account other than its owner
StaticSerializationSerialization failure
StaticSerialCurrently no more than 4,294,967,295 NFTs may be minted for a given unique token type
StaticServiceThe number of service endpoints exceeds the limit
StaticSettingattempting to set negative balance value for crypto account
StaticSomeAt least one of the signatures in the provided sig map did not represent a valid signature for any required signer
StaticSpenderSpender is repeated more than once in Crypto or Token or NFT allowance lists in a single CryptoApproveAllowance or CryptoAdjustAllowance transaction.
StaticSpenderAn approved allowance specifies a spender account that is the same as the hbar/token owner account.
StaticSpenderThe spender does not have an existing approved allowance with the hbar/token owner.
StaticStakingNative staking, while implemented, has not yet enabled by the council.
StaticSuccessThe transaction succeeded
StaticSuccessThe throttle definitions file was updated, but some supported operations were not assigned a bucket
StaticThrottledConsensus throttle did not allow execution of this transaction.
The transaction should be retried after a modest delay.
StaticThrottleA throttle group was granted zero opsPerSec
StaticThrottleThe least common multiple of the throttle group's milliOpsPerSec is too large and it's overflowing.
StaticTokenThe token to be airdropped has a fallback royalty fee and cannot be sent or claimed via an airdrop transaction.
StaticTokenAn associateToken operation specified a token already associated to the account
StaticTokenAdmin key is not set on token
StaticTokenFee schedule key is not set on token
StaticTokenFreeze key is not set on token
StaticTokenKYC key is not set on token
StaticTokenMetadata key is not set on token
StaticTokenStaticTokenPause key is not set on token
StaticTokenSupply key is not set on token
StaticTokenWipe key is not set on token
StaticTokenSame TokenIDs present in the token list
StaticTokenToken does not have Admin key set, thus update/delete transactions cannot be performed
StaticTokenToken is paused. This Token cannot be a part of any kind of Transaction until unpaused.
StaticTokenA token cannot have more units minted due to its configured supply ceiling
StaticTokenToken Name is too long
StaticTokenA required token-account relationship is missing
StaticTokenAny of the token Ids in customFees are not associated to feeCollector
StaticTokenThe transaction attempted to use more than the allowed number of TokenReference.
StaticTokenThe transaction attempted to use duplicate TokenReference.
This affects TokenReject attempting to reject same token reference more than once.
StaticTokensAn involved account already has more than tokens.maxPerAccount associations with non-deleted tokens.
StaticTokenThe provided token symbol was too long
StaticTokenExceeded the number of token transfers (both from and to) allowed for token transfer list
StaticTokenToken transactions cannot be executed on deleted token
StaticTootoo many lambda storage updates
StaticTopicThe topic has expired, was not automatically renewed, and is in a 7 day grace period before the topic will be deleted unrecoverably. This error response code will not be returned until autoRenew functionality is supported by HAPI.
StaticTotalStaticTransactionPre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time.
StaticTransactionA transaction's protobuf message includes unknown fields; could mean that a client expects not-yet-released functionality to be available.
StaticTransactionThe scheduled field in the TransactionID may not be set to true
StaticTransactionThe size of the Transaction is greater than transactionMaxBytes
StaticTransactiontransaction requires zero hooks
StaticTransactionAn attempted operation is invalid until all token balances for the target account are zero
StaticTransactionThe Transaction has more than 50 levels
StaticTransferTransfer Account should not be same as Account to be deleted
StaticTransferExceeded the number of accounts (both from and to) allowed for crypto transfer list
StaticTransfersAmounts in transfer list are not net zero
StaticTreasuryA NFT can only be burned when owned by the unique token's treasury
StaticUnauthorizedAn attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey).
StaticUnexpectedA fungible token transfer expected a different number of decimals than the involved type actually has.
StaticUnknownThe responding node has submitted the transaction to the network. Its final status is still unknown.
StaticUnparseableThe new contents for the throttle definitions system file were not valid protobuf
StaticUnresolvableThe required signers for a scheduled transaction cannot be resolved, for example because they do not exist or have been deleted
StaticUpdateThe update file hash when handling a FREEZE_UPGRADE transaction differs from the file hash at the time of handling the PREPARE_UPGRADE transaction.
StaticUpdateIf an NMT upgrade has been prepared, the subsequent FREEZE_UPGRADE transaction must confirm the hash of the file to be used in the upgrade.
StaticUpdateIf an NMT upgrade has been prepared, the subsequent FREEZE_UPGRADE transaction must confirm the id of the file to be used in the upgrade.
StaticUpdateStaticWaitingThe target network is waiting for the ledger ID to be set, which is a side effect of finishing the network's TSS construction.
StaticWrongEthereumTransaction was signed against a chainId that this network does not support.
StaticWrongwrong hook entity type
StaticWrongThis transaction specified an ethereumNonce that is not the current ethereumNonce of the account.
proto