Protocol Documentation

The Account ID that sends/receives cryptocurrency or tokens

The amount of tinybars (for Crypto transfers) or in the lowest denomination (for Token transfers) that the account sends(negative) or receives(positive)

If true then the transfer is expected to be an approved allowance and the accountID is expected to be the owner. The default is false (omitted).

The shard number (nonnegative)

The realm number (nonnegative)

A non-negative account number unique within its realm

The public key bytes to be used as the account's alias. The public key bytes are the result of serializing a protobuf Key message for any primitive key type. Currently only primitive key bytes are supported as an alias (ThresholdKey, KeyList, ContractID, and delegatable_contract_id are not supported) At most one account can ever have a given alias and it is used for account creation if it was automatically created using a crypto transfer. It will be null if an account is created normally. It is immutable once it is set for an account. If a transaction auto-creates the account, any further transfers to that alias will simply be deposited in that account, without creating anything, and with no creation fee being charged.

The ethereum account 20-byte EVM address to be used initially in place of the public key bytes. This EVM address may be either the encoded form of the shard.realm.num or the keccak-256 hash of a ECDSA_SECP256K1 primitive key. If a transaction lazily-creates this account, a subsequent transaction will be required containing the public key bytes that map to the EVM address bytes. Lazy account creates will only support the keccak-256 hash of a ECDSA_SECP256K1 primitive key form.

The shard number (nonnegative)

The realm number (nonnegative)

A nonnegative number unique within a given shard and realm

The 20-byte EVM address of the contract to call. Every contract has an EVM address determined by its <tt>shard.realm.num</tt> id. This address is as follows: <ol> <li>The first 4 bytes are the big-endian representation of the shard.</li> <li>The next 8 bytes are the big-endian representation of the realm.</li> <li>The final 8 bytes are the big-endian representation of the number.</li> </ol> Contracts created via CREATE2 have an <b>additional, primary address</b> that is derived from the <a href="https://eips.ethereum.org/EIPS/eip-1014">EIP-1014</a> specification, and does not have a simple relation to a <tt>shard.realm.num</tt> id. (Please do note that CREATE2 contracts can also be referenced by the three-part EVM address described above.)

Contains current Fee Schedule

Contains next Fee Schedule

A minimum, the calculated fee must be greater than this value

A maximum, the calculated fee must be less than this value

A constant contribution to the fee

The price of bandwidth consumed by a transaction, measured in bytes

The price per signature verification for a transaction

The price of RAM consumed by a transaction, measured in byte-hours

The price of storage consumed by a transaction, measured in byte-hours

The price of computation for a smart contract transaction, measured in gas

The price per hbar transferred for a transfer

The price of bandwidth for data retrieved from memory for a response, measured in bytes

The price of bandwidth for data retrieved from disk for a response, measured in bytes

Fee paid to the submitting node

Fee paid to the network for processing a transaction into consensus

Fee paid to the network for providing the service associated with the transaction; for instance, storing a file

SubType distinguishing between different types of FeeData, correlating to the same HederaFunctionality

List of price coefficients for network resources

FeeSchedule expiry time

The shard number (nonnegative)

The realm number (nonnegative)

A nonnegative File number unique within its realm

The rational's numerator

The rational's denominator; a zero value will result in FRACTION_DIVIDES_BY_ZERO

smart contract instance that is authorized as if it had signed with a key

Ed25519 public key bytes

(NOT SUPPORTED) RSA-3072 public key bytes

(NOT SUPPORTED) ECDSA with the p-384 curve public key bytes

a threshold N followed by a list of M keys, any N of which are required to form a valid signature

A list of Keys of the Key type.

Compressed ECDSA(secp256k1) public key bytes

