Secure processing and transfer of tokens in a distributed chain database

A system for securely processing a token in a distributed chain database, comprising:

• a processor configured to:
• receive, using an R-Token, a first valid call to a first transfer function to execute a first transfer, wherein the first transfer function transfers funds from a transferor to a mediator, wherein the distributed chain database includes the R-token, a registry, and an authorization service, the R-token being a first smart contract, the registry being a second smart contract, the authorization service being a third smart contract;
• upon transferring the the funds to the mediator, receive, using the R-Token, a second valid call to a second transfer function to execute a second transfer, wherein the second transfer function transfers funds from the mediator to a transferee;
• in response to the receiving of the second valid call to the second transfer function, route, using the R-Token, a check function to the authorization service that is executed on the chain database, comprising to:
• send a service call to the registry, wherein the registry is configured to determine an address of the authorization service based on the R-Token, wherein the R-Token corresponds to a first R-Token or a second R-Token, and send the address of the authorization service to the R-Token;
• receive, from the registry, the address of the authorization service in response to the service call;
• and
• route, using the received address of the authorization service, the check function to the authorization service;
• determine in the authorization service whether the second transfer is authorized, wherein the authorization service includes a state that is controlled by an approver process that is executed off the chain database;
• return a value by the authorization service that indicates whether the second transfer can proceed;
• determine whether to validate or invalidate the second transfer in response to the returned value;
• and
• in response to a determination that the second transfer is validated, commit the funds to the transferee;
• and
• a memory coupled to the processor and configured to provide the processor with instructions.

A computer program product to be executed by a computer processor for securely processing a token in a distributed chain database, the computer program product being embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions for:

• receiving, by the processor and using an R-Token, a first valid call to a first transfer function to execute a first transfer, wherein the first transfer function transfers funds from a transferor to a mediator, wherein the distributed chain database includes the R-token, a registry, and an authorization service, the R-token being a first smart contract, the registry being a second smart contract, the authorization service being a third smart contract;
• upon transferring the funds to the mediator, receiving, by the processor and using the R-Token, a second valid call to a second transfer function to execute a second transfer, wherein the second transfer function transfers funds from the mediator to a transferee;
• in response to the receiving of the second valid call to the second transfer function, routing, by the processor and using the R-Token, a check function to the authorization service that is executed on the chain database, comprising:
• sending, by the processor, a service call to the registry, wherein the registry is configured to determine an address of the authorization service based on the R-Token, wherein the R-Token corresponds to a first R-Token or a second R-Token, and send the address of the authorization service to the R-Token;
• receiving, by the processor and from the registry, the address of the authorization service in response to the service call;
• and
• routing, by the processor, using the received address of the authorization service, the check function to the authorization service;
• determining, by the processor using the authorization service, whether the second transfer is authorized, wherein the authorization service includes a state that is controlled by an approver process that is executed off the chain database;
• returning, by the processor, a value by the authorization service that indicates whether the second transfer can proceed;
• determining, by the processor, whether to validate or invalidate the second transfer in response to the returned value;
• and
• in response to a determination that the second transfer is validated, committing, by the processor, the funds to the transferee.

A method executed by a computer processor for securely processing a token in a distributed chain database comprising:

• receiving, by the processor and using an R-Token, a first valid call to a first transfer function to execute a first transfer, wherein the first transfer function transfers funds from a transferor to a mediator, wherein the distributed chain database includes the R-token, a registry, and an authorization service, the R-token being a first smart contract, the registry being a second smart contract, the authorization service being a third smart contract;
• upon transferring the funds to the mediator, receiving, by the processor and using the R-Token, a second valid call to a second transfer function to execute a second transfer, wherein the second transfer function transfers funds from the mediator to a transferee;
• in response to the receiving of the second valid call to the second transfer function, routing, by the processor and using the R-Token, a check function to the authorization service that is executed by the processor on the chain database, comprising:
• sending, by the processor, a service call to the registry, wherein the registry is configured to determine an address of the authorization service based on the R-Token, wherein the R-Token corresponds to a first R-Token or a second R-Token, and send the address of the authorization service to the R-Token;
• receiving, by the processor and from the registry, the address of the authorization service in response to the service call;
• and
• routing, by the processor, using the received address of the authorization service, the check function to the authorization service;
• determining, by the processor using the authorization service, whether the second transfer is authorized, wherein the authorization service queues a request to an on-chain oracle;
• returning, by the processor, a value by the authorization service that indicates whether the second transfer can proceed;
• determining, by the processor, whether to validate or invalidate the second transfer in response to the returned value;
• and
• in response to a determination that the second transfer is validated, committing, by the processor, the funds to the transferee.