Class StatusNamespace

The ethereum transaction specified an access list, which the network does not support.

An AccountAmount token transfers list referenced a token type other than FUNGIBLE_COMMON

the account has been marked as deleted

An account did not own the NFT to be wiped

The 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

account frozen for token

account has pending airdrops

the account id passed has not yet been created.

The account cannot be modified. Account's key is not set

This operation cannot be completed because the target account is a "Node Account".
This account is currently in use as the "Node Account" for a consensus node, and therefore the requested change is not permitted. The transaction may be resubmitted once the account is no longer in use as a "Node Account" for any consensus node.

Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account

account is treasury

account kyc not granted for token

same accounts repeated in the transfer account list

An account cannot be dissociated from a unique token if it owns NFTs for the token

The update of the account failed

Token airdrop transactions can not contain multiple senders for a single token.

An alias that is assigned to an account or contract cannot be assigned to another account or contract.

The alias already set on an account cannot be updated using CryptoUpdate transaction.

The transfer amount exceeds the current approved allowance for the spender account.

The establishment or adjustment of an approved allowance cause the token allowance to exceed the token maximum supply.

Violating 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).

An adminKey was not specified on the topic, so there must not be an autoRenewAccount.

the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION]

Unsupported algorithm/encoding used for keys in the transaction

A transaction tried to execute a hook that did not match the specified type or was malformed in some other way.

The batch key is set for a non batch transaction

The list of batch transactions contains duplicated transactions

The list of batch transactions is empty

Repeated operations count exceeds the limit

The list of batch transactions contains a transaction type that is in the AtomicBatch blacklist as configured in the network.

The capacity needed to satisfy all opsPerSec groups in a bucket overflowed a signed 8-byte integral type

A bucket was defined without any throttle groups

If API is throttled out

The approveForAll flag cannot be set for a fungible token.

Cannot set both a hook call and an approval on the same AccountAmount or NftTransfer message.

cannot wipe token treasury account

Consensus throttle did not allow execution of this transaction. System is throttled at consensus level.

Bytecode for smart contract is of length zero

Contract is marked as deleted

For any contract execution related error not handled by specific error codes listed above.

A 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.

File to create a smart contract was of length zero

A ContractUpdate requested removal of a contract's auto-renew account, but that contract has no auto-renew account.

A selfdestruct or ContractDelete targeted a contract with non-zero token balances.

A selfdestruct or ContractDelete targeted a contract that is a token treasury.

Negative gas was offered in smart contract call

Negative value / initial balance was specified in a smart contract call / create

Contract REVERT OPCODE executed

contract byte code size is over the limit

update of the contract failed

The network just started at genesis and is creating system entities.

The treasury for a unique token cannot be changed until it owns no NFTs

More than 20 balance adjustments were to satisfy a CryptoTransfer and its implied custom fee payments

The reference chain of custom fees for a transferred token exceeded the maximum length of 2

Only tokens of type FUNGIBLE_COMMON can be used to as fee schedule denominations

Only positive fees may be assessed at this time

A custom fee schedule entry did not specify either a fixed or fractional fee

A fractional custom fee exceeded the range of a 64-bit signed integer

More than 10 custom fees were specified

Only tokens of type FUNGIBLE_COMMON can have fractional fees

Only tokens of type NON_FUNGIBLE_UNIQUE can have royalty fees

A fee schedule update tried to clear the custom fees from a token whose fee schedule was already empty

The delegating Spender cannot grant approveForAll allowance on a NFT token type for another spender.

The delegating Spender cannot grant allowance on a NFT serial for another spender as it doesnt not have approveForAll granted on token-owner.

The provided max custom fee list contains fees with duplicate account id.

The provided max custom fee list contains fees with duplicate denominations.

This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period)

No allowances have been specified in the approval transaction.

An EVM hook storage update had no contents.

the livehash data is missing

the livehash body is empty

the keys for a livehash are missing