A smart contract that, if the recipient of the active message frame, should be treated as having signed. (Note this does not mean the <i>code being executed in the frame</i> will belong to the given contract, since it could be running another contract's code via <tt>delegatecall</tt>. So setting this key is a more permissive version of setting the contractID key, which also requires the code in the active message frame belong to the the contract with the given id.)

list of keys

The accountID of the sender

The accountID of the receiver

The serial number of the NFT

If true then the transfer is expected to be an approved allowance and the senderAccountID is expected to be the owner. The default is false (omitted).

Deprecated. The IP address of the Node with separator & octets encoded in UTF-8. Usage is deprecated, ServiceEndpoint is preferred to retrieve a node's list of IP addresses and ports

Deprecated. The port number of the grpc server for the node. Usage is deprecated, ServiceEndpoint is preferred to retrieve a node's list of IP addresses and ports

Deprecated. Usage is deprecated, nodeAccountId is preferred to retrieve a node's account ID

The node's X509 RSA public key used to sign stream files (e.g., record stream files). Precisely, this field is a string of hexadecimal characters which, translated to binary, are the public key's DER encoding.

# A non-sequential identifier for the node

# The account to be paid for queries and transactions sent to this node

# Hash of the node's TLS certificate. Precisely, this field is a string of hexadecimal characters which, translated to binary, are the SHA-384 hash of the UTF-8 NFKD encoding of the node's TLS cert in PEM format. Its value can be used to verify the node's certificate it presents during TLS negotiations.

# A node's service IP addresses and ports

A description of the node, with UTF-8 encoding up to 100 bytes

Deprecated. [Deprecated] The amount of tinybars staked to the node

Metadata of all nodes in the network

The shard number (nonnegative)

The realm number (nonnegative)

A nonnegative shard number

A nonnegative realm number

A nonnegative schedule number

Increases with incompatible API changes

Increases with backwards-compatible new functionality

Increases with backwards-compatible bug fixes

A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers (https://semver.org/#spec-item-9); so given a semver 0.14.0-alpha.1+21AF26D3, this field would contain 'alpha.1'

Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version (https://semver.org/#spec-item-10); so given a semver 0.14.0-alpha.1+21AF26D3, this field would contain '21AF26D3'

The 32-bit IPv4 address of the node encoded in left to right order (e.g. 127.0.0.1 has 127 as its first byte)

The port of the node

list of name value pairs of the application properties

name of the property

value of the property

any data associated with property

the shard number (nonnegative)

smart contract virtual signature (always length zero)

ed25519 signature bytes

RSA-3072 signature bytes

ECDSA p-384 signature bytes

A list of signatures for a single N-of-M threshold Key. This must be a list of exactly M signatures, at least N of which are non-null.

A list of M signatures, each corresponding to a Key in a KeyList of the same length.

each signature corresponds to a Key in the KeyList

Each signature pair corresponds to a unique Key required to sign the transaction.

First few bytes of the public key

smart contract virtual signature (always length zero)

ed25519 signature

RSA-3072 signature

ECDSA p-384 signature

ECDSA(secp256k1) signature

If true, this account or contract declined to receive a staking reward.

The staking period during which either the staking settings for this account or contract changed (such as starting staking or changing staked_node_id) or the most recent reward was earned, whichever is later. If this account or contract is not currently staked to a node, then this field is not set.

The amount in tinybars that will be received in the next reward situation.

The total of balance of all accounts staked to this account or contract.

The account to which this account or contract is staking.

The ID of the node this account or contract is staked to.

A valid signature set must have at least this many signatures

List of all the keys that can sign

for an N-of-M threshold key, this is a list of M signatures, at least N of which must be non-null

The token involved in the association

The account involved in the association

A unique token id

Number of transferable units of the identified token. For token of type FUNGIBLE_COMMON - balance in the smallest denomination. For token of type NON_FUNGIBLE_UNIQUE - the number of NFTs held by the account

Tokens divide into <tt>10^decimals</tt> pieces

A nonnegative shard number

A nonnegative realm number

A nonnegative token number

The ID of the token

The Symbol of the token

For token of type FUNGIBLE_COMMON - the balance that the Account holds in the smallest denomination. For token of type NON_FUNGIBLE_UNIQUE - the number of NFTs held by the account

The KYC status of the account (KycNotApplicable, Granted or Revoked). If the token does not have KYC key, KycNotApplicable is returned

The Freeze status of the account (FreezeNotApplicable, Frozen or Unfrozen). If the token does not have Freeze key, FreezeNotApplicable is returned

Tokens divide into <tt>10^decimals</tt> pieces

Specifies if the relationship is created implicitly. False : explicitly associated, True : implicitly associated.

The ID of the token

Applicable to tokens of type FUNGIBLE_COMMON. Multiple list of AccountAmounts, each of which has an account and amount

Applicable to tokens of type NON_FUNGIBLE_UNIQUE. Multiple list of NftTransfers, each of which has a sender and receiver account, including the serial number of the NFT

If present, the number of decimals this fungible token type is expected to have. The transfer will fail with UNEXPECTED_TOKEN_DECIMALS if the actual decimals differ.

The shard number (nonnegative)

The realm number (nonnegative)

Unique topic identifier within a realm (nonnegative).

A particular transaction or query

Deprecated. Resource price coefficients

Resource price coefficients. Supports subtype price definition.

The transaction is invalid if consensusTimestamp < transactionID.transactionStartValid

The Account ID that paid for this transaction

Whether the Transaction is of type Scheduled or no

The identifier for an internal transaction that was spawned as part of handling a user transaction. (These internal transactions share the transactionValidStart and accountID of the user transaction, so a nonce is necessary to give them a unique TransactionID.) An example is when a "parent" ContractCreate or ContractCall transaction calls one or more HTS precompiled contracts; each of the "child" transactions spawned for a precompile has a id with a different nonce.

Multiple list of AccountAmount pairs, each of which has an account and an amount to transfer into it (positive) or out of it (negative)

The 20-byte EVM address that is derived from the keccak-256 hash of a ECDSA_SECP256K1 primitive key.

Flag if this address should now be set or is the default address on the account.

Short publicly visible memo about the topic. No guarantee of uniqueness.

Access control for updateTopic/deleteTopic. Anyone can increase the topic's expirationTime via ConsensusService.updateTopic(), regardless of the adminKey. If no adminKey is specified, updateTopic may only be used to extend the topic's expirationTime, and deleteTopic is disallowed.

Access control for submitMessage. If unspecified, no access control is performed on ConsensusService.submitMessage (all submissions are allowed).

The initial lifetime of the topic and the amount of time to attempt to extend the topic's lifetime by automatically at the topic's expirationTime, if the autoRenewAccount is configured (once autoRenew functionality is supported by HAPI). Limited to MIN_AUTORENEW_PERIOD and MAX_AUTORENEW_PERIOD value by server-side configuration. Required.

Optional account to be used at the topic's expirationTime to extend the life of the topic (once autoRenew functionality is supported by HAPI). The topic lifetime will be extended up to a maximum of the autoRenewPeriod or however long the topic can be extended using all funds on the account (whichever is the smaller duration/amount and if any extension is possible with the account's funds). If specified, there must be an adminKey and the autoRenewAccount must sign this transaction.

Topic identifier

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The Topic for which information is being requested

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither.

Topic identifier.

Current state of the topic

TransactionID of the first chunk, gets copied to every subsequent chunk in a fragmented message.

The total number of chunks in the message.

The sequence number (from 1 to total) of the current chunk in the message.

Topic to submit message to.

Message to be submitted. Max size of the Transaction (including signatures) is 6KiB.

Optional information of the current chunk in a fragmented message.

The memo associated with the topic (UTF-8 encoding max 100 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.

Sequence number (starting at 1 for the first submitMessage) of messages on the topic.

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.

Access control for update/delete of the topic. Null if there is no key.

Access control for ConsensusService.submitMessage. Null if there is no key.

If an auto-renew account is specified, when the topic expires, its lifetime will be extended by up to this duration (depending on the solvency of the auto-renew account). If the auto-renew account has no funds at all, the topic will be deleted instead.

The account, if any, to charge for automatic renewal of the topic's lifetime upon expiry.

The ledger ID the response was returned from; please see <a href="https://github.com/hashgraph/hedera-improvement-proposal/blob/master/HIP/hip-198.md">HIP-198</a> for the network-specific IDs.

UNDOCUMENTED

If set, the new memo to be associated with the topic (UTF-8 encoding max 100 bytes)

Effective consensus timestamp at (and after) which all consensus transactions and queries will fail. The expirationTime may be no longer than MAX_AUTORENEW_PERIOD (8000001 seconds) from the consensus timestamp of this transaction. On topics with no adminKey, extending the expirationTime is the only updateTopic option allowed on the topic. If unspecified, no change.

Access control for update/delete of the topic. If unspecified, no change. If empty keyList - the adminKey is cleared.

Access control for ConsensusService.submitMessage. If unspecified, no change. If empty keyList - the submitKey is cleared.

The amount of time to extend the topic's lifetime automatically at expirationTime if the autoRenewAccount is configured and has funds (once autoRenew functionality is supported by HAPI). Limited to between MIN_AUTORENEW_PERIOD (6999999 seconds) and MAX_AUTORENEW_PERIOD (8000001 seconds) by servers-side configuration (which may change). If unspecified, no change.

Optional account to be used at the topic's expirationTime to extend the life of the topic. Once autoRenew functionality is supported by HAPI, the topic lifetime will be extended up to a maximum of the autoRenewPeriod or however long the topic can be extended using all funds on the account (whichever is the smaller duration/amount). If specified as the default value (0.0.0), the autoRenewAccount will be removed. If unspecified, no change.

The contract to call

the maximum amount of gas to use for the call

number of tinybars sent (the function must be payable if this is nonzero)

which function to call, and the parameters to pass to the function

standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither). The payment must cover the fees and all of the gas offered.

The contract to make a static call against

The amount of gas to use for the call; all of the gas offered will be used and charged a corresponding fee

which function to call, and the parameters to pass to the function

Deprecated. max number of bytes that the result might include. The run will fail if it would have returned more than this number of bytes.

The account that is the "sender." If not present it is the accountId from the transactionId. Typically a different value than specified in the transactionId requires a valid signature over either the hedera transaction or foreign transaction data.

standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

the value returned by the function (if it completed and didn't fail)

the smart contract instance whose function was called

the result returned by the function

message In case there was an error during smart contract execution

bloom filter for record

units of gas used to execute contract

the log info for events returned by the function

Deprecated. [DEPRECATED] the list of smart contracts that were created by the function call. The created ids will now _also_ be externalized through internal transaction records, where each record has its alias field populated with the new contract's EVM address. (This is needed for contracts created with CREATE2, since there is no longer a simple relationship between the new contract's 0.0.X id and its Solidity address.)

The new contract's 20-byte EVM address. Only populated after release 0.23, where each created contract will have its own record. (This is an important point--the field is not <tt>repeated</tt> because there will be a separate child record for each created contract.) Every contract has an EVM address determined by its <tt>shard.realm.num</tt> id. This address is as follows: <ol> <li>The first 4 bytes are the big-endian representation of the shard.</li> <li>The next 8 bytes are the big-endian representation of the realm.</li> <li>The final 8 bytes are the big-endian representation of the number.</li> </ol> Contracts created via CREATE2 have an <b>additional, primary address</b> that is derived from the <a href="https://eips.ethereum.org/EIPS/eip-1014">EIP-1014</a> specification, and does not have a simple relation to a <tt>shard.realm.num</tt> id. (Please do note that CREATE2 contracts can also be referenced by the three-part EVM address described above.)

The amount of gas available for the call, aka the gasLimit. This field should only be populated when the paired TransactionBody in the record stream is not a ContractCreateTransactionBody or a ContractCallTransactionBody.

Number of tinybars sent (the function must be payable if this is nonzero). This field should only be populated when the paired TransactionBody in the record stream is not a ContractCreateTransactionBody or a ContractCallTransactionBody.

The parameters passed into the contract call. This field should only be populated when the paired TransactionBody in the record stream is not a ContractCreateTransactionBody or a ContractCallTransactionBody.

The account that is the "sender." If not present it is the accountId from the transactionId. This field should only be populated when the paired TransactionBody in the record stream is not a ContractCreateTransactionBody or a ContractCallTransactionBody.

address of a contract that emitted the event

bloom filter for a particular log

topics of a particular event

event data

The file containing the smart contract initcode. A copy will be made and held by the contract instance, and have the same expiration time as the instance.

The bytes of the smart contract initcode. This is only useful if the smart contract init is less than the hedera transaction limit. In those cases fileID must be used.

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.

gas to run the constructor

initial number of tinybars to put into the cryptocurrency account associated with and owned by the smart contract

Deprecated. [Deprecated] ID of the account to which this account 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 instance will charge its account every this many seconds to renew for this long

parameters to pass to the constructor

shard in which to create this

realm in which to create this (leave this null to create a new realm)

if realmID is null, then this the admin key for the new realm that will be created

the memo that was submitted as part of the contract (max 100 bytes)

The maximum number of tokens that this contract can be automatically associated with (i.e., receive air-drops from).

An account to charge for auto-renewal of this contract. If not set, or set to an account with zero hbar balance, the contract's own hbar balance will be used to cover auto-renewal fees.

ID of the account to which this contract is staking.

ID of the node this contract is staked to.

If true, the contract declines receiving a staking reward. The default value is false.

The id of the contract to be deleted

The id of an account to receive any remaining hBars from the deleted contract

The id of a contract to receive any remaining hBars from the deleted contract

If set to true, means this is a "synthetic" system transaction being used to alert mirror nodes that the contract is being permanently removed from the ledger. <b>IMPORTANT:</b> User transactions cannot set this field to true, as permanent removal is always managed by the ledger itself. Any ContractDeleteTransactionBody submitted to HAPI with permanent_removal=true will be rejected with precheck status PERMANENT_REMOVAL_REQUIRES_SYSTEM_INITIATION.

standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

the contract for which information is requested

standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

the runtime bytecode of the contract

standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

the contract for which information is requested

standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

the information about this contract instance (a state proof can be generated for this)

ID of the contract instance, in the format used in transactions

ID of the cryptocurrency account owned by the contract instance, in the format used in transactions

ID of both the contract instance and the cryptocurrency account owned by the contract instance, in the format used by Solidity

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.

the current time at which this contract instance (and its account) is set to expire

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.

number of bytes of storage being used by this instance (which affects the cost to extend the expiration time)

the memo associated with the contract (max 100 bytes)

The current balance, in tinybars

Whether the contract has been deleted

Deprecated. [DEPRECATED] The metadata of the tokens associated to the contract. This field was deprecated by <a href="https://hips.hedera.com/hip/hip-367">HIP-367</a>, which allowed an account to be associated to an unlimited number of tokens. This scale makes it more efficient for users to consult mirror nodes to review their token associations.

The ledger ID the response was returned from; please see <a href="https://github.com/hashgraph/hedera-improvement-proposal/blob/master/HIP/hip-198.md">HIP-198</a> for the network-specific IDs.

ID of the an account to charge for auto-renewal of this contract. If not set, or set to an account with zero hbar balance, the contract's own hbar balance will be used to cover auto-renewal fees.

The maximum number of tokens that a contract can be implicitly associated with.

Staking metadata for this contract.

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The smart contract instance for which the records should be retrieved

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The smart contract instance that this record is for

List of records, each with contractCreateResult or contractCallResult as its body

The id of the contract to be updated

The new expiry of the contract, no earlier than the current expiry (resolves to EXPIRATION_REDUCTION_NOT_ALLOWED otherwise)

The new key to control updates to the contract

Deprecated. [Deprecated] The new id of the account to which the contract is proxy staked

If an auto-renew account is in use, the lifetime to be added by each auto-renewal.

Deprecated. This field is unused and will have no impact on the specified smart contract.

Deprecated. [Deprecated] If set with a non-zero length, the new memo to be associated with the account (UTF-8 encoding max 100 bytes)

If set, the new memo to be associated with the account (UTF-8 encoding max 100 bytes)

If set, the new maximum number of tokens that this contract can be automatically associated with (i.e., receive air-drops from).

If set to the sentinel <tt>0.0.0</tt> AccountID, this field removes the contract's auto-renew account. Otherwise it updates the contract's auto-renew account to the referenced account.

ID of the new account to which this contract is staking. If set to the sentinel <tt>0.0.0</tt> AccountID, this field removes the contract's staked account ID.

ID of the new node this contract is staked to. If set to the sentinel <tt>-1</tt>, this field removes the contract's staked node ID.

If true, the contract declines receiving a staking reward.

A hash of some credential or certificate, along with the keys of the entities that asserted it validity

The account to which the livehash is attached

The SHA-384 hash of a credential or certificate

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.

The duration for which the livehash will remain valid

List of hbar allowances approved by the account owner.

List of non-fungible token allowances approved by the account owner.

List of fungible token allowances approved by the account owner.

The account ID of the hbar owner (ie. the grantor of the allowance).

The account ID of the spender of the hbar allowance.

The amount of the spender's allowance in tinybars.

List of hbar allowances approved by the account owner.

List of non-fungible token allowances approved by the account owner.

List of fungible token allowances approved by the account owner.

The NFT token type that the allowance pertains to.

The account ID of the token owner (ie. the grantor of the allowance).

The account ID of the token allowance spender.

The list of serial numbers that the spender is permitted to transfer.

If true, the spender has access to all of the owner's NFT units of type tokenId (currently owned and any in the future).

The account ID of the spender who is granted approvedForAll allowance and granting approval on an NFT serial to another spender.

The token that the allowance pertains to.

The account ID of the token owner (ie. the grantor of the allowance).

The account ID of the token allowance spender.

The amount of the spender's token allowance.

The key that must sign each transfer out of the account. If receiverSigRequired is true, then it must also sign any transfer into the account.

The initial number of tinybars to put into the account

Deprecated. [Deprecated] ID of the account to which this account 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.

Deprecated. [Deprecated]. The threshold amount (in tinybars) for which an account record is created for any send/withdraw transaction

Deprecated. [Deprecated]. The threshold amount (in tinybars) for which an account record is created for any receive/deposit transaction

If true, this account's key must sign any transaction depositing into this account (in addition to all withdrawals)

The account is charged to extend its expiration date every this many seconds. If it doesn't have enough balance, it extends as long as possible. If it is empty when it expires, then it is deleted.

The shard in which this account is created

The realm in which this account is created (leave this null to create a new realm)

If realmID is null, then this the admin key for the new realm that will be created

The memo associated with the account (UTF-8 encoding max 100 bytes)

The maximum number of tokens that an Account can be implicitly associated with. Defaults to 0 and up to a maximum value of 1000.

ID of the account to which this account is staking.

ID of the node this account is staked to.

If true, the account declines receiving a staking reward. The default value is false.

The bytes to be used as the account's alias. It will be the serialization of a protobuf Key message for an ED25519/ECDSA_SECP256K1 primitive key type. Currently only primitive key bytes are supported as the key for an account with an alias. ThresholdKey, KeyList, ContractID, and delegatable_contract_id are not supported. A given alias can map to at most one account on the network at a time. This uniqueness will be enforced relative to aliases currently on the network at alias assignment. If a transaction creates an account using an alias, any further crypto transfers to that alias will simply be deposited in that account, without creating anything, and with no creation fee being charged.

An account to charge for auto-renewal of this account . If not set, or set to an account with zero hbar balance, the account's own hbar balance will be used to cover auto-renewal fees.

EOA 20-byte address to create that is derived from the keccak-256 hash of a ECDSA_SECP256K1 primitive key.

The account ID which will receive all remaining hbars

The account ID which should be deleted

List of non-fungible token allowances to remove.

The token that the allowance pertains to.

The account ID of the token owner (ie. the grantor of the allowance).

The list of serial numbers to remove allowances from.

The account owning the livehash

The SHA-384 livehash to delete from the account

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The account ID for which information is requested

The account ID for which information is requested

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither.

The account ID that is being described (this is useful with state proofs, for proving to a third party)

The current balance, in tinybars.

Deprecated. [DEPRECATED] The balances of the tokens associated to the account. This field was deprecated by <a href="https://hips.hedera.com/hip/hip-367">HIP-367</a>, which allowed an account to be associated to an unlimited number of tokens. This scale makes it more efficient for users to consult mirror nodes to review their token balances.

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The account ID for which the records should be retrieved

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The account that this record is for

List of records

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The account ID for which information is requested

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

Info about the account (a state proof can be generated for this)

The account ID for which this information applies

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

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

Deprecated. [Deprecated] 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 total number of tinybars proxy staked to this account

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.

The current balance of account in tinybars

Deprecated. [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

Deprecated. [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

If true, no transaction can transfer to this account unless signed by this account's key

The TimeStamp time at which this account is set to expire

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.

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)

Deprecated. [DEPRECATED] The metadata of the tokens associated to the account. This field was deprecated by <a href="https://hips.hedera.com/hip/hip-367">HIP-367</a>, which allowed an account to be associated to an unlimited number of tokens. This scale makes it more efficient for users to consult mirror nodes to review their token associations.

The memo associated with the account

The number of NFTs owned by this account

The maximum number of tokens that an Account can be implicitly associated with.

The alias of this account

The ledger ID the response was returned from; please see <a href="https://github.com/hashgraph/hedera-improvement-proposal/blob/master/HIP/hip-198.md">HIP-198</a> for the network-specific IDs.

The ethereum transaction nonce associated with this account.

Staking metadata for this account.

If present, the account that will be charged for auto-renewal of this account. If not set, or set to an account with zero hbar balance, the account's own hbar balance will be used to cover auto-renewal fees.

List of virtual addresses each of which is an EVM address that maps to an ECDSA key pair a user must prove ownership of.

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The account to which the livehash is associated

The SHA-384 data in the livehash

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The livehash, if present

The Account ID that is being proxy staked to

Each of the proxy staking accounts, and the amount they are proxy staking

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The Account ID for which the records should be retrieved

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

List of accounts proxy staking to this account, and the amount each is currently proxy staking

The Account ID that is proxy staking

The number of hbars that are currently proxy staked

The desired hbar balance adjustments

The desired token unit balance adjustments; if any custom fees are assessed, the ledger will try to deduct them from the payer of this CryptoTransfer, resolving the transaction to INSUFFICIENT_PAYER_BALANCE_FOR_CUSTOM_FEE if this is not possible

The account ID which is being updated in this transaction

The new key

Deprecated. [Deprecated] ID of the account to which this account 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.

Deprecated. [Deprecated]. Payments earned from proxy staking are shared between the node and this account, with proxyFraction / 10000 going to this account

Deprecated. [Deprecated]. The new threshold amount (in tinybars) for which an account record is created for any send/withdraw transaction

Deprecated. [Deprecated]. The new threshold amount (in tinybars) for which an account record is created for any send/withdraw transaction

Deprecated. [Deprecated]. The new threshold amount (in tinybars) for which an account record is created for any receive/deposit transaction.

Deprecated. [Deprecated]. The new threshold amount (in tinybars) for which an account record is created for any receive/deposit transaction.

The duration in which it will automatically extend the expiration period. If it doesn't have enough balance, it extends as long as possible. If it is empty when it expires, then it is deleted.

The new expiration time to extend to (ignored if equal to or before the current one)

Deprecated. [Deprecated] Do NOT use this field to set a false value because the server cannot distinguish from the default value. Use receiverSigRequiredWrapper field for this purpose.

If true, this account's key must sign any transaction depositing into this account (in addition to all withdrawals)

If set, the new memo to be associated with the account (UTF-8 encoding max 100 bytes)

The maximum number of tokens that an Account can be implicitly associated with. Up to a 1000 including implicit and explicit associations.

ID of the new account to which this account is staking. If set to the sentinel <tt>0.0.0</tt> AccountID, this field removes this account's staked account ID.

ID of the new node this account is staked to. If set to the sentinel <tt>-1</tt>, this field removes this account's staked node ID.

If true, the account declines receiving a staking reward. The default value is false.

If set to the sentinel <tt>0.0.0</tt> AccountID, this field removes the account's auto-renew account. Otherwise it updates the account's auto-renew account to the referenced account.

The virtual address to be added.

The 20-byte EVM address of the virtual address that is being removed.

The number of units assessed for the fee

The denomination of the fee; taken as hbar if left unset

The account to receive the assessed fee

The account(s) whose final balances would have been higher in the absence of this assessed fee

Fixed fee to be charged

Fractional fee to be charged

Royalty fee to be charged

The account to receive the custom fee

If true, exempts all the token's fee collection accounts from this fee. (The token's treasury and the above fee_collector_account_id will always be exempt. Please see <a href="https://hips.hedera.com/hip/hip-573">HIP-573</a> for details.)

The number of units to assess as a fee

The denomination of the fee; taken as hbar if left unset and, in a TokenCreate, taken as the id of the newly created token if set to the sentinel value of 0.0.0

The fraction of the transferred units to assess as a fee

The minimum amount to assess

The maximum amount to assess (zero implies no maximum)

If true, assesses the fee to the sender, so the receiver gets the full amount from the token transfer list, and the sender is charged an additional fee; if false, the receiver does NOT get the full amount, but only what is left over after paying the fractional fee

The fraction of fungible value exchanged for an NFT to collect as royalty

If present, the fixed fee to assess to the NFT receiver when no fungible value is exchanged with the sender

The number of seconds

The raw Ethereum transaction (RLP encoded type 0, 1, and 2). Complete unless the callData field is set.

For large transactions (for example contract create) this is the callData of the ethereumData. The data in the ethereumData will be re-written with the callData element as a zero length string with the original contents in the referenced file at time of execution. The ethereumData will need to be "rehydrated" with the callData for signature validation to pass.

The maximum amount, in tinybars, that the payer of the hedera transaction is willing to pay to complete the transaction. Ordinarily the account with the ECDSA alias corresponding to the public key that is extracted from the ethereum_data signature is responsible for fees that result from the execution of the transaction. If that amount of authorized fees is not sufficient then the payer of the transaction can be charged, up to but not exceeding this amount. If the ethereum_data transaction authorized an amount that was insufficient then the payer will only be charged the amount needed to make up the difference. If the gas price in the transaction was set to zero then the payer will be assessed the entire fee.

Denominator in calculation of exchange rate between hbar and cents

Numerator in calculation of exchange rate between hbar and cents

Expiration time in seconds for this exchange rate

Current exchange rate

Next exchange rate which will take effect when current rate expires

The file to which the bytes will be appended

The bytes that will be appended to the end of the specified file

The time at which this file should expire (unless FileUpdateTransaction is used before then to extend its life)

All keys at the top level of a key list must sign to create or modify the file. Any one of the keys at the top level key list can sign to delete the file.

The bytes that are the contents of the file

Shard in which this file is created

The Realm in which to the file is created (leave this null to create a new realm)

If realmID is null, then this the admin key for the new realm that will be created

The memo associated with the file (UTF-8 encoding max 100 bytes)

An account to charge for auto-renewal of this file. If not set, or set to an account with zero hbar balance, the file's expiration must be manually extended using a FileUpdate transaction, since the network will not have authorization for any kind of auto-renewal fee collection.

If an auto-renew account is in use, the lifetime to be added by each auto-renewal. When both auto-renew account and auto-renew period are set in the create transaction, the initial expiry of the file will be the valid start of the create transaction plus the auto-renew period. (I.e., the expirationTime field will be ignored.)

The file to delete. It will be marked as deleted until it expires. Then it will disappear.

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The file ID of the file whose contents are requested

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

the file ID and contents (a state proof can be generated for this)

The file ID of the file whose contents are being returned

The bytes contained in the file

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The file ID of the file for which information is requested

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The information about the file

The file ID of the file for which information is requested

Number of bytes in contents

The current time at which this account is set to expire

True if deleted but not yet expired

One of these keys must sign in order to modify or delete the file

The memo associated with the file

The ledger ID the response was returned from; please see <a href="https://github.com/hashgraph/hedera-improvement-proposal/blob/master/HIP/hip-198.md">HIP-198</a> for the network-specific IDs.

If set, the account that is used to pay for auto-renewal of the file.

If an auto-renew account is in use, the added lifetime (in seconds) of each auto-renewal.

The ID of the file to update

The new expiry time (ignored if not later than the current expiry)

The new list of keys that can modify or delete the file

The new contents that should overwrite the file's current contents

If set, the new memo to be associated with the file (UTF-8 encoding max 100 bytes)

If set to the sentinel <tt>0.0.0</tt> AccountID, this field removes the file's auto-renew account. Otherwise it updates the file's auto-renew account to the referenced account.

If an auto-renew account is in use, the lifetime to be added by each auto-renewal.

Deprecated. !! DEPRECATED and REJECTED by nodes The start hour (in UTC time), a value between 0 and 23

Deprecated. !! DEPRECATED and REJECTED by nodes The start minute (in UTC time), a value between 0 and 59

Deprecated. !! DEPRECATED and REJECTED by nodes The end hour (in UTC time), a value between 0 and 23

Deprecated. !! DEPRECATED and REJECTED by nodes The end minute (in UTC time), a value between 0 and 59

If set, the file whose contents should be used for a network software update during the maintenance window.

If set, the expected hash of the contents of the update file (used to verify the update).

The consensus time at which the maintenance window should begin.

The type of network freeze or upgrade operation to perform.

Account details sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The account ID for which information is requested

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

Details of the account (a state proof can be generated for this)

The account ID for which this information applies

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

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

Deprecated. [Deprecated] 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 total number of tinybars proxy staked to this account

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.

The current balance of account in tinybars

If true, no transaction can transfer to this account unless signed by this account's key

The TimeStamp time at which this account is set to expire

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.

All tokens related to this account

The memo associated with the account

The number of NFTs owned by this account

The maximum number of tokens that an Account can be implicitly associated with.

The alias of this account

The ledger ID the response was returned from; please see <a href="https://github.com/hashgraph/hedera-improvement-proposal/blob/master/HIP/hip-198.md">HIP-198</a> for the network-specific IDs.

All of the hbar allowances approved by the account owner.

All of the non-fungible token allowances approved by the account owner.

All of the fungible token allowances approved by the account owner.

The account ID of the spender of the hbar allowance.

The amount of the spender's allowance in tinybars.

The token that the allowance pertains to.

The account ID of the spender that has been granted access to all NFTs of the owner

The token that the allowance pertains to.

The account ID of the token allowance spender.

The amount of the spender's token allowance.

The Account ID for the cryptocurrency account

A uniquely identifying livehash of an acount

The file ID of the file

The smart contract ID that identifies instance

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The key to search for. It must not contain a contractID nor a ThresholdSignature.

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The list of entities that include this public key in their associated Key list

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The ID in the format used by Solidity

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The Account ID for the cryptocurrency account

The file Id for the file

A smart contract ID for the instance (if this is included, then the associated accountID will also be included)

standard info sent from client to node including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

The id(s) of the transactions to get the execution time(s) of

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The execution time(s) of the requested TransactionIDs, if available

Standard info sent from client to node, including the signed payment, and what kind of response is requested (cost, state proof, both, or neither).

Standard response from node to client, including the requested fields: cost, or state proof, or both, or neither

The Hedera API (HAPI) protobuf version recognized by the responding node.

The version of the Hedera Services software deployed on the responding node.

The maximum stake (rewarded or not rewarded) this node can have as consensus weight. If its stake to reward is above this maximum at the start of a period, then accounts staking to the node in that period will be rewarded at a lower rate scaled by (maxStake / stakeRewardStart).

The minimum stake (rewarded or not rewarded) this node must reach before having non-zero consensus weight. If its total stake is below this minimum at the start of a period, then accounts staking to the node in that period will receive no rewards.

The id of this node.

The reward rate _per whole hbar_ that was staked to this node with declineReward=false from the start of the staking period that is ending.

Consensus weight of this node for the new staking period.

Total of (balance + stakedToMe) for all accounts staked to this node with declineReward=true, at the beginning of the new staking period.

Total of (balance + stakedToMe) for all accounts staked to this node with declineReward=false, at the beginning of the new staking period.

Time and date of the end of the staking period that is ending

Staking info of each node at the beginning of the new staking period

The maximum reward rate, in tinybars per whole hbar, that any account can receive in a day.

The fraction of the network and service fees paid to the node reward account 0.0.801.

The maximum number of trailing periods for which a user can collect rewards. For example, if this is 365 with a UTC calendar day period, then users must collect rewards at least once per calendar year to avoid missing any value.

The number of minutes in a staking period. Note for the special case of 1440 minutes, periods are treated as UTC calendar days, rather than repeating 1440 minute periods left-aligned at the epoch.

The fraction of the network and service fees paid to the staking reward account 0.0.800.

The minimum balance of staking reward account 0.0.800 required to active rewards.

The total number of tinybars to be distributed as staking rewards each period.

If provided and is positive, returns a 32-bit pseudorandom number from the given range in the transaction record. If not set or set to zero, will return a 384-bit pseudorandom number in the record.

Get all entities associated with a given key

Get the IDs in the format used in transactions, given the format used in Solidity

Call a function of a smart contract instance

Get information about a smart contract instance

Get runtime code used by a smart contract instance

Get Records of the contract instance

Get the current balance in a cryptocurrency account

Get all the records that currently exist for transactions involving an account

Get all information about an account

Get a single livehash from a single account, if present

Get all the accounts that proxy stake to a given account, and how much they proxy stake (not yet implemented in the current API)

Get the contents of a file (the bytes stored in it)

Get information about a file, such as its expiration date

Get a receipt for a transaction (lasts 180 seconds)

Get a record for a transaction

Get a record for a transaction (lasts 180 seconds)

Get the parameters of and state of a consensus topic.

Get the versions of the HAPI protobuf and Hedera Services software deployed on the responding node.

Get all information about a token

Get all information about a scheduled entity

Get a list of NFTs associated with the account

Get all information about a NFT

Get a list of NFTs for the token

Gets <tt>handleTransaction</tt> times for one or more "sufficiently recent" TransactionIDs

Gets all information about an account including allowances granted by the account

A signed CryptoTransferTransaction to pay the node a fee for handling this query

The requested response, asking for cost, state proof, both, or neither

Get all entities associated with a given key

Get the IDs in the format used in transactions, given the format used in Solidity

Response to call a function of a smart contract instance

Get the runtime code for a smart contract instance

Get information about a smart contract instance

Get all existing records for a smart contract instance

Get the current balance in a cryptocurrency account