Cryptographic encryption protocol for data types and values

A method comprising:

• initiating a cryptographic transaction between a first user and a second user, wherein the first user and the second user each having a respective cryptographic key pair including a public key and a private key, the cryptographic transaction including a first operand, a second operand, and a third operand wherein the first and second operands are associated with an amount of the cryptographic transaction and the third operand is associated with an asset type of the cryptographic transaction;
• encrypting the first operand with a first public key associated with the first user, thereby generating a first ciphertext;
• encrypting the second operand and the third operand with a second public key associated with the second user, thereby generating a second ciphertext and a third ciphertext respectively;
• confirming, via zero-knowledge proof, that the first ciphertext and the second ciphertext having matching plaintext values;
• and
• in response to said confirming, executing the cryptographic transaction on an immutable public ledger wherein the first ciphertext, the second ciphertext, and the third ciphertext are published, and wherein the amount of the cryptographic transaction is transferred from the first user to the second user.

A system comprising:

• a first node on a cryptographic network, the first node associated with a first user having a first cryptographic wallet and wherein the first user is identified by a first cryptographic keypair including a first public key and a first private key;
• a second node on a cryptographic network, the second node associated with a second user having a second cryptographic wallet and wherein the second user is identified by a second cryptographic keypair including a second public key and a second private key;
• and
• a distributed, immutable public ledger configured to store cryptographic transaction records;
• wherein the first node is configured to initiate a cryptographic transaction between the first user and the second user, and wherein the first node is configured to generate a first operand, a second operand, and a third operand, wherein the first and second operands are associated with an amount of the cryptographic transaction and the third operand is associated with an asset type of the cryptographic transaction;
• wherein the first node is configured to encrypt the first operand with the first public key thereby generating a first ciphertext, and encrypt the second operand and the third operand with the second public key thereby generating a second ciphertext and a third ciphertext respectively, and to confirm, via zero-knowledge proof, that the first ciphertext and the second ciphertext have matching plaintext values;
• wherein the second node is configured to verify that the third ciphertext matches an asset type associated with the second cryptographic wallet;
• and
• wherein the distributed immutable public ledger is configured to execute the cryptographic transaction in response to said confirmation by the second node, and wherein the distributed immutable public ledger is configured to publish the first ciphertext, the second ciphertext, and the third ciphertext, and wherein the amount of the cryptographic transaction is transferred from the first cryptographic wallet to the second cryptographic wallet.