the crypto livehash query is empty

The list of PendingAirdropIds is empty and MUST NOT be empty.

the query body is empty

The transaction attempted to use empty TokenReference list.

empty token transfer account amounts

empty token transfer body

Transaction body provided is empty

Entities with Entity ID below 1000 are not allowed to be deleted

Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string.

An EVM hook execution was throttled due to high network gas utilization.

An EVM hook's mapping slot, storage key, or storage value failed to use the minimal representation (i.e., no leading zeros).

An EVM hook mapping slot, storage key, or storage value exceeded 32 bytes.

The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage

Already existing automatic associations are more than the new maximum automatic associations.

The expiration date/time on a smart contract may not be reduced

There was a system error while performing balance checks, reserved for future.

There was a system error while performing fee calculation, reserved for future.

There was a system error and the transaction failed because of invalid request parameters.

The provided fee exempt key list contains duplicated keys.

Fee Schedule Proto File Part uploaded

If a fee schedule key is not set when we create a topic we cannot add it on update.

If the topic's custom fees are updated the topic SHOULD have a fee schedule key

The contents of file are provided as empty.

the file has been marked as deleted

Unexpected exception thrown by file system functions

Fee Schedule Proto uploaded but not valid (append or update is required)

Fee Schedule Proto uploaded but not valid (append or update is required)

In ServiceEndpoint, domain_name size too large

Each fractional custom fee must have its maximum_amount, if specified, at least its minimum_amount

A custom fractional fee set a denominator of zero

Once a freeze is scheduled, it must be aborted before any other type of freeze can can be performed.

The given freeze start time was in the (consensus) past.

FreezeTransactionBody does not exist

The update file in a freeze transaction body must exist.

The hash of the update file in a freeze transaction body must match the in-memory hash.

If an NMT upgrade has been prepared, the following operation must be a FREEZE_UPGRADE. (To issue a FREEZE_ONLY, submit a FREEZE_ABORT first.)

Fungible common token used in NFT allowances

Fully qualified domain name is not allowed in gossip_endpoint

The number of gossip endpoints exceeds the limit

The GRPC proxy endpoint is set in the NodeCreate or NodeUpdate transaction, which the network does not support.

An EVM hook mapping slot, storage key, or storage value failed to use the minimal representation (i.e., no leading zeros).

A EVM hook mapping slot, storage key, or storage value exceeded 32 bytes.

A hook was deleted.

The hook deletion requires the hook to have zero storage slots.

A hook extension point was empty.

A user tried to create a hook with an id already in use.

A user repeated the same hook id in a creation details list.

The target hook is not an EVM hook.

A hook id was not found.

Hooks are not supported to be used in TokenAirdrop transactions

Hooks are not supported to be used in Batch transactions and Scheduled transactions. They are only supported in a top level CryptoTransfer transaction.

Hooks are not not enabled on the target Hiero network.

A schedule already exists with the same identifying fields of an attempted ScheduleCreate (that is, all fields other than scheduledPayerAccountID)

The inner transaction of a batch transaction failed

When the account balance is not sufficient for the transfer

The 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.

The 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.

Not enough gas was supplied to execute transaction

Payment tendered for contract local call cannot cover both the fee and the gas

The payer account has insufficient cryptocurrency to pay the transaction fee

The transaction payer could not afford a custom fee

The sender account in the token transfer transaction could not afford a custom fee

insufficient token balance

The fee provided in the transaction is insufficient for this type of transaction

The crypto transfer credit and debit do not sum equal to 0

The account id is invalid or does not exist

A provided admin key was invalid. Verify the bytes for an Ed25519 public key are exactly 32 bytes; and the bytes for a compressed ECDSA(secp256k1) key are exactly 33 bytes, with the first byte either 0x02 or 0x03..

An 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.

The account id specified as the owner is invalid or does not exist.

The account id specified as the spender is invalid or does not exist.

The autoRenewAccount specified is not a valid, active account.

