Tassat Group Inc.

Brian Bruce

Kevin Lupowitz

Eric Couillard

Joe Grastara

Sanjaya Kulkarni

Sanjay Deshpande

Omari Edwards

Chester Chee

Al Gleicher

Jeff Yang

Systems and/or methods of the present disclosure enable ledger interoperability using a controller to perform an operation between a first user and a second user on separate entity-specific distributed ledgers, where the separate entity-specific distributed ledgers are both operatively linked to a membered common distributed ledger. The controller burns a first quantity of first entity-specific tokens from the first entity-specific distributed ledger and mints a second quantity of the common tokens on the membered common distributed ledger, where the first quantity of first entity-specific tokens and the second quantity of the common tokens represent an equivalency. The controller moves the second quantity of common tokens from a first encrypted storage to a second encrypted storage of the membered common distributed ledger, burns the second quantity of the common tokens and mints a third quantity of the second entity-specific tokens on the second entity-specific distributed ledger to complete the operation.

Systems for multi-blockchain, multi-token interoperability via common blockchain integration

Systems and/or methods of the present disclosure enable crypto-ledger interoperability using a controller to perform an operation between a first user and a second user on separate entity-specific distributed crypto-ledgers, where the separate entity-specific distributed crypto-ledgers are both operatively linked to a membered common distributed crypto-ledger. The controller burns a first quantity of first entity-specific crypto-tokens from the first entity-specific distributed crypto-ledger and mints a second quantity of the common crypto-tokens on the membered common distributed crypto-ledger, where the first quantity of first entity-specific crypto-tokens and the second quantity of the common crypto-tokens represent an equivalency. The controller moves the second quantity of common crypto-tokens from a first encrypted storage to a second encrypted storage of the membered common distributed crypto-ledger, burns the second quantity of the common crypto-tokens and mints a third quantity of the second entity-specific crypto-tokens on the second entity-specific distributed crypto-ledger to complete the operation.

A method, controller, and non-transitory computer-readable medium of a distributed crypto-ledger network, including receiving an instruction to perform an operation between a first user and a second user, the first user corresponding to a first entity that is a member of the distributed crypto-ledger network, the instruction comprising a destination address corresponding to the second user, querying a top-level name registry with the destination address to determine a second entity associated with the destination address, the second entity being a different member of the crypto-ledger network, and executing the operation between the first user and the second user by transmitting execution instructions to the first entity and the second entity, the execution instructions causing a first entity controller to modify data stored on a first distributed crypto-ledger of the first entity, and causing a second entity controller to modify data stored on the second distributed crypto-ledger of the second entity.

Method, controller, and computer-readable medium for network addressing on a distributed crypto ledger network

The disclosed systems and methods provide non-native functionality to a distributed network for distributed ledger token verification and event permissioning. The disclosed technology receives a transfer event request from a first node associated with a first token storage, where the transfer event request corresponds to movement of a requested token amount that is associated with at least one token. In response, the transfer event request is inserted into a pending transfer log that is configured to queue pending transfer event requests. A determination is made regarding a first permission based on the currently queued pending transfer event requests, and as a result, the transfer event request is transmitted to the distributed network based on the first permission, where such transfer causes the requested movement of the requested token amount.

Systems and methods for distributed ledger token verification for distributed ledger event permissioning

The disclosed systems and methods provide non-native functionality to a distributed network for events management on a blockchain via locking queued distributed network tokens. The disclosed technology receives a transfer event request from a first node associated with a first token storage, where the transfer event request corresponds to movement of a requested token amount that is associated with at least one token. A pending transfer event log that queues pending transfer event requests is accessed and modified by adding the transfer event request to the queue of pending transfer event requests. This causes the at least one token associated with the transfer event request to be locked, thereby preventing its association with other transfer events. The transfer event request is then transmitted to the distributed network, whereby the distributed network executes the movement of the at least one token.

Systems and methods for locking queued distributed network tokens

Systems and methods of the present disclosure enable distributed network request permissioning by receiving, from a first node associated with a token storage, a transfer event request for a movement of a requested token amount relative to the token storage via a distributed network and accessing a pending transfer event log recorded in an event record database, the pending transfer event log including other transfer event request records associated with other transfer event requests. A denial rejecting the transfer event request is determined based on the pending transfer event log. The transfer event request and the denial are transmitted to an approver node having supervisory permissions to approve or disapprove of event requests. A permission is received from the second node to approve the transfer event request, and a transfer event write permission determination is received by the distributed network that causes the movement to be performed.

Computer-based systems configured to utilize a supervisory node to approve distributed network events and methods of use thereof

Systems and methods of the present disclosure enable distributed network request permissioning receiving, from a first node associated with a token storage, a transfer event request for a movement of a requested token amount relative to the token storage via a distributed network. A pending transfer event log is accessed that includes a total pending token amount associated with pending tokens of pending transfer event requests with respect to the token storage, and a total available token amount associated with available tokens in the first token storage. A permission is determined based on the total available token amount exceeding a sum of the total pending token amount and the requested token amount. An updated total pending token amount is determined by adding the transfer event request record to the pending transfer event log, and the transfer event request is transmitted to the distributed network to perform the movement.

Computer-based systems configured to utilize an event log to pre-authorize distributed network events and methods of use thereof

Systems for multi-blockchain, multi-token interoperability via common blockchain integration and methods of use thereof

Systems and methods enable permission events management on a blockchain. Embodiments include receiving a transfer event request for a movement of a number of tokens relative to a token storage via the blockchain. An event log record database is accessed which includes a total number of tokens of pending transfer event request records, and a total number of tokens in the token storage. A first permission is determined for generating a transfer event request record to the event log record database based on the number of the tokens exceeding the total logged number of tokens. An updated total logged number of tokens is determined with the transfer event request record and the transfer event request is transmitted to the distributed network. An updated total number of tokens in the token storage is determined based on the transfer event log record and a blockchain write permission determination.

Growing community of inventors

New York, NY, United States of America

Brian Bruce