- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-getByKey |
-GetByKeyResponse |
-Get all entities associated with a given key |
-
-
-
- |
-
- Response when the client sends the node GetByKeyQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-entities |
-EntityID (repeated) |
-The list of entities that include this public key in their associated Key list |
-
-
-
- |
-
- the ID for a single entity (account, livehash, file, or smart contract instance)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-entity |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID for the cryptocurrency account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-liveHash |
-LiveHash |
-A uniquely identifying livehash of an acount |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountId |
-AccountID |
- The account to which the livehash is attached |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-hash |
-bytes |
- The SHA-384 hash of a credential or certificate |
-
-
-
-keys |
-KeyList |
- A list of keys (primitive or threshold), all of which must sign to attach the livehash to an account, and any one of which can later delete it. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
-Self Reference
- |
-
-
-
- |
-
-
- |
-
-
-
-
- |
-
-
-duration |
-Duration |
- The duration for which the livehash will remain valid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-The number of seconds |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-fileID |
-FileID |
-The file ID of the file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
-The smart contract ID that identifies instance |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-
-
- |
-
-
-getBySolidityID |
-GetBySolidityIDResponse |
-Get the IDs in the format used in transactions, given the format used in Solidity |
-
-
-
- |
-
- Response when the client sends the node GetBySolidityIDQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The Account ID for the cryptocurrency account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
-The file Id for the file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
-A smart contract ID for the instance (if this is included, then the associated accountID will also be included) |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractCallLocal |
-ContractCallLocalResponse |
-Response to call a function of a smart contract instance |
-
-
-
- |
-
- Response when the client sends the node ContractCallLocalQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-functionResult |
-ContractFunctionResult |
-the value returned by the function (if it completed and didn't fail) |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractGetBytecodeResponse |
-ContractGetBytecodeResponse |
-Get the bytecode for a smart contract instance |
-
-
-
- |
-
- Response when the client sends the node ContractGetBytecodeQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-bytecode |
-bytes |
-the bytecode |
-
-
-
-
-
- |
-
-
-contractGetInfo |
-ContractGetInfoResponse |
-Get information about a smart contract instance |
-
-
-
- |
-
- Response when the client sends the node ContractGetInfoQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-contractInfo |
-ContractGetInfoResponse.ContractInfo |
-the information about this contract instance (a state proof can be generated for this) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-ID of the contract instance, in the format used in transactions |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-ID of the cryptocurrency account owned by the contract instance, in the format used in transactions |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-contractAccountID |
-string |
-ID of both the contract instance and the cryptocurrency account owned by the contract instance, in the format used by Solidity |
-
-
-
-adminKey |
-Key |
-the state of the instance and its fields can be modified arbitrarily if this key signs a transaction to modify it. If this is null, then such modifications are not possible, and there is no administrator that can override the normal operation of this smart contract instance. Note that if it is created with no admin keys, then there is no administrator to authorize changing the admin keys, so there can never be any admin keys for that instance. |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-expirationTime |
-Timestamp |
-the current time at which this contract instance (and its account) is set to expire |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-autoRenewPeriod |
-Duration |
-the expiration time will extend every this many seconds. If there are insufficient funds, then it extends as long as possible. If the account is empty when it expires, then it is deleted. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-The number of seconds |
-
-
-
-
-
- |
-
-
-storage |
-int64 |
-number of bytes of storage being used by this instance (which affects the cost to extend the expiration time) |
-
-
-
-memo |
-string |
-the memo associated with the contract (max 100 bytes) |
-
-
-
-balance |
-uint64 |
-The current balance, in tinybars |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractGetRecordsResponse |
-ContractGetRecordsResponse |
-Get all existing records for a smart contract instance |
-
-
-
- |
-
- Response when the client sends the node ContractGetRecordsQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
-The smart contract instance that this record is for |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-records |
-TransactionRecord (repeated) |
-List of records, each with contractCreateResult or contractCallResult as its body |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-receipt |
-TransactionReceipt |
-The status (reach consensus, or failed, or is unknown) and the ID of any new account/file/instance created. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionHash |
-bytes |
-The hash of the Transaction that executed (not the hash of any Transaction that failed for having a duplicate TransactionID) |
-
-
-
-consensusTimestamp |
-Timestamp |
-The consensus timestamp (or null if didn't reach consensus yet) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-transactionID |
-TransactionID |
-The ID of the transaction this record represents |
-
-
-
- |
-
- The ID for a transaction. This is used for retrieving receipts and records for a transaction, for appending to a file right after creating it, for instantiating a smart contract with bytecode in a file just created, and internally by the network for detecting when duplicate transactions are submitted. A user might get a transaction processed faster by submitting it to N nodes, each with a different node account, but all with the same TransactionID. Then, the transaction will take effect when the first of all those nodes submits the transaction and it reaches consensus. The other transactions will not take effect. So this could make the transaction take effect faster, if any given node might be slow. However, the full transaction fee is charged for each transaction, so the total fee is N times as much if the transaction is sent to N nodes.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-transactionValidStart |
-Timestamp |
-The transaction is invalid if consensusTimestamp < transactionID.transactionStartValid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The Account ID that paid for this transaction |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-memo |
-string |
-The memo that was submitted as part of the transaction (max 100 bytes) |
-
-
-
-transactionFee |
-uint64 |
-The actual transaction fee charged, not the original transactionFee value from TransactionBody |
-
-
-
-body |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractCallResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract function (if it completed and didn't fail) from ContractCallTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractCreateResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract constructor (if it completed and didn't fail) from ContractCreateTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
- |
-transferList |
-TransferList |
-All hbar transfers as a result of this transaction, such as fees, or transfers performed by the transaction, or by a smart contract it calls, or by the creation of threshold records that it triggers. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountAmounts |
-AccountAmount (repeated) |
-Multiple list of AccountAmount pairs, each of which has an account and an amount to transfer into it (positive) or out of it (negative) |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenTransferLists |
-TokenTransferList (repeated) |
-All Token transfers as a result of this transaction |
-
-
-
- |
-
- A list of token IDs and amounts representing the transferred out (negative) or into (positive) amounts, represented in the lowest denomination of the token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-token |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-transfers |
-AccountAmount (repeated) |
-Multiple list of AccountAmounts, each of which has an account and amount |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-cryptogetAccountBalance |
-CryptoGetAccountBalanceResponse |
-Get the current balance in a cryptocurrency account |
-
-
-
- |
-
- Response when the client sends the node CryptoGetAccountBalanceQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The account ID that is being described (this is useful with state proofs, for proving to a third party) |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-balance |
-uint64 |
-The current balance, in tinybars |
-
-
-
-tokenBalances |
-TokenBalance (repeated) |
-The array of tokens that the account possesses |
-
-
-
- |
-
- Contains information the balance of an Account in regards to the corresponding Token ID
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-tokenId |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-balance |
-uint64 |
-The current token balance |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-cryptoGetAccountRecords |
-CryptoGetAccountRecordsResponse |
-Get all the records that currently exist for transactions involving an account |
-
-
-
- |
-
- Response when the client sends the node CryptoGetAccountRecordsQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The account that this record is for |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-records |
-TransactionRecord (repeated) |
-List of records, each with CryptoRecordBody as their body |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-receipt |
-TransactionReceipt |
-The status (reach consensus, or failed, or is unknown) and the ID of any new account/file/instance created. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionHash |
-bytes |
-The hash of the Transaction that executed (not the hash of any Transaction that failed for having a duplicate TransactionID) |
-
-
-
-consensusTimestamp |
-Timestamp |
-The consensus timestamp (or null if didn't reach consensus yet) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-transactionID |
-TransactionID |
-The ID of the transaction this record represents |
-
-
-
- |
-
- The ID for a transaction. This is used for retrieving receipts and records for a transaction, for appending to a file right after creating it, for instantiating a smart contract with bytecode in a file just created, and internally by the network for detecting when duplicate transactions are submitted. A user might get a transaction processed faster by submitting it to N nodes, each with a different node account, but all with the same TransactionID. Then, the transaction will take effect when the first of all those nodes submits the transaction and it reaches consensus. The other transactions will not take effect. So this could make the transaction take effect faster, if any given node might be slow. However, the full transaction fee is charged for each transaction, so the total fee is N times as much if the transaction is sent to N nodes.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-transactionValidStart |
-Timestamp |
-The transaction is invalid if consensusTimestamp < transactionID.transactionStartValid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The Account ID that paid for this transaction |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-memo |
-string |
-The memo that was submitted as part of the transaction (max 100 bytes) |
-
-
-
-transactionFee |
-uint64 |
-The actual transaction fee charged, not the original transactionFee value from TransactionBody |
-
-
-
-body |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractCallResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract function (if it completed and didn't fail) from ContractCallTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractCreateResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract constructor (if it completed and didn't fail) from ContractCreateTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
- |
-transferList |
-TransferList |
-All hbar transfers as a result of this transaction, such as fees, or transfers performed by the transaction, or by a smart contract it calls, or by the creation of threshold records that it triggers. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountAmounts |
-AccountAmount (repeated) |
-Multiple list of AccountAmount pairs, each of which has an account and an amount to transfer into it (positive) or out of it (negative) |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenTransferLists |
-TokenTransferList (repeated) |
-All Token transfers as a result of this transaction |
-
-
-
- |
-
- A list of token IDs and amounts representing the transferred out (negative) or into (positive) amounts, represented in the lowest denomination of the token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-token |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-transfers |
-AccountAmount (repeated) |
-Multiple list of AccountAmounts, each of which has an account and amount |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-cryptoGetInfo |
-CryptoGetInfoResponse |
-Get all information about an account |
-
-
-
- |
-
- Response when the client sends the node CryptoGetInfoQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-accountInfo |
-CryptoGetInfoResponse.AccountInfo |
-Info about the account (a state proof can be generated for this) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The account ID for which this information applies |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-contractAccountID |
-string |
-The Contract Account ID comprising of both the contract instance and the cryptocurrency account owned by the contract instance, in the format used by Solidity |
-
-
-
-deleted |
-bool |
-If true, then this account has been deleted, it will disappear when it expires, and all transactions for it will fail except the transaction to extend its expiration date |
-
-
-
-proxyAccountID |
-AccountID |
-The Account ID of the account to which this is proxy staked. If proxyAccountID is null, or is an invalid account, or is an account that isn't a node, then this account is automatically proxy staked to a node chosen by the network, but without earning payments. If the proxyAccountID account refuses to accept proxy staking , or if it is not currently running a node, then it will behave as if proxyAccountID was null. |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-proxyReceived |
-int64 |
-The total number of tinybars proxy staked to this account |
-
-
-
-key |
-Key |
-The key for the account, which must sign in order to transfer out, or to modify the account in any way other than extending its expiration date. |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-balance |
-uint64 |
-The current balance of account in tinybars |
-
-
-
-generateSendRecordThreshold |
-uint64 |
- [Deprecated]. The threshold amount, in tinybars, at which a record is created of any transaction that decreases the balance of this account by more than the threshold |
-
-
-
-generateReceiveRecordThreshold |
-uint64 |
- [Deprecated]. The threshold amount, in tinybars, at which a record is created of any transaction that increases the balance of this account by more than the threshold |
-
-
-
-receiverSigRequired |
-bool |
-If true, no transaction can transfer to this account unless signed by this account's key |
-
-
-
-expirationTime |
-Timestamp |
-The TimeStamp time at which this account is set to expire |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-autoRenewPeriod |
-Duration |
-The duration for expiration time will extend every this many seconds. If there are insufficient funds, then it extends as long as possible. If it is empty when it expires, then it is deleted. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-The number of seconds |
-
-
-
-
-
- |
-
-
-liveHashes |
-LiveHash (repeated) |
-All of the livehashes attached to the account (each of which is a hash along with the keys that authorized it and can delete it) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountId |
-AccountID |
- The account to which the livehash is attached |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-hash |
-bytes |
- The SHA-384 hash of a credential or certificate |
-
-
-
-keys |
-KeyList |
- A list of keys (primitive or threshold), all of which must sign to attach the livehash to an account, and any one of which can later delete it. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
-Self Reference
- |
-
-
-
- |
-
-
- |
-
-
-
-
- |
-
-
-duration |
-Duration |
- The duration for which the livehash will remain valid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-The number of seconds |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenRelationships |
-TokenRelationship (repeated) |
-All tokens related to this account |
-
-
-
- |
-
- Token's information related to the given Account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-tokenId |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-symbol |
-string |
-The Symbol of the token |
-
-
-
-balance |
-uint64 |
-The balance that the Account holds in the smallest denomination |
-
-
-
-kycStatus |
-TokenKycStatus |
-The KYC status of the account (KycNotApplicable, Granted or Revoked). If the token does not have KYC key, KycNotApplicable is returned |
-
-
-
- |
-
- Possible KYC statuses returned on TokenGetInfoQuery or CryptoGetInfoResponse in TokenRelationship
-
-
-
-Enum Name |
-Description |
-
-
-
-
-KycNotApplicable |
- |
-
-
-
-Granted |
- |
-
-
-
-Revoked |
- |
-
-
-
-
-
- |
-
-
-freezeStatus |
-TokenFreezeStatus |
-The Freeze status of the account (FreezeNotApplicable, Frozen or Unfrozen). If the token does not have Freeze key, FreezeNotApplicable is returned |
-
-
-
- |
-
- Possible Freeze statuses returned on TokenGetInfoQuery or CryptoGetInfoResponse in TokenRelationship
-
-
-
-Enum Name |
-Description |
-
-
-
-
-FreezeNotApplicable |
- |
-
-
-
-Frozen |
- |
-
-
-
-Unfrozen |
- |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-cryptoGetLiveHash |
-CryptoGetLiveHashResponse |
-Contains a livehash associated to an account |
-
-
-
- |
-
- Returns the full livehash associated to an account, if it is present. Note that the only way to obtain a state proof exhibiting the absence of a livehash from an account is to retrieve a state proof of the entire account with its list of livehashes.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
- Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-liveHash |
-LiveHash |
- The livehash, if present |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountId |
-AccountID |
- The account to which the livehash is attached |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-hash |
-bytes |
- The SHA-384 hash of a credential or certificate |
-
-
-
-keys |
-KeyList |
- A list of keys (primitive or threshold), all of which must sign to attach the livehash to an account, and any one of which can later delete it. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
-Self Reference
- |
-
-
-
- |
-
-
- |
-
-
-
-
- |
-
-
-duration |
-Duration |
- The duration for which the livehash will remain valid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-The number of seconds |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-cryptoGetProxyStakers |
-CryptoGetStakersResponse |
-Get all the accounts that proxy stake to a given account, and how much they proxy stake |
-
-
-
- |
-
- Response when the client sends the node CryptoGetStakersQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-stakers |
-AllProxyStakers |
-List of accounts proxy staking to this account, and the amount each is currently proxy staking |
-
-
-
- |
-
- all of the accounts proxy staking to a given account, and the amounts proxy staked
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that is being proxy staked to |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-proxyStaker |
-ProxyStaker (repeated) |
-Each of the proxy staking accounts, and the amount they are proxy staking |
-
-
-
- |
-
- information about a single account that is proxy staking
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that is proxy staking |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-int64 |
-The number of hbars that are currently proxy staked |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-fileGetContents |
-FileGetContentsResponse |
-Get the contents of a file (the bytes stored in it) |
-
-
-
- |
-
- Response when the client sends the node FileGetContentsQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-fileContents |
-FileGetContentsResponse.FileContents |
-the file ID and contents (a state proof can be generated for this) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-fileID |
-FileID |
-The file ID of the file whose contents are being returned |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contents |
-bytes |
-The bytes contained in the file |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-fileGetInfo |
-FileGetInfoResponse |
-Get information about a file, such as its expiration date |
-
-
-
- |
-
- Response when the client sends the node FileGetInfoQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-fileInfo |
-FileGetInfoResponse.FileInfo |
-The information about the file |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-fileID |
-FileID |
-The file ID of the file for which information is requested |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-size |
-int64 |
-Number of bytes in contents |
-
-
-
-expirationTime |
-Timestamp |
-The current time at which this account is set to expire |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-deleted |
-bool |
-True if deleted but not yet expired |
-
-
-
-keys |
-KeyList |
-One of these keys must sign in order to modify or delete the file |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
-Self Reference
- |
-
-
-
- |
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionGetReceipt |
-TransactionGetReceiptResponse |
-Get a receipt for a transaction |
-
-
-
- |
-
- Response when the client sends the node TransactionGetReceiptQuery. If it created a new entity (account, file, or smart contract instance) then one of the three ID fields will be filled in with the ID of the new entity. Sometimes a single transaction will create more than one new entity, such as when a new contract instance is created, and this also creates the new account that it owned by that instance. No State proof is available for this response
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-receipt |
-TransactionReceipt |
-Either the receipt of processing the first consensus transaction with the given id whose status was neither INVALID_NODE_ACCOUNT nor INVALID_PAYER_SIGNATURE; or, if no such receipt exists, the receipt of processing the first transaction to reach consensus with the given transaction id. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-duplicateTransactionReceipts |
-TransactionReceipt (repeated) |
-The receipts of processing all consensus transaction with the same id as the distinguished receipt above, in chronological order. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionGetRecord |
-TransactionGetRecordResponse |
-Get a record for a transaction |
-
-
-
- |
-
- Response when the client sends the node TransactionGetRecordQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-transactionRecord |
-TransactionRecord |
-Either the record of processing the first consensus transaction with the given id whose status was neither INVALID_NODE_ACCOUNT nor INVALID_PAYER_SIGNATURE; or, if no such record exists, the record of processing the first transaction to reach consensus with the given transaction id. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-receipt |
-TransactionReceipt |
-The status (reach consensus, or failed, or is unknown) and the ID of any new account/file/instance created. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionHash |
-bytes |
-The hash of the Transaction that executed (not the hash of any Transaction that failed for having a duplicate TransactionID) |
-
-
-
-consensusTimestamp |
-Timestamp |
-The consensus timestamp (or null if didn't reach consensus yet) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-transactionID |
-TransactionID |
-The ID of the transaction this record represents |
-
-
-
- |
-
- The ID for a transaction. This is used for retrieving receipts and records for a transaction, for appending to a file right after creating it, for instantiating a smart contract with bytecode in a file just created, and internally by the network for detecting when duplicate transactions are submitted. A user might get a transaction processed faster by submitting it to N nodes, each with a different node account, but all with the same TransactionID. Then, the transaction will take effect when the first of all those nodes submits the transaction and it reaches consensus. The other transactions will not take effect. So this could make the transaction take effect faster, if any given node might be slow. However, the full transaction fee is charged for each transaction, so the total fee is N times as much if the transaction is sent to N nodes.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-transactionValidStart |
-Timestamp |
-The transaction is invalid if consensusTimestamp < transactionID.transactionStartValid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The Account ID that paid for this transaction |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-memo |
-string |
-The memo that was submitted as part of the transaction (max 100 bytes) |
-
-
-
-transactionFee |
-uint64 |
-The actual transaction fee charged, not the original transactionFee value from TransactionBody |
-
-
-
-body |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractCallResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract function (if it completed and didn't fail) from ContractCallTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractCreateResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract constructor (if it completed and didn't fail) from ContractCreateTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
- |
-transferList |
-TransferList |
-All hbar transfers as a result of this transaction, such as fees, or transfers performed by the transaction, or by a smart contract it calls, or by the creation of threshold records that it triggers. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountAmounts |
-AccountAmount (repeated) |
-Multiple list of AccountAmount pairs, each of which has an account and an amount to transfer into it (positive) or out of it (negative) |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenTransferLists |
-TokenTransferList (repeated) |
-All Token transfers as a result of this transaction |
-
-
-
- |
-
- A list of token IDs and amounts representing the transferred out (negative) or into (positive) amounts, represented in the lowest denomination of the token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-token |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-transfers |
-AccountAmount (repeated) |
-Multiple list of AccountAmounts, each of which has an account and amount |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-duplicateTransactionRecords |
-TransactionRecord (repeated) |
-The records of processing all consensus transaction with the same id as the distinguished record above, in chronological order. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-receipt |
-TransactionReceipt |
-The status (reach consensus, or failed, or is unknown) and the ID of any new account/file/instance created. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionHash |
-bytes |
-The hash of the Transaction that executed (not the hash of any Transaction that failed for having a duplicate TransactionID) |
-
-
-
-consensusTimestamp |
-Timestamp |
-The consensus timestamp (or null if didn't reach consensus yet) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-transactionID |
-TransactionID |
-The ID of the transaction this record represents |
-
-
-
- |
-
- The ID for a transaction. This is used for retrieving receipts and records for a transaction, for appending to a file right after creating it, for instantiating a smart contract with bytecode in a file just created, and internally by the network for detecting when duplicate transactions are submitted. A user might get a transaction processed faster by submitting it to N nodes, each with a different node account, but all with the same TransactionID. Then, the transaction will take effect when the first of all those nodes submits the transaction and it reaches consensus. The other transactions will not take effect. So this could make the transaction take effect faster, if any given node might be slow. However, the full transaction fee is charged for each transaction, so the total fee is N times as much if the transaction is sent to N nodes.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-transactionValidStart |
-Timestamp |
-The transaction is invalid if consensusTimestamp < transactionID.transactionStartValid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The Account ID that paid for this transaction |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-memo |
-string |
-The memo that was submitted as part of the transaction (max 100 bytes) |
-
-
-
-transactionFee |
-uint64 |
-The actual transaction fee charged, not the original transactionFee value from TransactionBody |
-
-
-
-body |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractCallResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract function (if it completed and didn't fail) from ContractCallTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractCreateResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract constructor (if it completed and didn't fail) from ContractCreateTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
- |
-transferList |
-TransferList |
-All hbar transfers as a result of this transaction, such as fees, or transfers performed by the transaction, or by a smart contract it calls, or by the creation of threshold records that it triggers. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountAmounts |
-AccountAmount (repeated) |
-Multiple list of AccountAmount pairs, each of which has an account and an amount to transfer into it (positive) or out of it (negative) |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenTransferLists |
-TokenTransferList (repeated) |
-All Token transfers as a result of this transaction |
-
-
-
- |
-
- A list of token IDs and amounts representing the transferred out (negative) or into (positive) amounts, represented in the lowest denomination of the token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-token |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-transfers |
-AccountAmount (repeated) |
-Multiple list of AccountAmounts, each of which has an account and amount |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionGetFastRecord |
-TransactionGetFastRecordResponse |
-Get a record for a transaction (lasts 180 seconds) |
-
-
-
- |
-
- Response when the client sends the node TransactionGetFastRecordQuery. If it created a new entity (account, file, or smart contract instance) then one of the three ID fields will be filled in with the ID of the new entity. Sometimes a single transaction will create more than one new entity, such as when a new contract instance is created, and this also creates the new account that it owned by that instance.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-transactionRecord |
-TransactionRecord |
-The requested transaction records |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-receipt |
-TransactionReceipt |
-The status (reach consensus, or failed, or is unknown) and the ID of any new account/file/instance created. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-status |
-ResponseCodeEnum |
- The consensus status of the transaction; is UNKNOWN if consensus has not been reached, or if the associated transaction did not have a valid payer signature |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
- In the receipt of a CryptoCreate, the id of the newly created account |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-fileID |
-FileID |
- In the receipt of a FileCreate, the id of the newly created file |
-
-
-
- |
-
- The ID for a file
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-fileNum |
-int64 |
-A nonnegative File number unique within its realm |
-
-
-
-
-
- |
-
-
-contractID |
-ContractID |
- In the receipt of a ContractCreate, the id of the newly created contract |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-exchangeRate |
-ExchangeRateSet |
- The exchange rates in effect when the transaction reached consensus |
-
-
-
- |
-
- Two sets of exchange rates
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-currentRate |
-ExchangeRate |
- Current exchange rate |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-nextRate |
-ExchangeRate |
- Next exchange rate which will take effect when current rate expires |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-hbarEquiv |
-int32 |
- Denominator in calculation of exchange rate between hbar and cents |
-
-
-
-centEquiv |
-int32 |
- Numerator in calculation of exchange rate between hbar and cents |
-
-
-
-expirationTime |
-TimestampSeconds |
- Expiration time in seconds for this exchange rate |
-
-
-
- |
-
- An exact date and time, with a resolution of one second (no nanoseconds).
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-topicID |
-TopicID |
- In the receipt of a ConsensusCreateTopic, the id of the newly created topic. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicSequenceNumber |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the new sequence number of the topic that received the message |
-
-
-
-topicRunningHash |
-bytes |
- In the receipt of a ConsensusSubmitMessage, the new running hash of the topic that received the message. This 48-byte field is the output of a particular SHA-384 digest whose input data are determined by the value of the topicRunningHashVersion below. The bytes of each uint64 or uint32 are to be in Big-Endian format.
IF the topicRunningHashVersion is '0' or '1', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topic's shard (8 bytes) 3. The topic's realm (8 bytes) 4. The topic's number (8 bytes) 5. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 6. The number of nanoseconds since 5. before the ConsensusSubmitMessage reached consensus (4 bytes) 7. The topicSequenceNumber from above (8 bytes) 8. The message bytes from the ConsensusSubmitMessage (variable).
IF the topicRunningHashVersion is '2', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The topic's shard (8 bytes) 4. The topic's realm (8 bytes) 5. The topic's number (8 bytes) 6. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 7. The number of nanoseconds since 6. before the ConsensusSubmitMessage reached consensus (4 bytes) 8. The topicSequenceNumber from above (8 bytes) 9. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes)
Otherwise, IF the topicRunningHashVersion is '3', then the input data to the SHA-384 digest are, in order: --- 1. The previous running hash of the topic (48 bytes) 2. The topicRunningHashVersion below (8 bytes) 3. The payer account's shard (8 bytes) 4. The payer account's realm (8 bytes) 5. The payer account's number (8 bytes) 6. The topic's shard (8 bytes) 7. The topic's realm (8 bytes) 8. The topic's number (8 bytes) 9. The number of seconds since the epoch before the ConsensusSubmitMessage reached consensus (8 bytes) 10. The number of nanoseconds since 9. before the ConsensusSubmitMessage reached consensus (4 bytes) 11. The topicSequenceNumber from above (8 bytes) 12. The output of the SHA-384 digest of the message bytes from the consensusSubmitMessage (48 bytes) |
-
-
-
-topicRunningHashVersion |
-uint64 |
- In the receipt of a ConsensusSubmitMessage, the version of the SHA-384 digest used to update the running hash. |
-
-
-
-tokenId |
-TokenID |
- In the receipt of a CreateToken, the id of the newly created token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-transactionHash |
-bytes |
-The hash of the Transaction that executed (not the hash of any Transaction that failed for having a duplicate TransactionID) |
-
-
-
-consensusTimestamp |
-Timestamp |
-The consensus timestamp (or null if didn't reach consensus yet) |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-transactionID |
-TransactionID |
-The ID of the transaction this record represents |
-
-
-
- |
-
- The ID for a transaction. This is used for retrieving receipts and records for a transaction, for appending to a file right after creating it, for instantiating a smart contract with bytecode in a file just created, and internally by the network for detecting when duplicate transactions are submitted. A user might get a transaction processed faster by submitting it to N nodes, each with a different node account, but all with the same TransactionID. Then, the transaction will take effect when the first of all those nodes submits the transaction and it reaches consensus. The other transactions will not take effect. So this could make the transaction take effect faster, if any given node might be slow. However, the full transaction fee is charged for each transaction, so the total fee is N times as much if the transaction is sent to N nodes.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-transactionValidStart |
-Timestamp |
-The transaction is invalid if consensusTimestamp < transactionID.transactionStartValid |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-accountID |
-AccountID |
-The Account ID that paid for this transaction |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-memo |
-string |
-The memo that was submitted as part of the transaction (max 100 bytes) |
-
-
-
-transactionFee |
-uint64 |
-The actual transaction fee charged, not the original transactionFee value from TransactionBody |
-
-
-
-body |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractCallResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract function (if it completed and didn't fail) from ContractCallTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-contractCreateResult |
-ContractFunctionResult |
-Record of the value returned by the smart contract constructor (if it completed and didn't fail) from ContractCreateTransaction |
-
-
-
- |
-
- The result returned by a call to a smart contract function. This is part of the response to a ContractCallLocal query, and is in the record for a ContractCall or ContractCreateInstance transaction. The ContractCreateInstance transaction record has the results of the call to the constructor.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-the smart contract instance whose function was called |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-contractCallResult |
-bytes |
-the result returned by the function |
-
-
-
-errorMessage |
-string |
-message In case there was an error during smart contract execution |
-
-
-
-bloom |
-bytes |
-bloom filter for record |
-
-
-
-gasUsed |
-uint64 |
-units of gas used to execute contract |
-
-
-
-logInfo |
-ContractLoginfo (repeated) |
-the log info for events returned by the function |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-address of a contract that emitted the event |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-bloom |
-bytes |
-bloom filter for a particular log |
-
-
-
-topic |
-bytes (repeated) |
-topics of a particular event |
-
-
-
-data |
-bytes |
-event data |
-
-
-
-
-
- |
-
-
-createdContractIDs |
-ContractID (repeated) |
-the list of smart contracts that were created by the function call |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
- |
-transferList |
-TransferList |
-All hbar transfers as a result of this transaction, such as fees, or transfers performed by the transaction, or by a smart contract it calls, or by the creation of threshold records that it triggers. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountAmounts |
-AccountAmount (repeated) |
-Multiple list of AccountAmount pairs, each of which has an account and an amount to transfer into it (positive) or out of it (negative) |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenTransferLists |
-TokenTransferList (repeated) |
-All Token transfers as a result of this transaction |
-
-
-
- |
-
- A list of token IDs and amounts representing the transferred out (negative) or into (positive) amounts, represented in the lowest denomination of the token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-token |
-TokenID |
-The ID of the token |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-transfers |
-AccountAmount (repeated) |
-Multiple list of AccountAmounts, each of which has an account and amount |
-
-
-
- |
-
- An account, and the amount that it sends or receives during a cryptocurrency or token transfer.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-accountID |
-AccountID |
-The Account ID that sends/receives cryptocurrency or tokens |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-amount |
-sint64 |
-The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive) |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-consensusGetTopicInfo |
-ConsensusGetTopicInfoResponse |
-Parameters of and state of a consensus topic.. |
-
-
-
- |
-
- Retrieve the parameters of and state of a consensus topic.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
- Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-topicID |
-TopicID |
-Topic identifier. |
-
-
-
- |
-
- Unique identifier for a topic (used by the consensus service)
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-topicNum |
-int64 |
-Unique topic identifier within a realm (nonnegative). |
-
-
-
-
-
- |
-
-
-topicInfo |
-ConsensusTopicInfo |
-Current state of the topic |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-memo |
-string |
-Short publicly visible memo about the topic. No guarantee of uniqueness. |
-
-
-
-runningHash |
-bytes |
- When a topic is created, its running hash is initialized to 48 bytes of binary zeros. For each submitted message, the topic's running hash is then updated to the output of a particular SHA-384 digest whose input data include the previous running hash.
See the TransactionReceipt.proto documentation for an exact description of the data included in the SHA-384 digest used for the update. |
-
-
-
-sequenceNumber |
-uint64 |
- Sequence number (starting at 1 for the first submitMessage) of messages on the topic. |
-
-
-
-expirationTime |
-Timestamp |
- Effective consensus timestamp at (and after) which submitMessage calls will no longer succeed on the topic and the topic will expire and after AUTORENEW_GRACE_PERIOD be automatically deleted. |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-Number of complete seconds since the start of the epoch |
-
-
-
-nanos |
-int32 |
-Number of nanoseconds since the start of the last second |
-
-
-
-
-
- |
-
-
-adminKey |
-Key |
-Access control for update/delete of the topic. Null if there is no key. |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-submitKey |
-Key |
-Access control for ConsensusService.submitMessage. Null if there is no key. |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-autoRenewPeriod |
-Duration |
- |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-seconds |
-int64 |
-The number of seconds |
-
-
-
-
-
- |
-
-
-autoRenewAccount |
-AccountID |
-Null if there is no autoRenewAccount. |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-networkGetVersionInfo |
-NetworkGetVersionInfoResponse |
-Semantic versions of Hedera Services and HAPI proto |
-
-
-
- |
-
- Response when the client sends the node NetworkGetVersionInfoQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-hapiProtoVersion |
-SemanticVersion |
- |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-major |
-int32 |
-Increases with incompatible API changes |
-
-
-
-minor |
-int32 |
-Increases with backwards-compatible new functionality |
-
-
-
-patch |
-int32 |
-Increases with backwards-compatible bug fixes |
-
-
-
-
-
- |
-
-
-hederaServicesVersion |
-SemanticVersion |
- |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-major |
-int32 |
-Increases with incompatible API changes |
-
-
-
-minor |
-int32 |
-Increases with backwards-compatible new functionality |
-
-
-
-patch |
-int32 |
-Increases with backwards-compatible bug fixes |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-tokenGetInfo |
-TokenGetInfoResponse |
-Get all information about a token |
-
-
-
- |
-
- Response when the client sends the node TokenGetInfoQuery
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-header |
-ResponseHeader |
-Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither |
-
-
-
- |
-
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-nodeTransactionPrecheckCode |
-ResponseCodeEnum |
-Result of fee transaction precheck, saying it passed, or why it failed |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-OK |
-The transaction passed the precheck validations. |
-
-
-
-INVALID_TRANSACTION |
-For any error not handled by specific error codes listed below. |
-
-
-
-PAYER_ACCOUNT_NOT_FOUND |
-Payer account does not exist. |
-
-
-
-INVALID_NODE_ACCOUNT |
-Node Account provided does not match the node account of the node the transaction was submitted to. |
-
-
-
-TRANSACTION_EXPIRED |
-Pre-Check error when TransactionValidStart + transactionValidDuration is less than current consensus time. |
-
-
-
-INVALID_TRANSACTION_START |
-Transaction start time is greater than current consensus time |
-
-
-
-INVALID_TRANSACTION_DURATION |
-valid transaction duration is a positive non zero number that does not exceed 120 seconds |
-
-
-
-INVALID_SIGNATURE |
-The transaction signature is not valid |
-
-
-
-MEMO_TOO_LONG |
-Transaction memo size exceeded 100 bytes |
-
-
-
-INSUFFICIENT_TX_FEE |
-The fee provided in the transaction is insufficient for this type of transaction |
-
-
-
-INSUFFICIENT_PAYER_BALANCE |
-The payer account has insufficient cryptocurrency to pay the transaction fee |
-
-
-
-DUPLICATE_TRANSACTION |
-This transaction ID is a duplicate of one that was submitted to this node or reached consensus in the last 180 seconds (receipt period) |
-
-
-
-BUSY |
-If API is throttled out |
-
-
-
-NOT_SUPPORTED |
-The API is not currently supported |
-
-
-
-INVALID_FILE_ID |
-The file id is invalid or does not exist |
-
-
-
-INVALID_ACCOUNT_ID |
-The account id is invalid or does not exist |
-
-
-
-INVALID_CONTRACT_ID |
-The contract id is invalid or does not exist |
-
-
-
-INVALID_TRANSACTION_ID |
-Transaction id is not valid |
-
-
-
-RECEIPT_NOT_FOUND |
-Receipt for given transaction id does not exist |
-
-
-
-RECORD_NOT_FOUND |
-Record for given transaction id does not exist |
-
-
-
-INVALID_SOLIDITY_ID |
-The solidity id is invalid or entity with this solidity id does not exist |
-
-
-
-UNKNOWN |
-The responding node has submitted the transaction to the network. Its final status is still unknown. |
-
-
-
-SUCCESS |
-The transaction succeeded |
-
-
-
-FAIL_INVALID |
-There was a system error and the transaction failed because of invalid request parameters. |
-
-
-
-FAIL_FEE |
-There was a system error while performing fee calculation, reserved for future. |
-
-
-
-FAIL_BALANCE |
-There was a system error while performing balance checks, reserved for future. |
-
-
-
-KEY_REQUIRED |
-Key not provided in the transaction body |
-
-
-
-BAD_ENCODING |
-Unsupported algorithm/encoding used for keys in the transaction |
-
-
-
-INSUFFICIENT_ACCOUNT_BALANCE |
-When the account balance is not sufficient for the transfer |
-
-
-
-INVALID_SOLIDITY_ADDRESS |
-During an update transaction when the system is not able to find the Users Solidity address |
-
-
-
-INSUFFICIENT_GAS |
-Not enough gas was supplied to execute transaction |
-
-
-
-CONTRACT_SIZE_LIMIT_EXCEEDED |
-contract byte code size is over the limit |
-
-
-
-LOCAL_CALL_MODIFICATION_EXCEPTION |
-local execution (query) is requested for a function which changes state |
-
-
-
-CONTRACT_REVERT_EXECUTED |
-Contract REVERT OPCODE executed |
-
-
-
-CONTRACT_EXECUTION_EXCEPTION |
-For any contract execution related error not handled by specific error codes listed above. |
-
-
-
-INVALID_RECEIVING_NODE_ACCOUNT |
-In Query validation, account with +ve(amount) value should be Receiving node account, the receiver account should be only one account in the list |
-
-
-
-MISSING_QUERY_HEADER |
-Header is missing in Query request |
-
-
-
-ACCOUNT_UPDATE_FAILED |
-The update of the account failed |
-
-
-
-INVALID_KEY_ENCODING |
-Provided key encoding was not supported by the system |
-
-
-
-NULL_SOLIDITY_ADDRESS |
-null solidity address |
-
-
-
-CONTRACT_UPDATE_FAILED |
-update of the contract failed |
-
-
-
-INVALID_QUERY_HEADER |
-the query header is invalid |
-
-
-
-INVALID_FEE_SUBMITTED |
-Invalid fee submitted |
-
-
-
-INVALID_PAYER_SIGNATURE |
-Payer signature is invalid |
-
-
-
-KEY_NOT_PROVIDED |
-The keys were not provided in the request. |
-
-
-
-INVALID_EXPIRATION_TIME |
-Expiration time provided in the transaction was invalid. |
-
-
-
-NO_WACL_KEY |
-WriteAccess Control Keys are not provided for the file |
-
-
-
-FILE_CONTENT_EMPTY |
-The contents of file are provided as empty. |
-
-
-
-INVALID_ACCOUNT_AMOUNTS |
-The crypto transfer credit and debit do not sum equal to 0 |
-
-
-
-EMPTY_TRANSACTION_BODY |
-Transaction body provided is empty |
-
-
-
-INVALID_TRANSACTION_BODY |
-Invalid transaction body provided |
-
-
-
-INVALID_SIGNATURE_TYPE_MISMATCHING_KEY |
-the type of key (base ed25519 key, KeyList, or ThresholdKey) does not match the type of signature (base ed25519 signature, SignatureList, or ThresholdKeySignature) |
-
-
-
-INVALID_SIGNATURE_COUNT_MISMATCHING_KEY |
-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. |
-
-
-
-EMPTY_LIVE_HASH_BODY |
-the livehash body is empty |
-
-
-
-EMPTY_LIVE_HASH |
-the livehash data is missing |
-
-
-
-EMPTY_LIVE_HASH_KEYS |
-the keys for a livehash are missing |
-
-
-
-INVALID_LIVE_HASH_SIZE |
-the livehash data is not the output of a SHA-384 digest |
-
-
-
-EMPTY_QUERY_BODY |
-the query body is empty |
-
-
-
-EMPTY_LIVE_HASH_QUERY |
-the crypto livehash query is empty |
-
-
-
-LIVE_HASH_NOT_FOUND |
-the livehash is not present |
-
-
-
-ACCOUNT_ID_DOES_NOT_EXIST |
-the account id passed has not yet been created. |
-
-
-
-LIVE_HASH_ALREADY_EXISTS |
-the livehash already exists for a given account |
-
-
-
-INVALID_FILE_WACL |
-File WACL keys are invalid |
-
-
-
-SERIALIZATION_FAILED |
-Serialization failure |
-
-
-
-TRANSACTION_OVERSIZE |
-The size of the Transaction is greater than transactionMaxBytes |
-
-
-
-TRANSACTION_TOO_MANY_LAYERS |
-The Transaction has more than 50 levels |
-
-
-
-CONTRACT_DELETED |
-Contract is marked as deleted |
-
-
-
-PLATFORM_NOT_ACTIVE |
-the platform node is either disconnected or lagging behind. |
-
-
-
-KEY_PREFIX_MISMATCH |
-one public key matches more than one prefixes on the signature map |
-
-
-
-PLATFORM_TRANSACTION_NOT_CREATED |
-transaction not created by platform due to large backlog |
-
-
-
-INVALID_RENEWAL_PERIOD |
-auto renewal period is not a positive number of seconds |
-
-
-
-INVALID_PAYER_ACCOUNT_ID |
-the response code when a smart contract id is passed for a crypto API request |
-
-
-
-ACCOUNT_DELETED |
-the account has been marked as deleted |
-
-
-
-FILE_DELETED |
-the file has been marked as deleted |
-
-
-
-ACCOUNT_REPEATED_IN_ACCOUNT_AMOUNTS |
-same accounts repeated in the transfer account list |
-
-
-
-SETTING_NEGATIVE_ACCOUNT_BALANCE |
-attempting to set negative balance value for crypto account |
-
-
-
-OBTAINER_REQUIRED |
-when deleting smart contract that has crypto balance either transfer account or transfer smart contract is required |
-
-
-
-OBTAINER_SAME_CONTRACT_ID |
-when deleting smart contract that has crypto balance you can not use the same contract id as transferContractId as the one being deleted |
-
-
-
-OBTAINER_DOES_NOT_EXIST |
-transferAccountId or transferContractId specified for contract delete does not exist |
-
-
-
-MODIFYING_IMMUTABLE_CONTRACT |
-attempting to modify (update or delete a immutable smart contract, i.e. one created without a admin key) |
-
-
-
-FILE_SYSTEM_EXCEPTION |
-Unexpected exception thrown by file system functions |
-
-
-
-AUTORENEW_DURATION_NOT_IN_RANGE |
-the duration is not a subset of [MINIMUM_AUTORENEW_DURATION,MAXIMUM_AUTORENEW_DURATION] |
-
-
-
-ERROR_DECODING_BYTESTRING |
-Decoding the smart contract binary to a byte array failed. Check that the input is a valid hex string. |
-
-
-
-CONTRACT_FILE_EMPTY |
-File to create a smart contract was of length zero |
-
-
-
-CONTRACT_BYTECODE_EMPTY |
-Bytecode for smart contract is of length zero |
-
-
-
-INVALID_INITIAL_BALANCE |
-Attempt to set negative initial balance |
-
-
-
-INVALID_RECEIVE_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative receive record threshold |
-
-
-
-INVALID_SEND_RECORD_THRESHOLD |
-[Deprecated]. attempt to set negative send record threshold |
-
-
-
-ACCOUNT_IS_NOT_GENESIS_ACCOUNT |
-Special Account Operations should be performed by only Genesis account, return this code if it is not Genesis Account |
-
-
-
-PAYER_ACCOUNT_UNAUTHORIZED |
-The fee payer account doesn't have permission to submit such Transaction |
-
-
-
-INVALID_FREEZE_TRANSACTION_BODY |
-FreezeTransactionBody is invalid |
-
-
-
-FREEZE_TRANSACTION_BODY_NOT_FOUND |
-FreezeTransactionBody does not exist |
-
-
-
-TRANSFER_LIST_SIZE_LIMIT_EXCEEDED |
-Exceeded the number of accounts (both from and to) allowed for crypto transfer list |
-
-
-
-RESULT_SIZE_LIMIT_EXCEEDED |
-Smart contract result size greater than specified maxResultSize |
-
-
-
-NOT_SPECIAL_ACCOUNT |
-The payer account is not a special account(account 0.0.55) |
-
-
-
-CONTRACT_NEGATIVE_GAS |
-Negative gas was offered in smart contract call |
-
-
-
-CONTRACT_NEGATIVE_VALUE |
-Negative value / initial balance was specified in a smart contract call / create |
-
-
-
-INVALID_FEE_FILE |
-Failed to update fee file |
-
-
-
-INVALID_EXCHANGE_RATE_FILE |
-Failed to update exchange rate file |
-
-
-
-INSUFFICIENT_LOCAL_CALL_GAS |
-Payment tendered for contract local call cannot cover both the fee and the gas |
-
-
-
-ENTITY_NOT_ALLOWED_TO_DELETE |
-Entities with Entity ID below 1000 are not allowed to be deleted |
-
-
-
-AUTHORIZATION_FAILED |
-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). |
-
-
-
-FILE_UPLOADED_PROTO_INVALID |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FILE_UPLOADED_PROTO_NOT_SAVED_TO_DISK |
-Fee Schedule Proto uploaded but not valid (append or update is required) |
-
-
-
-FEE_SCHEDULE_FILE_PART_UPLOADED |
-Fee Schedule Proto File Part uploaded |
-
-
-
-EXCHANGE_RATE_CHANGE_LIMIT_EXCEEDED |
-The change on Exchange Rate exceeds Exchange_Rate_Allowed_Percentage |
-
-
-
-MAX_CONTRACT_STORAGE_EXCEEDED |
-Contract permanent storage exceeded the currently allowable limit |
-
-
-
-TRANSFER_ACCOUNT_SAME_AS_DELETE_ACCOUNT |
-Transfer Account should not be same as Account to be deleted |
-
-
-
-TOTAL_LEDGER_BALANCE_INVALID |
- |
-
-
-
-EXPIRATION_REDUCTION_NOT_ALLOWED |
-The expiration date/time on a smart contract may not be reduced |
-
-
-
-MAX_GAS_LIMIT_EXCEEDED |
-Gas exceeded currently allowable gas limit per transaction |
-
-
-
-MAX_FILE_SIZE_EXCEEDED |
-File size exceeded the currently allowable limit |
-
-
-
-INVALID_TOPIC_ID |
-The Topic ID specified is not in the system. |
-
-
-
-INVALID_ADMIN_KEY |
- |
-
-
-
-INVALID_SUBMIT_KEY |
- |
-
-
-
-UNAUTHORIZED |
-An attempted operation was not authorized (ie - a deleteTopic for a topic with no adminKey). |
-
-
-
-INVALID_TOPIC_MESSAGE |
-A ConsensusService message is empty. |
-
-
-
-INVALID_AUTORENEW_ACCOUNT |
-The autoRenewAccount specified is not a valid, active account. |
-
-
-
-AUTORENEW_ACCOUNT_NOT_ALLOWED |
- An adminKey was not specified on the topic, so there must not be an autoRenewAccount. |
-
-
-
-TOPIC_EXPIRED |
- The 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. |
-
-
-
-INVALID_CHUNK_NUMBER |
-chunk number must be from 1 to total (chunks) inclusive. |
-
-
-
-INVALID_CHUNK_TRANSACTION_ID |
-For 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. |
-
-
-
-ACCOUNT_FROZEN_FOR_TOKEN |
-Account is frozen and cannot transact with the token |
-
-
-
-TOKENS_PER_ACCOUNT_LIMIT_EXCEEDED |
-Maximum number of token relations for agiven account is exceeded |
-
-
-
-INVALID_TOKEN_ID |
-The token is invalid or does not exist |
-
-
-
-INVALID_TOKEN_DECIMALS |
-Invalid token decimals |
-
-
-
-INVALID_TOKEN_INITIAL_SUPPLY |
-Invalid token initial supply |
-
-
-
-INVALID_TREASURY_ACCOUNT_FOR_TOKEN |
-Treasury Account does not exist or is deleted |
-
-
-
-INVALID_TOKEN_SYMBOL |
-Token Symbol is not UTF-8 capitalized alphabetical string |
-
-
-
-TOKEN_HAS_NO_FREEZE_KEY |
-Freeze key is not set on token |
-
-
-
-TRANSFERS_NOT_ZERO_SUM_FOR_TOKEN |
-Amounts in transfer list are not net zero |
-
-
-
-MISSING_TOKEN_SYMBOL |
-Token Symbol is not provided |
-
-
-
-TOKEN_SYMBOL_TOO_LONG |
-Token Symbol is too long |
-
-
-
-ACCOUNT_KYC_NOT_GRANTED_FOR_TOKEN |
-KYC must be granted and account does not have KYC granted |
-
-
-
-TOKEN_HAS_NO_KYC_KEY |
-KYC key is not set on token |
-
-
-
-INSUFFICIENT_TOKEN_BALANCE |
-Token balance is not sufficient for the transaction |
-
-
-
-TOKEN_WAS_DELETED |
-Token transactions cannot be executed on deleted token |
-
-
-
-TOKEN_HAS_NO_SUPPLY_KEY |
-Supply key is not set on token |
-
-
-
-TOKEN_HAS_NO_WIPE_KEY |
-Wipe key is not set on token |
-
-
-
-INVALID_TOKEN_MINT_AMOUNT |
- |
-
-
-
-INVALID_TOKEN_BURN_AMOUNT |
- |
-
-
-
-TOKEN_NOT_ASSOCIATED_TO_ACCOUNT |
- |
-
-
-
-CANNOT_WIPE_TOKEN_TREASURY_ACCOUNT |
-Cannot execute wipe operation on treasury account |
-
-
-
-INVALID_KYC_KEY |
- |
-
-
-
-INVALID_WIPE_KEY |
- |
-
-
-
-INVALID_FREEZE_KEY |
- |
-
-
-
-INVALID_SUPPLY_KEY |
- |
-
-
-
-MISSING_TOKEN_NAME |
-Token Name is not provided |
-
-
-
-TOKEN_NAME_TOO_LONG |
-Token Name is too long |
-
-
-
-INVALID_WIPING_AMOUNT |
-The provided wipe amount must not be negative, zero or bigger than the token holder balance |
-
-
-
-TOKEN_IS_IMMUTABLE |
-Token does not have Admin key set, thus update/delete transactions cannot be performed |
-
-
-
-TOKEN_ALREADY_ASSOCIATED_TO_ACCOUNT |
-An associateToken operation specified a token already associated to the account |
-
-
-
-TRANSACTION_REQUIRES_ZERO_TOKEN_BALANCES |
-An attempted operation is invalid until all token balances for the target account are zero |
-
-
-
-ACCOUNT_IS_TREASURY |
-An attempted operation is invalid because the account is a treasury |
-
-
-
-
-
- |
-
-
-responseType |
-ResponseType |
-The requested response is repeated back here, for convenience |
-
-
-
- |
-
-
-
-
-
-Enum Name |
-Description |
-
-
-
-
-ANSWER_ONLY |
- Response returns answer |
-
-
-
-ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns both answer and state proof |
-
-
-
-COST_ANSWER |
- Response returns the cost of answer |
-
-
-
-COST_ANSWER_STATE_PROOF |
- (NOT YET SUPPORTED) Response returns the total cost of answer and state proof |
-
-
-
-
-
- |
-
-
-cost |
-uint64 |
-The fee that would be charged to get the requested information (if a cost was requested). Note: This cost only includes the query fee and does not include the transfer fee(which is required to execute the transfer transaction to debit the payer account and credit the node account with query fee) |
-
-
-
-stateProof |
-bytes |
-The state proof for this information (if a state proof was requested, and is available) |
-
-
-
-
-
- |
-
-
-tokenInfo |
-TokenInfo |
-The information requested about this token instance |
-
-
-
- |
-
- The metadata about a Token instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-tokenId |
-TokenID |
-ID of the token instance |
-
-
-
- |
-
- Unique identifier for a token
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-A nonnegative shard number |
-
-
-
-realmNum |
-int64 |
-A nonnegative realm number |
-
-
-
-tokenNum |
-int64 |
-A nonnegative token number |
-
-
-
-
-
- |
-
-
-name |
-string |
-The name of the token. It is a string of ASCII only characters |
-
-
-
-symbol |
-string |
-The symbol of the token. It is a UTF-8 capitalized alphabetical string |
-
-
-
-decimals |
-uint32 |
-The number of decimal places a token is divisible by |
-
-
-
-totalSupply |
-uint64 |
-The total supply of tokens that are currently in circulation |
-
-
-
-treasury |
-AccountID |
-The ID of the account which is set as Treasury |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-adminKey |
-Key |
-The key which can perform update/delete operations on the token. If empty, the token can be perceived as immutable (not being able to be updated/deleted) |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-kycKey |
-Key |
-The key which can grant or revoke KYC of an account for the token's transactions. If empty, KYC is not required, and KYC grant or revoke operations are not possible. |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-freezeKey |
-Key |
-The key which can freeze or unfreeze an account for token transactions. If empty, freezing is not possible |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-wipeKey |
-Key |
-The key which can wipe token balance of an account. If empty, wipe is not possible |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-supplyKey |
-Key |
-The key which can change the supply of a token. The key is used to sign Token Mint/Burn operations |
-
-
-
- |
-
- A Key can be a public key from one of the three supported systems (ed25519, RSA-3072, ECDSA with p384). Or, it can be the ID of a smart contract instance, which is authorized to act as if it had a key. If an account has an ed25519 key associated with it, then the corresponding private key must sign any transaction to transfer cryptocurrency out of it. And similarly for RSA and ECDSA. A Key can be a smart contract ID, which means that smart contract is to authorize operations as if it had signed with a key that it owned. The smart contract doesn't actually have a key, and doesn't actually sign a transaction. But it's as if a virtual transaction were created, and the smart contract signed it with a private key. A key can be a "threshold key", which means a list of M keys, any N of which must sign in order for the threshold signature to be considered valid. The keys within a threshold signature may themselves be threshold signatures, to allow complex signature requirements. A Key can be a list of keys. Their use is dependent on context. For example, a Hedera file is created with a list of keys, where all of them must sign a transaction to create or modify the file, but only one of them is needed to sign a transaction to delete the file. So it's a single list that sometimes acts as a 1-of-M threshold key, and sometimes acts as an M-of-M threshold key. A Key can contain a ThresholdKey or KeyList, which in turn contain a Key, so this mutual recursion would allow nesting arbitrarily deep. A ThresholdKey which contains a list of primitive keys (e.g., ed25519) has 3 levels: ThresholdKey -> KeyList -> Key. A KeyList which contains several primitive keys (e.g., ed25519) has 2 levels: KeyList -> Key. A Key with 2 levels of nested ThresholdKeys has 7 levels: Key -> ThresholdKey -> KeyList -> Key -> ThresholdKey -> KeyList -> Key. Each Key should not have more than 46 levels, which implies 15 levels of nested ThresholdKeys.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-key |
-oneof |
- |
-
-
-
- |
-
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-contractID |
-ContractID |
-smart contract instance that is authorized as if it had signed with a key |
-
-
-
- |
-
- The ID for a smart contract instance
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-contractNum |
-int64 |
-A nonnegative number unique within its realm |
-
-
-
-
-
- |
-
-
-ed25519 |
-bytes |
-ed25519 public key bytes |
-
-
-
-RSA_3072 |
-bytes |
-RSA-3072 public key bytes |
-
-
-
-ECDSA_384 |
-bytes |
-ECDSA with the p-384 curve public key bytes |
-
-
-
-thresholdKey |
-ThresholdKey |
-a threshold N followed by a list of M keys, any N of which are required to form a valid signature |
-
-
-
- |
-
- A set of public keys that are used together to form a threshold signature. If the threshold is N and there are M keys, then this is an N of M threshold signature. If an account is associated with ThresholdKeys, then a transaction to move cryptocurrency out of it must be signed by a list of M signatures, where at most M-N of them are blank, and the other at least N of them are valid signatures corresponding to at least N of the public keys listed here.
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-threshold |
-uint32 |
-A valid signature set must have at least this many signatures |
-
-
-
-keys |
-KeyList |
-List of all the keys that can sign |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
-
- |
-
-
-keyList |
-KeyList |
-A list of Keys of the Key type. |
-
-
-
- |
-
- A list of keys
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-keys |
-Key (repeated) |
-list of keys |
-
-
-
- |
-
-Self Reference
- |
-
-
-
-
- |
-
-
-
- |
-
-
- |
-
-
-defaultFreezeStatus |
-TokenFreezeStatus |
-The default Freeze status (not applicable, frozen or unfrozen) of Hedera accounts relative to this token. FreezeNotApplicable is returned if Token Freeze Key is empty. Frozen is returned if Token Freeze Key is set and defaultFreeze is set to true. Unfrozen is returned if Token Freeze Key is set and defaultFreeze is set to false |
-
-
-
- |
-
- Possible Freeze statuses returned on TokenGetInfoQuery or CryptoGetInfoResponse in TokenRelationship
-
-
-
-Enum Name |
-Description |
-
-
-
-
-FreezeNotApplicable |
- |
-
-
-
-Frozen |
- |
-
-
-
-Unfrozen |
- |
-
-
-
-
-
- |
-
-
-defaultKycStatus |
-TokenKycStatus |
-The default KYC status (KycNotApplicable or Revoked) of Hedera accounts relative to this token. KycNotApplicable is returned if KYC key is not set, otherwise Revoked |
-
-
-
- |
-
- Possible KYC statuses returned on TokenGetInfoQuery or CryptoGetInfoResponse in TokenRelationship
-
-
-
-Enum Name |
-Description |
-
-
-
-
-KycNotApplicable |
- |
-
-
-
-Granted |
- |
-
-
-
-Revoked |
- |
-
-
-
-
-
- |
-
-
-isDeleted |
-bool |
-Specifies whether the token was deleted or not |
-
-
-
-autoRenewAccount |
-AccountID |
-An account which will be automatically charged to renew the token's expiration, at autoRenewPeriod interval |
-
-
-
- |
-
- The ID for an a cryptocurrency account
-
-
-
-Field |
-Type |
-Description |
-
-
-
-
-shardNum |
-int64 |
-The shard number (nonnegative) |
-
-
-
-realmNum |
-int64 |
-The realm number (nonnegative) |
-
-
-
-accountNum |
-int64 |
-A nonnegative account number unique within its realm |
-
-
-
-
-
- |
-
-
-autoRenewPeriod |
-uint64 |
-The interval at which the auto-renew account will be charged to extend the token's expiry |
-
-
-
-expiry |
-uint64 |
-The epoch second at which the token will expire; if an auto-renew account and period are specified, this is coerced to the current epoch second plus the autoRenewPeriod |
-
-
-
-
-
- |
-
-
-
-
- |
-
-
-
- |