The batch key is not valid

invalid chunk number

invalid chunk transaction id

The contract id is invalid or does not exist

Any of the feeCollector accounts for customFees is invalid

The provided custom fee schedule key was invalid

If the account Id specified as the delegating spender is invalid or does not exist.

ServiceEndpoint is invalid

The ethereum transaction either failed parsing or failed signature validation, or some other EthereumTransaction error not covered by another response code.

Failed to update exchange rate file

Expiration time provided in the transaction was invalid.

The fee collector account id in TokenFeeScheduleUpdate is invalid or does not exist.

Failed to update fee file

The provided fee schedule key contains an invalid key.

Invalid fee submitted

The file id is invalid or does not exist

File WACL keys are invalid

invalid freeze key

FreezeTransactionBody is invalid

The full prefix signature for precompile is not valid

A transaction failed because the TLS certificate provided for the node is missing or invalid.

#### Probable Causes The certificate MUST be a TLS certificate of a type permitted for gossip signatures.
The value presented MUST be a UTF-8 NFKD encoding of the TLS certificate.
The certificate encoded MUST be in PEM format.
The gossip_ca_certificate field is REQUIRED and MUST NOT be empty.

A transaction failed because one or more entries in the list of service endpoints for the gossip_endpoint field is invalid.
The most common cause for this response is a service endpoint that has the domain name (DNS) set rather than address and port.

A transaction failed because the hash provided for the gRPC certificate is present but invalid.

#### Probable Causes The grpc_certificate_hash MUST be a SHA-384 hash.
The input hashed MUST be a UTF-8 NFKD encoding of the actual TLS certificate.
The certificate to be encoded MUST be in PEM format.

The provided gRPC certificate hash is invalid.

A hook admin key was invalid.

The HookCall set in the transaction is invalid

A hook creation spec was not found.

A hook id was invalid.

Attempt to set negative initial balance

invalid ipv4 address

Provided key encoding was not supported by the system

The provided fee exempt key list contains an invalid key.

invalid kyc key

the livehash data is not the output of a SHA-384 digest

The maximum automatic associations value is not valid.
The most common cause for this error is a value less than -1.

The provided list contains invalid max custom fee.

A provided metadata key was invalid. Verification includes, for example, checking the size of Ed25519 and ECDSA(secp256k1) public keys.

Invalid nft id

Node Account provided does not match the node account of the node the transaction was submitted to.

A transaction failed because the node account identifier provided does not exist or is not valid.
One common source of this error is providing a node account identifier using the "alias" form rather than "numeric" form. It is also used for atomic batch transaction for child transaction if the node account id is not 0.0.0.

A transaction failed because the description field cannot be encoded as UTF-8 or is more than 100 bytes when encoded.

A transaction failed because the consensus node identified is not valid or does not exist in state.

The account id specified as the owner in TokenReject is invalid or does not exist.

The provided pause key was invalid

the response code when a smart contract id is passed for a crypto API request

Payer signature is invalid

The 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.

The range provided in UtilPrng transaction is negative.

The proxy account id is invalid or does not exist.

the query header is invalid

The range of data to be gathered is out of the set boundaries

Attempt to set negative receive record threshold

In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list

auto renewal period is not a positive number of seconds

The Schedule Create Transaction TransactionID account does not exist

The Scheduled entity does not exist; or has now expired, been deleted, or been executed

The provided Scheduled Payer does not exist

Attempt to set negative send record threshold

A HAPI client cannot set the SignedTransaction#use_serialized_tx_message_hash_algorithm field.

A transaction failed because one or more entries in the list of service endpoints for the service_endpoint field is invalid.
The most common cause for this response is a service endpoint that has the domain name (DNS) set rather than address and port.

The transaction signature is not valid

the 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.

the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature)

During an update transaction when the system is not able to find the Users Solidity address

The solidity id is invalid or entity with this solidity id does not exist

