Updateable smart contracts
A parent/child model for smart contracts enables the smart contracts to be updateable without compromising the immutability of the underlying data. As a first step, a parent smart contract (Client Contract) is deployed that stores any other contract that may be called using the contract address. Then, whenever a new child smart contract (Service Contract) is deployed, the parent smart contract is updated with the address of the new child smart contract so that the parent smart contract will be able to call the child smart contract. The structure of the child smart contract is known to the parent smart contract. For example, the number of inputs going into the child smart contract and the number of outputs coming out of the child smart contract are known to the parent smart contract before deployment of the parent smart contract, and the transaction data remains accessible without affecting the parent contract.
1. A method for updating a smart contract executed implemented on a blockchain, comprising:
segregating the smart contract into an updateable smart contract and a non-updateable smart contract, where the non-updateable smart contract handles persistent data storage and retrieval to the blockchain for data that needs to be permanently accessible and the updateable smart contract does not contain data storage and retrieval to the blockchain;
deploying the non-updateable smart contract and a first version of the updateable smart contract;
the first version of the updateable smart contract self-registering with the non-updateable smart contract upon deployment by providing the non-updateable smart contract with an address of the first version of the updateable smart contract;
the non-updateable smart contract storing the address of the first version of the updateable smart contract to the blockchain;
the non-updateable smart contract retrieving permanent data from the blockchain and passing the permanent data to the first version of the updateable smart contract;
the updateable smart contract performing a computation on the permanent data and returning updated data based on the computation of the permanent data back to the non-updateable smart contract; and
the non-updateable smart contract storing the updated data to the blockchain.
2. A method as in claim 1 , wherein the updateable smart contract and the non-updateable smart contract are connected via a fixed interface, and wherein the address of the first version of the updateable smart contract is provided to the non-updateable smart contract via the fixed interface, the non-updateable smart contract passes the permanent data to the first version of the updateable smart contract via the fixed interface, and the updateable smart contract returns updated data based on the computation of the permanent data back to the non-updateable smart contract via the fixed interface.
3. A method as in claim 1 , wherein providing the non-updateable smart contract with an address of the first version of the updateable smart contract comprises calling an interface of the non-updateable smart contract with the address of the first version of the updateable smart contract.
4. A method as in claim 3 , further comprising:
deploying a second version of the updateable smart contract;
calling the interface of the non-updateable smart contract with an address of the second version of the updateable smart contract;
the non-updateable smart contract storing the address of the second version of the updateable smart contract to the blockchain; and
the non-updateable smart contract invoking the second version of the updateable smart contract by retrieving the address of the second version of the updateable smart contract from the blockchain and calling the second version of the updateable smart contract at the retrieved address.
5. A method as claimed in claim 4 , wherein the segregating comprises segregating the smart contract into the non-updateable smart contract and a plurality of the updateable smart contracts, the deploying steps comprise deploying first and second versions of each updateable smart contract, the calling steps comprise calling respective interfaces with addresses of the respective versions of the respective updateable smart contracts, the storing steps comprise storing the addresses of the respective versions of the respective updateable smart contracts to the blockchain, and the invoking step comprises retrieving the addresses of the second versions of the updateable smart contracts from the blockchain and calling the second versions of the updateable smart contracts at the retrieved addresses.
6. A method as in claim 4 , wherein the segregating comprises segregating the smart contract into the non-updateable smart contract and a plurality of the updateable smart contracts, the deploying steps comprise deploying first and second versions of each updateable smart contract, the calling steps comprise calling the interface with an identifier associated with and the respective addresses of the respective updateable smart contracts, the storing steps comprise storing the identifiers and addresses of the respective versions of the respective updateable smart contracts to the blockchain, and the invoking step comprises retrieving the identifiers and addresses of the second versions of the updateable smart contracts from the blockchain and calling the second versions of the updateable smart contracts identified by the identifier at the retrieved addresses.
7. A method as in claim 4 , wherein each version of the updateable smart contract is self-registering with its address and the calling steps comprise respective versions of the self-registering updateable smart contract calling the interface of the non-updateable smart contract with the address of the respective versions of the self-registering updateable smart contract.
8. A method as in claim 4 , wherein the segregating comprises segregating the smart contract into the non-updateable smart contract and a plurality of the self-registering updateable smart contracts, the deploying steps comprise deploying first and second versions of each self-registering updateable smart contract, and the calling steps comprise the self-registering updateable smart contracts calling respective interfaces of the non-updateable smart contract with the addresses of the respective versions of the respective self-registering updateable smart contracts, the storing steps comprise storing the addresses of the respective versions of the respective updateable smart contracts to the blockchain, and the invoking step comprises retrieving the addresses of the second versions of the updateable smart contracts from the blockchain and calling the second versions of the updateable smart contracts at the retrieved addresses.
9. A method as in claim 4 , wherein the non-updateable smart contract retrieves permanent data from the blockchain and passes the permanent data to the updateable smart contract, and the updateable smart contract computes and returns data based on computation of the permanent data back to the non-updateable smart contract for permanent storage to the blockchain.
10. A method as in claim 4 , wherein the segregating comprises segregating the smart contract into a plurality of non-updateable smart contracts.
11. A method as in claim 1 , farther comprising:
hard-coding an address of the non-updateable smart contract into the first version of the updateable smart contract prior to deploying the first version of the updateable smart contract;
deploying a second version of the updateable smart contract;
calling the second version of the updateable smart contract;
the second version of the updateable smart contract calling the non-updateable smart contract at the hard-coded address; and
the non-updateable smart contract storing any permanent data to the blockchain.
12. A system for executing a smart contract on a blockchain, comprising:
a memory to store instructions; and
one or more processors using the instructions stored in the memory to perform operations including:
segregating the smart contract into an updateable smart contract and a non-updateable smart contract, where the non-updateable smart contract handles persistent data storage and retrieval to the blockchain for data that needs to be permanently accessible and the updateable smart contract does not contain data storage and retrieval to the blockchain;
deploying the non-updateable smart contract and a first version of the updateable smart contract;
the first version of the updateable smart contract self-registering with the non-updateable smart contract upon deployment by providing the non-updateable smart contract with an address of the first version of the updateable smart contract;
the non-updateable smart contract storing the address of the first version of the updateable smart contract to the blockchain;
the non-updateable smart contract retrieving permanent data from the blockchain and passing the permanent data to the first version of the updateable smart contract;
the updateable smart contract performing a computation on the permanent data and returning updated data based on the computation of the permanent data back to the non-updateable smart contract; and
the non-updateable smart contract storing the updated data to the blockchain.
13. A system as in claim 12 , further comprising a fixed interface that connects the updateable smart contract and the non-updateable smart contract, wherein the address of the first version of the updateable smart contract is provided to the non-updateable smart contract via the fixed interface, the non-updateable smart contract passes the permanent data to the first version of the updateable smart contract via the fixed interface, and the updateable smart contract returns updated data based on the computation of the permanent data back to the non-updateable smart contract via the fixed interface.
14. A system as in claim 12 , wherein the memory stores further instructions to perform operations including providing the non-updateable smart contract with an address of the first version of the updateable smart contract by calling an interface of the non-updateable mart contract with the address of the first version of the updateable smart contract.
15. A system as in claim 14 , wherein the memory stores further instructions to perform further operations including:
deploying a second version of the updateable smart contract;
calling the interface of the non-updateable smart contract with an address of the second version of the updateable smart contract;
the non-updateable smart contract storing the address of the second version of the updateable smart contract to the blockchain; and
the non-updateable smart contract invoking the second version of the updateable smart contract by retrieving the address of the second version of the updateable smart contract from the blockchain and calling the second version of the updateable smart contract at the retrieved address.
16. A system as in claim 15 , wherein the segregating comprises segregating the smart contract into the non-updateable smart contract and a plurality of the updateable smart contracts, the deploying comprises deploying first and second versions of each updateable smart contract, the calling comprises calling respective interfaces with addresses of the respective versions of the respective updateable smart contracts, the storing comprises storing the addresses of the respective versions of the respective updateable smart contracts to the blockchain, and the invoking comprises retrieving the addresses of the second versions of the updateable smart contracts from the blockchain and calling the second versions of the updateable smart contracts at the retrieved addresses.
17. A system as in claim 15 , wherein the segregating comprises segregating the smart contract into the non-updateable smart contract and a plurality of the updateable smart contracts, the deploying comprises deploying first and second versions of each updateable smart contract, the calling comprises calling the interface with an identifier associated with and the respective addresses of the respective updateable smart contracts, the storing comprises storing the identifiers and addresses of the respective versions of the respective updateable smart contracts to the blockchain, and the invoking comprises retrieving the identifiers and addresses of the second versions of the updateable smart contracts from the blockchain and calling the second versions of the updateable smart contracts identified by the identifier at the retrieved addresses.
18. A system as in claim 15 , wherein each version of the updateable smart contract is self-registering with its address and the calling comprises respective versions of the self-registering updateable smart contract calling the interface of the non-updateable smart contract with the address of the respective versions of the self-registering updateable smart contract.
19. A system as in claim 15 , wherein the segregating comprises segregating the smart contract into the non-updateable smart contract and a plurality of self-registering updateable smart contracts, the deploying comprises deploying first and second versions of each self-registering updateable smart contract, and the calling comprises the self-registering updateable smart contracts calling respective interfaces of the non-updateable smart contract with the addresses of the respective versions of the respective self-registering updateable smart contracts, the storing comprises storing the addresses of the respective versions of the respective updateable smart contracts to the blockchain, and the invoking comprises retrieving the addresses of the second versions of the updateable smart contracts from the blockchain and calling the second versions of the updateable smart contracts at the retrieved addresses.
20. A system as in claim 15 , wherein the memory stores further instructions to perform operations including the non-updateable smart contract retrieving permanent data from the blockchain and passing the permanent data to the updateable smart contract, and the updateable smart contract computing and returning data based on computation of the permanent data back to the non-updateable smart contract for permanent storage to the blockchain.
21. A system as in claim 15 , wherein the memory stores further instructions to perform operations including segregating the smart contract into a plurality of non-updateable smart contracts.
22. A system as in claim 12 , wherein the memory stores further instructions to perform operations including:
hard-coding an address of the non-updateable smart contract into the first version of the updateable smart contract prior to deploying the first version of the updateable smart contract;
deploying a second version of the updateable smart contract;
calling the second version of the updateable smart contract;
the second version of the updateable smart contract calling the non-updateable smart contract at the hard-coded address; and
the non-updateable smart contract storing any permanent data to the blockchain.
23. A non-transitory computer-readable medium storing computer instructions for updating a smart contract executed on a blockchain, that when executed by one or more processors, cause the one or more processors to perform the steps of:
segregating the smart contract into an updateable smart contract and a non-updateable smart contract, where the non-updateable smart contract handles persistent data storage and retrieval to the blockchain for data that needs to be permanently accessible and the updateable smart contract does not contain data storage and retrieval to the blockchain;
deploying the non-updateable smart contract and a first version of the updateable smart contract;
the first version of the updateable smart contract self-registering with the non-updateable smart contract upon deployment by providing the non-updateable smart contract with an address of the first version of the updateable smart contract;
the non-updateable smart contract storing the address of the first version of the updateable smart contract to the blockchain;
the non-updateable smart contract retrieving permanent data from the blockchain and passing the permanent data to the first version of the updateable smart contract;
the updateable smart contract performing a computation on the permanent data and returning updated data based on the computation of the permanent data back to the non-updateable smart contract; and
the non-updateable smart contract storing the updated data to the blockchain.