Abstract: Implementations of the present disclosure include instantiating a test blockchain container having read-only access to a production blockchain, copying a set of blocks from the production blockchain to a test environment to provide a test blockchain, the test blockchain container having read-write access to the test blockchain, and executing a test of a blockchain application, the test resulting in a set of test blocks being sequentially appended to the test blockchain, each test block at least partially including test data, wherein production blocks are appended to the production blockchain during execution of the test.

Abstract: Implementations of the present disclosure include receiving a transfer request including a first identifier of a first node, a second identifier of a second node, an identifier of a smart asset, and a value, determining whether the smart asset is capable of transfer at least partially based on the identifier of the smart asset, and the value, and in response to determining that the smart asset is capable of being transferred, automatically: providing a first smart asset and a second smart asset, the first smart asset being assigned a first identifier, a first value, and including properties of the smart asset, the second smart asset being assigned a second identifier, the value, and including properties of the smart asset, recording the first smart asset to the first node, and the second smart asset to the second node, and deleting the smart asset.

Abstract: Implementations of the present disclosure include receiving a merger request including a first identifier of a first node, a second identifier of a second node, and an identifier of a first smart asset, the first smart asset being associated with the first node, determining whether the first smart asset is capable of merger with a second smart asset associated with the second node at least partially based on the identifier of the first smart asset and an identifier of the second smart asset, and, in response to determining that the first smart asset is capable of being merged with the second smart asset, automatically: updating the second smart asset, the updated second smart asset being assigned a value, and including properties of the first smart asset, recording the updated second smart asset to the second node, and deleting the first smart asset.

Abstract: Implementations of the present specification include receiving, from a smart contract, and by a function controller executing within the blockchain network, a function call to execute a function, the function call including data for execution of the function, transmitting, by the function controller, the data of the function call to a function component, the function component executing the function based on the data of the function call, receiving, by the function controller, a function result from the function component, and providing, by the function controller, the function result to the smart contract.

Abstract: Implementations of the present specification include receiving, from a smart contract, and by a function controller executing within the blockchain network, a function call to execute a function, the function call including data for execution of the function, transmitting, by the function controller, the data of the function call to a function component, the function component executing the function based on the data of the function call, receiving, by the function controller, a function result from the function component, and providing, by the function controller, the function result to the smart contract.

Abstract: Implementations of the present specification include receiving, from a smart contract, and by a function controller executing within the blockchain network, a function call to execute a function, the function call including data for execution of the function, transmitting, by the function controller, the data of the function call to a function component, the function component executing the function based on the data of the function call, receiving, by the function controller, a function result from the function component, and providing, by the function controller, the function result to the smart contract.

Abstract: Implementations of the present specification include receiving, from a smart contract, and by a function controller executing within the blockchain network, a function call to execute a function, the function call including data for execution of the function, transmitting, by the function controller, the data of the function call to a function component, the function component executing the function based on the data of the function call, receiving, by the function controller, a function result from the function component, and providing, by the function controller, the function result to the smart contract.

Abstract: Implementations of the present disclosure include receiving, by a contract updates management system, an update request indicating a change to a smart contract, the change being a proposed update to the smart contract, determining, by executing an updates smart contract within the contract updates management system, whether conditions are met for updating the smart contract to incorporate the change, the updates smart contract defining the conditions, and upon determining, by the contract updates management system, that the conditions are met, updating, by the contract updates management system, the smart contract, and recording the change to one or more blocks in a blockchain of a blockchain network.

Abstract: Implementations of the present disclosure include initializing a nonce table comprising a plurality of nonce slots, each nonce slot being associated with a nonce index and a status, and storing a respective nonce value; receiving a request for a nonce value from an application, and in response, requesting a nonce value from the nonce table; receiving a nonce value in response to the request, a status of a nonce slot corresponding to the nonce value being set to occupied; and in response to a transaction using the nonce value being one of successful and failed, executing one of: releasing the nonce value within the nonce slot and setting the status to unoccupied, if the transaction is successful, and setting the status to unoccupied, if the transaction failed.