The staking account id or staking node id given is invalid or does not exist.

A provided submit key was invalid.

invalid supply key

The new throttle definitions system file were invalid, and no more specific error could be divined

invalid token burn amount

The requested token burn metadata was invalid

invalid token decimals

invalid token id

Any of the token Ids in customFees is invalid

invalid token initial supply

This 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.

Invalid token max supply

invalid token mint amount

The requested token mint metadata was invalid

Invalid token nft serial number

invalid token symbol

The Topic ID specified is not in the system.

A ConsensusService message is empty.

For any error not handled by specific error codes listed below.

Invalid transaction body provided

The given transactionValidDuration was either non-positive, or greater than the maximum valid duration of 180 secs.

Transaction id is not valid

Transaction start time is greater than current consensus time

The transfer account id in CryptoDelete transaction is invalid or does not exist.

invalid treasury account for token

invalid wipe key

invalid wiping amount

A string field in the transaction has a UTF-8 encoding with the prohibited zero byte

In ServiceEndpoint, domain_name and ipAddressV4 are mutually exclusive

The keys were not provided in the request.

one public key matches more than one prefixes on the signature map

Key not provided in the transaction body

the livehash already exists for a given account

the livehash is not present

local execution (query) is requested for a function which changes state

The payer account of an approveAllowances or adjustAllowance transaction is attempting to go beyond the maximum allowed number of allowances.

A contract transaction tried to use more than the allowed number of child records, via either system contract records or internal contract creations.

Contract permanent storage exceeded the currently allowable limit

The fee amount is exceeding the amount that the payer is willing to pay.

Max custom fees list is not supported for this operation.

The maximum number of entities allowed in the current price regime have been created.

The provided fee exempt key list size exceeded the limit.

File size exceeded the currently allowable limit

Gas exceeded currently allowable gas limit per transaction

All the NFTs allowed in the current price regime have already been minted

The maximum number of nodes allowed in the address book have been created.

All contract storage allocated to the current price regime has been consumed.

Transaction memo size exceeded 100 bytes

ConsensusSubmitMessage request's message size is larger than allowed.

Nft metadata is too long

The inner transaction of a batch transaction is missing a batch key

A scheduled transaction configured to wait for expiry to execute was not given an explicit expiration time.

Header is missing in Query request

NFT serial numbers are missing in the TokenUpdateNftsTransactionBody

Token Metadata is not provided

missing token name

missing token symbol

attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key)

The specified amount for an approved allowance cannot be negative.

Non fungible token used in fungible token allowances

An NFT transfers list referenced a token type other than NON_FUNGIBLE_UNIQUE.

This operation cannot be completed because the target account has a zero balance.
Node accounts require a positive balance. The transaction may be resubmitted once the account has been funded.

Given 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

A transaction failed because the consensus node identified is deleted from the address book.

A FREEZE_ABORT transaction was handled with no scheduled freeze.

The provided sig map did not contain any new valid signatures from required signers of the scheduled transaction

The account has reached the limit on the automatic associations count.

A contract operation attempted to schedule another transaction after it had already scheduled a recursive contract call.

The payer account is not a special account(account 0.0.55)

The API is not currently supported

A FREEZE_UPGRADE transaction was handled with no previous update prepared.

There are no corresponding custom fees.

WriteAccess Control Keys are not provided for the file

null solidity address

transferAccountId or transferContractId specified for contract delete does not exist

when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required

when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted

The transaction passed the precheck validations.

An operation was assigned to more than one throttle group in a given bucket

The payer account has been marked as deleted

Payer account does not exist.

The fee payer account doesn't have permission to submit such Transaction

The number of PendingAirdropId values in the list exceeds the maximum allowable number.

A PendingAirdropId is repeated in a claim or cancel transaction.

pending nft airdrop already exists

A delete transaction submitted via HAPI set permanent_removal=true

the platform node is either disconnected or lagging behind.

transaction not created by platform due to large backlog