SYSTEMS AND METHODS FOR UPGRADABLE SMART CONTRACT FACTORIES

1 . A method, comprising:

providing, by one or more processors coupled to memory, on a blockchain of a blockchain network, a beacon contract configured to (i) deploy proxy contracts in response to corresponding requests and (ii) maintain a list of a plurality of implementation contracts stored on the blockchain, each implementation contract corresponding to a respective token type;

invoking, by the one or more processors, the beacon contract based on a request to deploy a first proxy contract, the first proxy contract corresponding to processing of a first token type, the invocation of the beacon contract causing the blockchain network to:

determine that the list of the plurality of implementation contracts includes an implementation contract corresponding to the first token type;

generate, on the blockchain responsive to the determination, the first proxy contract comprising a first address of the beacon contract; and

provide, on the blockchain, a second address of the first proxy contract in response to the request; and

invoking, by the one or more processors, the first proxy contract on the blockchain using the second address of the first proxy contract.

2 . The method of claim 1 , further comprising:

storing, by the one or more processors, the second address of the first proxy contract in a storage system different from the blockchain.

3 . The method of claim 1 , wherein invoking the first proxy contract on the blockchain causes the blockchain network to execute the first proxy contract based on the first address of the beacon contract.

4 . The method of claim 3 , wherein invoking the first proxy contract causes the blockchain network to retrieve a third address of the implementation contract corresponding to the first token type via the beacon contract.

5 . The method of claim 4 , wherein retrieving the third address of the implementation contract corresponding to the first token type causes the blockchain network to:

select an identifier of the implementation contract corresponding to the first token type from the list of the plurality of implementation contracts; and

provide the identifier of the implementation contract corresponding to the first token type as the third address of the implementation contract.

6 . The method of claim 1 , further comprising:

providing, by the one or more processors, a second request to update the implementation contract corresponding to the first token type, the second request comprising an identifier of an additional implementation contract,

wherein the second request causes the blockchain network to replace the identifier of the implementation contract corresponding to the first token type with the identifier of the additional implementation contract.

7 . The method of claim 6 , further comprising invoking, by the one or more processors, the first proxy contract on the blockchain using the second address of the first proxy contract, causing the blockchain network to retrieve the identifier of the additional implementation contract via the beacon contract.

8 . The method of claim 1 , further comprising causing, by the one or more processors, generation of a token having the first token type by invoking the implementation contract corresponding to the first token type via a second request identifying the first proxy contract.

9 . The method of claim 8 , further comprising:

upon receiving confirmation that the token has been generated, storing, by the one or more processors, a set of metadata corresponding to the token in a storage system different from the blockchain.

10 . The method of claim 1 , further comprising:

determining, by the one or more processors, that the first proxy contract has been deployed on the blockchain; and

providing, by the one or more processors, an indication that the first proxy contract has been deployed on the blockchain, the indication comprising the second address of the first proxy contract.

11 . A system, comprising:

one or more processors coupled to non-transitory memory, the one or more processors configured to:

provide, on a blockchain of a blockchain network, a beacon contract configured to (i) deploy proxy contracts in response to corresponding requests and (ii) maintain a list of a plurality of implementation contracts stored on the blockchain, each implementation contract corresponding to a respective token type;

invoke the beacon contract based on a request to deploy a first proxy contract, the first proxy contract corresponding to processing of a first token type, the invocation of the beacon contract causing the blockchain network to:

determine that the list of the plurality of implementation contracts includes an implementation contract corresponding to the first token type;

generate, on the blockchain responsive to the determination, the first proxy contract comprising a first address of the beacon contract; and

provide, on the blockchain, a second address of the first proxy contract in response to the request; and

invoke the first proxy contract on the blockchain using the second address of the first proxy contract.

12 . The system of claim 11 , wherein the one or more processors are further configured to:

store the second address of the first proxy contract in a storage system different from the blockchain.

13 . The system of claim 11 , wherein invoking the first proxy contract on the blockchain causes the blockchain network to execute the first proxy contract based on the first address of the beacon contract.

14 . The system of claim 13 , wherein invoking the first proxy contract causes the blockchain network to retrieve a third address of the implementation contract corresponding to the first token type via the beacon contract.

15 . The system of claim 14 , wherein retrieving the third address of the implementation contract corresponding to the first token type causes the blockchain network to:

select an identifier of the implementation contract corresponding to the first token type from the list of the plurality of implementation contracts; and

provide the identifier of the implementation contract corresponding to the first token type as the third address of the implementation contract.

16 . The system of claim 11 , wherein the one or more processors are further configured to:

provide a second request to update the implementation contract corresponding to the first token type, the second request comprising an identifier of an additional implementation contract,

wherein the second request causes the blockchain network to replace the identifier of the implementation contract corresponding to the first token type with the identifier of the additional implementation contract.

17 . The system of claim 16 , wherein the one or more processors are further configured to:

invoke the first proxy contract on the blockchain using the second address of the first proxy contract, causing the blockchain network to retrieve the identifier of the additional implementation contract via the beacon contract.

18 . The system of claim 11 , wherein the one or more processors are further configured to:

cause generation of a token having the first token type by invoking the implementation contract corresponding to the first token type via a second request identifying the first proxy contract.

19 . The system of claim 18 , wherein the one or more processors are further configured to:

upon receiving confirmation that the token has been generated, store a set of metadata corresponding to the token in a storage system different from the blockchain.

20 . The system of claim 11 , wherein the one or more processors are further configured to:

determine that the first proxy contract has been deployed on the blockchain; and

provide an indication that the first proxy contract has been deployed on the blockchain, the indication comprising the second address of the first proxy contract.