Computer network systems for cryptographically-secured, token-based operations and methods of use thereof

A system comprising:

• a non-transient computer memory, storing software instructions;
• at least one processor of a computing device, the at least one processor executes software instructions, wherein the computing device is programmed to:
• receive activity initiation request from a first client device associated with a first user;
• wherein the activity initiation request comprises:
• at least one operation for exchange of a first token type for a second token type, and
• at least one reverse operation for exchange of the second token type for the first token type upon at least one condition being satisfied;
• wherein the first token type comprises a first cryptographic hash on a blockchain;
• wherein the second token type comprises a second cryptographic hash on the blockchain;
• wherein the first client device is a node on the blockchain;
• receive an activity initiation response from a second client device associated with a second user;
• wherein the activity initiation response indicates an acceptance of the activity initiation request, the acceptance corresponding to the at least one operation and the at least one reverse operation within the activity initiation request;
• wherein the second client device is a node on a blockchain;
• generate at least one self-executing software container (SESC) on the blockchain;
• wherein the at least one SESC comprises a plurality of instructions for execution of the at least one operation and the at least one reverse operation based at least in part on the at least one condition;
• wherein the plurality of instructions of the at least one SESC is configured to:
• detect a transfer of the first token type into a first segregated token storage;
• wherein the first segregated data structure is associated with a first segregated data structure of a third-party entity;
• wherein the first client device has permissions to access the first segregated token storage;
• wherein the first segregated data structure comprises a schema configured to store the first token type;
• detect a transfer of the second token type from a second token storage associated with the second client device to a first token storage associated with the first client device;
• automatically initiate a transfer of the first token type from the first segregated data structure to a second segregated token storage in response to the transfer of the second token type;
• wherein the second segregated token storage is associated with a second segregated data structure of the third-party entity;
• wherein the second client device has condition-dependent permissions to access the second segregated token storage;
• wherein the first segregated data structure comprises a schema configured to store the first token type;
• detect the at least one reverse operation matching the at least one condition;
• initiate a transfer via the detected at least one reverse operation of the first token type from the second segregated token storage back to the first segregated token storage and
• display, via the first client device, a rendering of a token return notification associated with the first token type.