Granted Patent B2

US 12,450,598 · App. 18/070,300 · Granted Oct 21, 2025

Inventors: Hao Wen (Bothell, WA); Jiangchuan He (Redmond, WA); Nate Welch (Portland, ME); Hui Xie (Vancouver, CA); Vignesh Muralidharan (Seattle, WA); Rajeev Vishaka (Austin, TX)

G06Q20/3825G06Q20/38215G06Q20/4014

Abstract

Claims (40)

1. A method for token management comprising:

deploying, to a blockchain network comprising a plurality of computing nodes that maintain a blockchain ledger, a plurality of inbound smart contracts, including:

a first inbound smart contract for a first user of a plurality of users of a custodial token platform, the plurality of users determined based at least in part on a level of activity of a respective user of the plurality of users on the blockchain ledger exceeding a threshold, wherein a first address of the first inbound smart contract is configured to receive a first set of one or more crypto tokens, and wherein the first address corresponds to a user account of the first user on the custodial token platform; and

a second inbound smart contract for a second user of the plurality of users of the custodial token platform, wherein a second address of the second inbound smart contract is configured to receive a second set of one or more crypto tokens, and wherein the second address corresponds to a user account of the second user on the custodial token platform;

deploying, to the blockchain ledger, a batch smart contract configured to control the plurality of inbound smart contracts based at least in part on each of the plurality of inbound smart contracts comprising a smart contract controller address that associates a respective inbound smart contract of the plurality of inbound smart contracts to the batch smart contract; and

broadcasting, to the blockchain ledger, a transaction that calls the batch smart contract, wherein the transaction causes, via a single transaction on the blockchain ledger and after verification of the single transaction by one or more computing nodes of the plurality of computing nodes, a set of state transfers based at least in part on each of the plurality of inbound smart contracts comprising the smart contract controller address, the set of state transfers comprising a first state transfer of the first set of one or more crypto tokens of the first inbound smart contract and a second state transfer of the second set of one or more crypto tokens of the second inbound smart contract to an outbound address of the custodial token platform.

2. The method of claim 1 , wherein the transaction causes a transfer of a respective set of one or more crypto token from each of the plurality of inbound smart contracts.

3. The method of claim 1 , wherein deploying the plurality of inbound smart contracts comprises:

deploying a respective inbound smart contract for each user of the plurality of users.

4. The method of claim 1 , wherein deploying the plurality of inbound smart contracts comprises:

deploying a respective clone of an inbound smart contract for each user of the plurality of users, wherein each respective clone is associated with a proxy instance of the inbound smart contract and wherein the transaction causes the batch smart contract to call a transfer function of each respective clone to cause the set of state transfers.

5. The method of claim 4 , further comprising:

deploying a new version of the inbound smart contract to the blockchain ledger; and

updating a proxy contract associated with the proxy instance to reference a smart contract address associated with the new version of the inbound smart contract.

6. The method of claim 1 , wherein:

the transaction causes the set of state transfers based at least in part on each of the plurality of inbound smart contracts comprising the smart contract controller address.

7. An apparatus, comprising:

one or more memories storing processor-executable code; and

one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the apparatus to:

deploy, to a blockchain network comprising a plurality of computing nodes that maintain a blockchain ledger, a plurality of inbound smart contracts including:

a first inbound smart contract for a first user of a plurality of users of a custodial token platform, the plurality of users determined based at least in part on a level of activity of a respective user of the plurality of users on the blockchain ledger exceeding a threshold, wherein a first address of the first inbound smart contract be configured to receive a first set of one or more crypto tokens, and wherein the first address corresponds to a user account of the first user on the custodial token platform; and

a second inbound smart contract for a second user of the plurality of users of the custodial token platform, wherein a second address of the second inbound smart contract be configured to receive a second set of one or more crypto tokens, and wherein the second address corresponds to a user account of the second user on the custodial token platform;

