contract_state_tree
Last updated
Was this helpful?
Last updated
Was this helpful?
The contracts reside in a contract state tree that is included in the root hash. The existence of a contract can be proven. Interactions, i.e. calls and return values, are stored in their own state tree for one block. The existence of the call in that block can be proven.
The contract state tree contains objects:
The contract definition (code binary)
The contract store (data binary)
Active flag (Boolean)
List of referring contracts (Note this will be changed to a list of referred contracts and a refcount.)
Deposit (amount)
Contract version (VM version + ABI version)
See for the serialization specification.
The contract also has a nonce and a balance recorded in an account state tree.
A call to a contract can execute chain transactions and these transactions are allowed to spend coins from the balance of the contract.
The contract definition
Created by a contract create transaction.
Created by a generalized account attach transaction
Deleted when an inactive contract has no more referrers.
The contract's account state tree is updated:
When the balance of a contract account is changed
Through a spend to the contract.
Through a call to the contract, with the transferred amount of the call.
Through a spend from a known account with an attached contract.
When a contract's balance is updated by a call executing a spend transaction.
When a call to a contract executes a transaction (create contract, call contract, spend, etc.) the nonce of the contract is increased by one. (This is subject to change in future versions.)
The contract's state tree is updated:
Upon success of a contract call the contract's storage sub tree is updated.
When another contract is created and that new contract refers to the contract in the code, the refcount is increased.
When another contract that refers to the contract is deleted the refcount is decreased.
When the contract executes the deactivate instruction the active field is set to false.
The fields owner, ct_version, code, and deposit are static throughout a contract's life time.
TO BE WRITTEN.
The calls state tree contains all calls done in the block and their return values. The calls state tree is pruned in each block so that the latest block only contains the calls in that block.
The key is <contract_address>Blake2b(<caller_address><caller_nonce><contract_address>), that uses Blake2b (256 bits digest).
Each call includes the caller address and caller nonce that, together, correlate the call with the transaction in the block that did the call.
The call object in the state tree contains the return value of a contract call transaction. For the contract create transaction the return value of the initial call is set to the empty byte array.
See for the serialization specification.