Abstract: Implementations of the present disclosure include receiving a transfer request including a first identifier of a first node, a second identifier of a second node, an identifier of a smart asset, and a value, determining whether the smart asset is capable of transfer at least partially based on the identifier of the smart asset, and the value, and in response to determining that the smart asset is capable of being transferred, automatically: providing a first smart asset and a second smart asset, the first smart asset being assigned a first identifier, a first value, and including properties of the smart asset, the second smart asset being assigned a second identifier, the value, and including properties of the smart asset, recording the first smart asset to the first node, and the second smart asset to the second node, and deleting the smart asset.

Abstract: Implementations of the present disclosure include receiving, by a contract updates management system, an update request indicating a change to a smart contract, the change being a proposed update to the smart contract, determining, by executing an updates smart contract within the contract updates management system, whether conditions are met for updating the smart contract to incorporate the change, the updates smart contract defining the conditions, and upon determining, by the contract updates management system, that the conditions are met, updating, by the contract updates management system, the smart contract, and recording the change to one or more blocks in a blockchain of a blockchain network.

Abstract: Implementations of the present disclosure include receiving a merger request including a first identifier of a first node, a second identifier of a second node, and an identifier of a first smart asset, the first smart asset being associated with the first node, determining whether the first smart asset is capable of merger with a second smart asset associated with the second node at least partially based on the identifier of the first smart asset and an identifier of the second smart asset, and, in response to determining that the first smart asset is capable of being merged with the second smart asset, automatically: updating the second smart asset, the updated second smart asset being assigned a value, and including properties of the first smart asset, recording the updated second smart asset to the second node, and deleting the first smart asset.

Abstract: Implementations of the present disclosure include instantiating a test blockchain container having read-only access to a production blockchain, copying a set of blocks from the production blockchain to a test environment to provide a test blockchain, the test blockchain container having read-write access to the test blockchain, and executing a test of a blockchain application, the test resulting in a set of test blocks being sequentially appended to the test blockchain, each test block at least partially including test data, wherein production blocks are appended to the production blockchain during execution of the test.

Abstract: Implementations of the this specification include receiving first transaction information from a first node, wherein the first transaction information comprises a transaction payload, a first public key, and a signed transaction payload for a transaction; verifying the signed transaction payload using the first public key; constructing an unconfirmed transaction data package, and setting a confirmation status of the unconfirmed transaction data package; receiving second transaction information from a second node, wherein the second transaction information includes a hash of the transaction payload, a second public key, and a signed hash of the transaction payload for the transaction, verifying the second transaction information using the second public key; updating the confirmation status of the unconfirmed transaction data package; and executing the transaction payload in response to the confirmation status indicating that all parties to the transaction have confirmed the transaction.

Abstract: Implementations of the present specification include polling the blockchain at specified time intervals, receiving block information from one or more updated blocks, the block information including static information and dynamic information, the dynamic information including one or more variables to be used in a smart contract, converting the dynamic information into one or more binary logs, and updating the local database using the one or more binary logs.

Abstract: Implementations of the present specification include receiving, from a smart contract, and by a function controller executing within the blockchain network, a function call to execute a function, the function call including data for execution of the function, transmitting, by the function controller, the data of the function call to a function component, the function component executing the function based on the data of the function call, receiving, by the function controller, a function result from the function component, and providing, by the function controller, the function result to the smart contract.

Abstract: Implementations of the present disclosure include initializing a nonce table comprising a plurality of nonce slots, each nonce slot being associated with a nonce index and a status, and storing a respective nonce value; receiving a request for a nonce value from an application, and in response, requesting a nonce value from the nonce table; receiving a nonce value in response to the request, a status of a nonce slot corresponding to the nonce value being set to occupied; and in response to a transaction using the nonce value being one of successful and failed, executing one of: releasing the nonce value within the nonce slot and setting the status to unoccupied, if the transaction is successful, and setting the status to unoccupied, if the transaction failed.