deploy, to the blockchain ledger, a batch smart contract configured to control the plurality of inbound smart contracts based at least in part on each of the plurality of inbound smart contracts comprising a smart contract controller address that associates a respective inbound smart contract of the plurality of inbound smart contracts to the batch smart contract; and

broadcast, to the blockchain ledger, a transaction that call the batch smart contract, wherein the transaction causes, via a single transaction on the blockchain ledger and after verification of the single transaction by one or more computing nodes of the plurality of computing nodes, a set of state transfers based at least in part on each of the plurality of inbound smart contracts comprising the smart contract controller address, the set of state transfers comprising a first state transfer of the first set of one or more crypto tokens of the first inbound smart contract and a second state transfer of the second set of one or more crypto tokens of the second inbound smart contract to an outbound address of the custodial token platform.

8. The apparatus of claim 7 , wherein the transaction causes a transfer of a respective set of one or more crypto token from each of the plurality of inbound smart contracts.

9. The apparatus of claim 7 , wherein, to deploy the plurality of inbound smart contracts, the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:

deploy a respective inbound smart contract for each user of the plurality of users.

10. The apparatus of claim 7 , wherein to deploy the plurality of inbound smart contracts, the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:

deploy a respective clone of an inbound smart contract for each user of the plurality of users, wherein each respective clone is associated with a proxy instance of the inbound smart contract and wherein the transaction causes the batch smart contract to call a transfer function of each respective clone to cause the set of state transfers.

11. A non-transitory computer-readable medium storing code, the code comprising instructions executable by one or more processors to:

deploy, to a blockchain network comprising a plurality of computing nodes that maintain a blockchain ledger, a plurality of inbound smart contracts, including:

a first inbound smart contract for a first user of a plurality of users of a custodial token platform, the plurality of users determined based at least in part on a level of activity of a respective user of the plurality of users on the blockchain ledger exceeding a threshold, wherein a first address of the first inbound smart contract be configured to receive a first set of one or more crypto tokens, and wherein the first address corresponds to a user account of the first user on the custodial token platform; and

a second inbound smart contract for a second user of the plurality of users of the custodial token platform, wherein a second address of the second inbound smart contract be configured to receive a second set of one or more crypto tokens, and wherein the second address corresponds to a user account of the second user on the custodial token platform;

deploy, to the blockchain ledger, a batch smart contract configured to control the plurality of inbound smart contracts based at least in part on each of the plurality of inbound smart contracts comprising a smart contract controller address that associates a respective inbound smart contract of the plurality of inbound smart contracts to the batch smart contract; and

broadcast, to the blockchain ledger, a transaction that calls the batch smart contract, wherein the transaction causes, via a single transaction on the blockchain ledger and after verification of the single transaction by one or more computing nodes of the plurality of computing nodes, a set of state transfers based at least in part on each of the plurality of inbound smart contracts comprising the smart contract controller address, the set of state transfers comprising a first state transfer of the first set of one or more crypto tokens of the first inbound smart contract and a second state transfer of the second set of one or more crypto tokens of the second inbound smart contract to an outbound address of the custodial token platform.

12. The non-transitory computer-readable medium of claim 11 , wherein the transaction causes a transfer of a respective set of one or more crypto token from each of the plurality of inbound smart contracts.

13. The non-transitory computer-readable medium of claim 11 , wherein the instructions to deploy the plurality of inbound smart contracts are executable by the one or more processors to:

deploy a respective inbound smart contract for each user of the plurality of users.

14. The non-transitory computer-readable medium of claim 11 , wherein the instructions to deploy the plurality of inbound smart contracts are executable by the one or more processors to:

deploy a respective clone of an inbound smart contract for each user of the plurality of users, wherein each respective clone is associated with a proxy instance of the inbound smart contract and wherein the transaction causes the batch smart contract to call a transfer function of each respective clone to cause the set of state transfers.

Assignments (1)

Continuity (1)

References Cited (30)