Solana developers can now use SecretPath to pass encrypted messages from Solana applications to a Secret Network smart contract. With this capability, Solana developers can build privacy-centric applications, such as:

• Private DeFi protocols: Allow users to interact with decentralized finance applications while keeping transaction details private.

• Confidential NFTs: Create NFTs where ownership or content can be privately verified and shared.

• Encrypted messaging apps: Build decentralized applications where users can exchange encrypted messages, ensuring confidentiality.

• Secure Voting Systems: Implement voting mechanisms where individual votes remain private but outcomes are publicly verifiable.

By integrating Solana with Secret Network via SecretPath, developers can bring enhanced privacy features to decentralized applications, improving security and user trust.

SecretPath seamlessly handles encrypted payloads, as the master gateway contract on Secret Network automatically decrypts payloads and passes the decrypted payload over to the target contract deployed on Secret Network.

The encryption of the payload is done using the ChaCha20-Poly1305, an authenticated encryption with additional data (AEAD) algorithm.

The key for this symmetric encryption is created by using the Elliptic-curve Diffie-Hellman (ECDH) scheme, comprising of two components:

1. An extra encryption public key provided from the Secret Gateway Contract

2. A randomly created (ephemeral) encryption private key on the user side (independent of the user wallet's private key)

Combining both of these keys together via the ECDH Scheme yields our encryption key, which we use to encrypt the payload with ChaCha20-Poly1305.

Let's learn how to use SecretPath on Solana in the key-value store developer tutorial 😊.

Usecases

• Storing Encrypted Data on Secret Network

• VRF (Sending on-chain generated random numbers to Solana)

Supported Networks

Solana Mainnet & Testnet

Overview

SecretPath seamlessly handles encrypted payloads on Solana, which means Solana developers can use SecretPath to encrypt and decrypt messages cross-chain on Secret Network!

In this tutorial, you will learn how to upload your own Key-value store program to Secret Network, which you can use to encrypt values on Solana and send them cross-chain to Secret Network!

By this end of this tutorial you will:

• Have an understanding of SecretPath, Secret Network's trustless Solana and EVM bridge

• Upload and instantiate your very own key value store contract on Secret Network

• Pass an encrypted string from Solana to Secret Network

• Connect a frontend to your Solana application

Key Value Store Demo

Getting Started

To get started, clone the repo:

git clone https://github.com/writersblockchain/solana-kv-store

Solana Prerequisites

1. Install Phantom wallet.

2. Fund your Solana devnet wallet.

Understanding SecretPath ✅

Before you upload a key-value store program to Secret Network, it is important for you to understand how messages are sent from Solana to Secret Network and vice-versa. This is thanks to a protocol that Secret Network developed called SecretPath, which allows Solana developers to execute programs on Secret Network while preserving the privacy of the inputs and validity of the outputs using ECDH cryptography 🤯.

SecretPath has two main components: gateways and relayers.

1. The Gateway is a Solana program created by Secret Network that acts as the interface for handling messages between Solana and Secret Network. The gateway program packages, verifies, and encrypts/decrypts messages. For your purposes, all that you must know is how to properly format your Secret Network program's functions so they can be understood by the Solana gateway program, which you will learn shortly.

2. Relayers watch for messages on Solana and then pass them to Secret Network, and vice-versa. They do not have access to the actual data (since messages are encrypted), so they can't compromise security. Their main job is ensuring the network runs smoothly by transmitting the messages, but they don’t move tokens or handle funds. For your purposes, you needn't focus on relayers as Secret Network maintains a relayer for all Solana transactions.

Now that you understand the basics of SecretPath, let's upload your very own key-value store program to Secret Network! 🤓

Understanding the Key-Value store program on Secret Network

cd into solana-kv-store/secret-contract:

cd solana-kv-store/secret-contract

Let's examine the key-value store program. Open the src folder and you will see four files:

• contract.rs

• lib.rs

• msg.rs

• state.rs

Like Solana, programs on Secret Network are written in Rust. Unlike Solana, Secret Network developers use a framework called Cosmwasm instead of Anchor. Let's examine each of these files before uploading the program to Secret Network testnet.

state.rs

On Solana, programs are stateless. On Secret Network, programs (ie smart contracts) are stateful. This means that unlike Solana's stateless programs, Secret Network programs maintain persistent state across transactions, allowing for private data storage and processing.

state.rs is where you manage your contract's state, which in this case is simply the program info for the master Solana Gateway Contract and the key-value pair that users will store in your program:

#[derive(Serialize, Deserialize, Clone, Debug, PartialEq)]
pub struct State {
    pub gateway_address: Addr,
    pub gateway_hash: String,
    pub gateway_key: Binary,
}

When you instantiate your program on Secret Network, you save the Solana Gateway Program info (gateway_address, gateway_hash, and gateway_key) in the Secret program so that it knows how to correctly route messages to the Solana Gateway program.

Key-Value storage struct:

#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, JsonSchema)]
pub struct StorageItem {
    // Value of the StorageItem
    pub value: String,
    // ViewingKey of the StorageItem to unlock the value
    pub key: String,
    
}

msg.rs

In Secret Network programs, a msg.rs file typically defines the structure of messages that your program will send or receive. It outlines how the program interacts with external users, other programs, or blockchain modules, specifying what kind of data is expected in those interactions.

For example, on Solana, you'd define instruction data formats in a similar way when developing programs that interact with accounts. In CosmWasm (Secret Network's smart contract framework), a msg.rs file similarly defines the data types for actions like instantiating, executing, and querying programs.

In the context of SecretPath, this msg.rs file defines the messages that will be sent to and received from the master Solana gateway program, which is responsible for managing cross-chain communication.

In your case, you will be passing the InputStoreMsg to state:

#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, JsonSchema)]
pub struct InputStoreMsg {
    // Value of the StorageItem
    pub value: String,
    // ViewingKey of the StorageItem to unlock the value
    pub key: String,

}

contract.rs

In the context of the Secret Network, the contract.rs file is the core of your program logic, much like the Solana program's main instruction handler. It contains the main program functions, handling instantiation, execution, and migration, as well as any specific functionality you’ve built in.

In this file, you define how the program will handle inputs, store state, interact with other programs (like the Solana gateway in SecretPath), and process outputs. Let’s focus on the key function, store_value, since that's the core of how key-value pairs are handled.

The store_value function takes in data (input values, task info, and an input hash), stores a key-value pair in the program's storage, and then sends a confirmation message back to the Solana master gateway program.

The input values are deserialized to extract the key and value, which are saved in the program's storage:

let input: InputStoreMsg = serde_json_wasm::from_str(&input_values)
        .map_err(|err| StdError::generic_err(err.to_string()))?;

    // create a task information store
    let storage_item = StorageItem {
        value: input.value,
        key: input.key.clone(),
    };

    // map task to task info
    KV_MAP.insert(deps.storage, &input.key, &storage_item)?;

    let data = ResponseStoreMsg {
        key: input.key.to_string(),
       message: "Value store completed successfully".to_string(),
    };

A success message is created, serialized to JSON, encoded in base64, and sent as part of the response:

// Serialize the struct to a JSON string1
    let json_string =
        serde_json_wasm::to_string(&data).map_err(|err| StdError::generic_err(err.to_string()))?;

    // Encode the JSON string to base64
    let result = base64::encode(json_string);

        // Get the contract's code hash using the gateway address
    let gateway_code_hash = get_contract_code_hash(deps, config.gateway_address.to_string())?;

    let callback_msg = GatewayMsg::Output {
        outputs: PostExecutionMsg {
            result,
            task,
            input_hash,
        },
    }
    .to_cosmos_msg(
        gateway_code_hash,
        config.gateway_address.to_string(),
        None,
    )?;

    Ok(Response::new()
        .add_message(callback_msg)
        .add_attribute("status", "stored value with key"))

This function stores data securely on-chain in your Key-Value store program and notifies the master Solana gateway program once the task is complete.

Now that you understand how the program works, let's upload it to Secret Network!

Uploading the Key-Value store program to Secret Network

Before you upload the key-value store program to Secret Network, you first must compile the code.

Compile the program:

make build-mainnet

cd into node:

cd node

Install secretjs:

npm i

Open upload.js and examine the code. You needn't change anything here unless you want to upload the Secret Network program to Mainnet instead of testnet.

Upload and instantiate the program on Secret Network testnet:

node upload

You will see a contract id, codehash, and address returned:

codeId:  10207
Contract hash: 931a6fa540446ca028955603fa4b924790cd3c65b3893196dc686de42b833f9c
contract address:  secret1zdz2h5883nlz757dsq2ejfwdy0wpq0uwe2mz0r

Now let's use this program to store encrypted strings on Solana!

Key-Value storage on Solana

Now that you have deployed your key-value store program on Secret Network, all that's left is to execute it from Solana! To do this, you will use the IDL of the master Solana Gateway program in order to execute your program on Secret Network and correctly format the parameters that you pass to the master Solana Gateway program, which you will now learn how to do 🤓

Let's start by examining solana-kv-store/solana-frontend/src/submit.ts.

Submit.ts is where you format and submit the transaction data to the Solana Gateway program so that it can execute your Secret Network key-value store program, and then send the callback message successfully back to the master Solana Gateway program 🤓

Notice that the IDL of the master Solana Gateway Program is imported into submit.ts, which you can find here: Gateway Contract IDL.

Import the IDL using:

import idl from "./solana_gateway.json";

To start, we first define all of our variables that we need for the encryption, as well as the gateway information:

const routing_contract = "secret15n9rw7leh9zc64uqpfxqz2ap3uz4r90e0uz3y3"; //the contract you want to call in secret
const routing_code_hash = "931a6fa540446ca028955603fa4b924790cd3c65b3893196dc686de42b833f9c" //its codehash

Replace routing_contract and routing_code_hash with your contract address and code hash! This is the Solana program that you just uploaded to Secret network testnet 😄

At this point, you can run the application exactly as is and the master Solana gateway program will correctly route to the program you deployed on Secret Network. But let's go more in depth so you understand how everything is working together 😄

Generating the encryption key using ECDH

Next, you generate ephermal keys and load in the public encryption key for the Solana Secret Gateway program. Then, use ECDH to create the encryption key:

  //Generating ephemeral keys
    const walletEpheremal = ethers.Wallet.createRandom();
    const userPrivateKeyBytes = Buffer.from(
      walletEpheremal.privateKey.slice(2),
      "hex"
    );
    const userPublicKey: string = new SigningKey(walletEpheremal.privateKey)
      .compressedPublicKey;
    const userPublicKeyBytes = Buffer.from(userPublicKey.slice(2), "hex");

    const sharedKey = await sha256(
      ecdh(userPrivateKeyBytes, gatewayPublicKeyBytes)
    );

Define the Calldata for the Secret program & Callback information

Next, you define all of the information that you need for calling the key-value store program on Secret AND add the callback information for the message on its way back.

First, we define the function that we are going to call on your Secret key-value store program, which in this case is store_value . Next, we add the parameters/calldata for this function and convert it into a JSON string:

1. Define the Function and Parameters (Calldata)

The first step is to define the function name and the parameters that you want to pass into your key-value store program on the Secret Network.

const value = document.querySelector<HTMLFormElement>("#input1")?.value;
const key = document.querySelector<HTMLFormElement>("#input2")?.value;
    
const callback_gas_limit =
    5000000; 
    
const handle = "store_value";

const data = JSON.stringify({
      value: value,
      key : key,
    });

• Function Name (handle): This specifies the function you wish to invoke within the Secret program. In this example, "store_value" is a function that stores a key-value pair.

• Parameters (data): This is the data that you will pass to the function in the Secret program. Here, we use a JSON string that contains the key-value pair.

2. Derive the Program Derived Addresses (PDAs)

In Solana, Program Derived Addresses (PDAs) are special types of addresses that are derived deterministically based on a seed and the program ID. Both PDAs are used here to store the gateway and the tasks' state. You do not need to manually save them as both of these can deterministically derived from the program id at any time.

// Derive the Gateway PDA / Program Derived Address
const [gateway_pda, gateway_bump] = web3.PublicKey.findProgramAddressSync(
  [Buffer.from("gateway_state")],
  program.programId
);

// Derive the Tasks PDA / Program Derived Address
const [tasks_pda, task_bump] = web3.PublicKey.findProgramAddressSync(
  [Buffer.from("task_state")],
  program.programId
);

• gateway_pda: This is the Program Derived Address associated with the gateway's state. It's derived from a seed ("gateway_state") and the program ID.

• tasks_pda: This is the Program Derived Address associated with the tasks' state. Similarly, it's derived from a seed ("task_state") and the program ID.

3. Define the Callback Information

The callback information specifies where and how the call should be handled. This involves setting a callback address and a callback selector.

// Include some address as a test (not needed here, you can add whatever you need for your dApp)
const testAddress1 = new web3.PublicKey("HZy2bXo1NmcTWURJvk9c8zofqE2MUvpu7wU722o7gtEN");
const testAddress2 = new web3.PublicKey("GPuidhXoR6PQ5skXEdrnJehYbffCXfLDf7pcnxH2EW7P");
const callbackAddress = Buffer.concat([testAddress1.toBuffer(),testAddress2.toBuffer()]).toString("base64");

Callback Address (callbackAddress): These are the addresses where the callback addresses needed for the CPI are included. In this example, it’s simply a test address. In a real-world application, this would typically be your callback contract's address or the addresses designated to handle the callback. The callback addresses are the concatenated 32 bytes of all addresses that need to be accessed for the callback CPI. We take two address public keys (32 bytes each), concatenate them together and then base64 encode them.

Next, we define the callback selector. The callback selector is a unique identifier that indicates which program and function the callback CPI should access. It's a combination of the program ID and a specific function identifier.

// 8 bytes of the function Identifier = CallbackTest in the SecretPath Solana Contract
const functionIdentifier = [196, 61, 185, 224, 30, 229, 25, 52];
const programId = program.programId.toBuffer();

// Callback Selector is ProgramId (32 bytes) + function identifier (8 bytes) concatenated
const callbackSelector = Buffer.concat([programId, Buffer.from(functionIdentifier)]);

• Function Identifier (functionIdentifier): This is an array of bytes that uniquely identifies the function within the contract that should process the callback. In this example, the identifier corresponds to a hypothetical function "CallbackTest" in the SecretPath Solana program.

• Program ID (programId): This is callback program on Solana that is involved for the callback.

• Callback Selector (callbackSelector): This is a combination of the programId and the functionIdentifier, and it uniquely identifies the callback program and function within the Solana program.

Finally, we specify the callback compute limit or callback gas limit:

const callbackGasLimit = Number(callback_gas_limit);

• Callback Gas Limit (callbackGasLimit): This represents the amount of gas that should be allocated to process the callback on the Solana side. It's important to estimate this correctly to ensure that the callback can be executed without running out of resources.

After defining the contract call and callback, we now construct the payload:

//Payload data that are going to be encrypted
const payload = {
  data: data,
  routing_info: routing_contract,
  routing_code_hash: routing_code_hash,
  user_address: provider.publicKey.toBase58(),
  user_key: Buffer.from(userPublicKeyBytes).toString("base64"),
  callback_address: callbackAddress,
  callback_selector: Buffer.from(callbackSelector).toString("base64"),
  callback_gas_limit: callbackGasLimit,
};

Encrypting the Payload

Next, we encrypt the payload using ChaCha20-Poly1305. Then, we hash the encrypted payload into a ciphertextHash using Keccak256.

//build a JSON of the payload 
const plaintext = json_to_bytes(payload);

// Generate a nonce for ChaCha20-Poly1305 encryption
//DO NOT skip this, stream cipher encryptions are only secure with a random nonce!
const nonce = crypto.getRandomValues(new Uint8Array(12));

// Encrypt the payload using ChachaPoly1305 and concatenate the ciphertext + tag
const [ciphertextClient, tagClient] = chacha20_poly1305_seal(sharedKey, nonce, plaintext);
const ciphertext = concat([ciphertextClient, tagClient]);

// Create the payloadHash by keccak256 of the ciphertext
const payloadHash = Buffer.from(keccak256.arrayBuffer(ciphertext));

Signing the Payload with Phantom Wallet

Next, we use Phantom to sign the payloadHash using signMessage.

Internally, Phantom Wallet only allows for ASCII encoded strings to be signed to prevent any wallet drainers from signing arbitrary bytes. For us this means that we take the payloadHash and base64 encode it. Phantom then actually directly signs the base64 string (NOT: the payloadHash directly) of the payloadHash to get the signature. Keep this in mind when verifying the signature against the payloadHash.

const payloadHashBase64 = Buffer.from(payloadHash.toString("base64"));
const payloadSignature = await provider.signMessage(payloadHashBase64);

Packing the Transaction & Send

Lastly, we pack all the information we collected during previous steps into an info struct that we send into the Solana Gateway program. We encode the function data. Finally, we set the tx_params. Please make sure to set an appropriate gas amount for your contract call, here we used 150k gas. For the value of the TX, we send over the estimated callback gas that we calculated above.

const executionInfo = {
  userKey: Buffer.from(userPublicKeyBytes),
  userPubkey: payloadSignature.publicKey.toBuffer(),
  routingCodeHash: routing_code_hash,
  taskDestinationNetwork: "pulsar-3",
  handle: handle,
  nonce: Buffer.from(nonce),
  callbackGasLimit: callback_gas_limit,
  payload: Buffer.from(ciphertext),
  payloadSignature: payloadSignature.signature,
};

// Get the latest blockhash
const { blockhash } = await connection.getLatestBlockhash("confirmed");

// Construct the transaction
const tx = await program.methods
  .send(provider.publicKey, routing_contract, executionInfo)
  .accounts({
    gatewayState: gateway_pda,
    taskState: tasks_pda,
    user: provider.publicKey,
    systemProgram: web3.SystemProgram.programId,
  })
  .transaction();

// Set the recent blockhash
tx.recentBlockhash = blockhash;
tx.feePayer = provider.publicKey;

// Sign the transaction using Phantom wallet
const signedTx = await provider.signTransaction(tx);

// Send the signed transaction
const signature = await connection.sendRawTransaction(signedTx.serialize());

// Confirm the transaction
await connection.confirmTransaction(signature);

console.log("Final result after rpc:", tx);

Now that you know how to correctly format and package data for the Solana Gateway program, let's learn how to connect your program to a frontend 🚀

Connecting Your Solana Key-value store program to Frontend

Open a new terminal window and cd into solana-kv-store/solana-frontend:

cd solana-kv-store/solana-frontend

Install the dependencies:

npm i

Initializing the Solana Client

Next, initialize the Solana client that you are using to interact with the program. Connect to Phantom wallet and set up the Anchor provider with the Program IDL imported earlier.

const network = "https://api.devnet.solana.com";
const connection = new Connection(network, "processed");

const getProvider = () => {
  if ("solana" in window) {
    const provider = window.solana as any;
    if (provider.isPhantom) {
      return provider;
    }
  }
  window.open("https://phantom.app/", "_blank");
};

const provider = getProvider();
if (!provider) {
  console.error("Phantom wallet not found");
} else {
  await provider.connect(); // Connect to the wallet
}

const wallet = {
  publicKey: provider.publicKey,
  signTransaction: provider.signTransaction.bind(provider),
  signAllTransactions: provider.signAllTransactions.bind(provider),
};

const anchorProvider = new AnchorProvider(connection, wallet, {
  preflightCommitment: "processed",
});
const program = new Program(idl, anchorProvider);

Now it's time to run the program! In the terminal:

npm run dev 

Congrats! You now have your very own Solana key-value store program deployed on Secret Network and can encrypt strings on Solana!

Summary

In conclusion we constructed and encrypted a payload for SecretPath for Solana direct in the Frontend as well as calling the SecretPath gateway program.

Need help with using encrypted payloads with Secretpath or want to discuss use cases for your dApp? Please ask in the Secret Network Telegram or Discord.

The latest IDL for the Solana Gateway contract on version 0.2.3 is the following:

Overview

, Secret Network's on-chain random number generator, enables Solana developers to access encrypted on-chain verifiable random numbers from Secret Network.

In this tutorial, you will learn how to send random numbers from Secret Network to a Solana program. By this end of this tutorial you will:

• Have an understanding of , Secret Network's trustless Solana and EVM bridge

• Upload and instantiate your very own randomness contract on Secret Network

• Request random numbers on Solana from Secret Network

• Connect a frontend to your Solana application

VRF Demo

Way to go! You just sent an encrypted on-chain random number from Secret Network to a Solana program. Now it's time to learn how to upload your own randomness contract on Secret Network so that you can program it as you see fit. Let's get started 😊

Getting Started

To get started, clone the repo:

Solana Prerequisites

Understanding SecretPath ✅

SecretPath has two main components: gateways and relayers.

1. The Gateway is a Solana program created by Secret Network that acts as the interface for handling messages between Solana and Secret Network. The gateway program packages, verifies, and encrypts/decrypts messages. For your purposes, all that you must know is how to properly format your Secret Network program's functions so they can be understood by the Solana gateway program, which you will learn shortly.

2. Relayers watch for messages on Solana and then pass them to Secret Network, and vice-versa. They do not have access to the actual data (since messages are encrypted), so they can't compromise security. Their main job is ensuring the network runs smoothly by transmitting the messages, but they don’t move tokens or handle funds. For your purposes, you needn't focus on relayers as Secret Network maintains a relayer for all Solana transactions.

Now that you understand the basics of SecretPath, let's upload your very own RNG program to Secret Network! 🤓

Understanding the RNG program on Secret Network

cd into solana-rng/rng:

Let's examine the RNG program. Open the src folder and you will see four files:

Like Solana, programs on Secret Network are written in Rust. Unlike Solana, Secret Network developers use a framework called Cosmwasm instead of Anchor. Let's examine each of these files before uploading the program to Secret Network testnet.

On Solana, programs are stateless. On Secret Network, programs (ie smart contracts) are stateful. This means that unlike Solana's stateless programs, Secret Network programs maintain persistent state across transactions, allowing for private data storage and processing.

When you instantiate your program on Secret Network, you save the Solana Gateway Program info (gateway_address, gateway_hash, and gateway_key) in the Secret program so that it knows how to correctly route messages to the Solana Gateway program.

In Secret Network programs, a msg.rs file typically defines the structure of messages that your program will send or receive. It outlines how the program interacts with external users, other programs, or blockchain modules, specifying what kind of data is expected in those interactions.

For example, on Solana, you'd define instruction data formats in a similar way when developing programs that interact with accounts. In CosmWasm (Secret Network's smart contract framework), a msg.rs file similarly defines the data types for actions like instantiating, executing, and querying programs.

In the context of SecretPath, this msg.rs file defines the messages that will be sent to and received from the master Solana gateway program, which is responsible for managing cross-chain communication.

• The randomness generation in the contract creates a buffer to store random data, fills it using a pseudorandom number generator (PRNG), and sends the result to the gateway.

• After generating random numbers, the contract returns the result back to the master gateway program. The randomness result is packaged into a PostExecutionMsg and passed to the Solana gateway as a callback.

Now that you understand how the program works, let's upload it to Secret Network!

Uploading the RNG program to Secret Network

Before you upload the randomness program to Secret Network, you first must compile the code.

Compile the randomness contract:

cd into node:

Install secretjs:

Upload and instantiate the program on Secret Network testnet:

You will see a contract id, codehash, and address returned:

Now let's use this program to request random numbers on Solana!

Request Random Numbers on Solana

Now that you have deployed your randomness program on Secret Network, all that's left is to execute it from Solana! To do this, you will use the IDL of the master Solana Gateway program in order to execute your randomness program on Secret Network and correctly format the parameters that you pass to the master Solana Gateway program, which you will now learn how to do 🤓

Import the IDL using:

Generating the encryption key using ECDH

Define the Calldata for the Secret program & Callback information

Next, you define all of the information that you need for calling the RNG program on Secret AND add the callback information for the message on its way back.

1. Define the Function and Parameters (Calldata)

The first step is to define the function name and the parameters that you want to pass into your RNG program on the Secret Network.

• Function Name (handle): This specifies the function you wish to invoke within the Secret program. In this example, "request_random" is a function that generates a random number.

• Parameters (data): This is the data that you will pass to the function in the Secret program. Here, we use a JSON string that contains the number of random words (numWords) that the function will generate.

2. Derive the Program Derived Addresses (PDAs)

In Solana, Program Derived Addresses (PDAs) are special types of addresses that are derived deterministically based on a seed and the program ID. Both PDAs are used here to store the gateway and the tasks' state. You do not need to manually save them as both of these can deterministically derived from the program id at any time.

• gateway_pda: This is the Program Derived Address associated with the gateway's state. It's derived from a seed ("gateway_state") and the program ID.

• tasks_pda: This is the Program Derived Address associated with the tasks' state. Similarly, it's derived from a seed ("task_state") and the program ID.

3. Define the Callback Information

The callback information specifies where and how the call should be handled. This involves setting a callback address and a callback selector.

• Callback Address (callbackAddress): These are the addresses where the callback addresses needed for the CPI are included. In this example, it’s simply a test address. In a real-world application, this would typically be your callback contract's address or the addresses designated to handle the callback. The callback addresses are the concatenated 32 bytes of all addresses that need to be accessed for the callback CPI. We take two address public keys (32 bytes each), concatinate them together and then base64 encode them.

Next, we define the callback selector. The callback selector is a unique identifier that indicates which program and function the callback CPI should access. It's a combination of the program ID and a specific function identifier.

• Function Identifier (functionIdentifier): This is an array of bytes that uniquely identifies the function within the contract that should process the callback. In this example, the identifier corresponds to a hypothetical function "CallbackTest" in the SecretPath Solana program.

• Program ID (programId): This is callback program on Solana that is involved for the callback.

• Callback Selector (callbackSelector): This is a combination of the programId and the functionIdentifier, and it uniquely identifies the callback program and function within the Solana program.

Finally, we specify the callback compute limit or callback gas limit:

• Callback Gas Limit (callbackGasLimit): This represents the amount of gas that should be allocated to process the callback on the Solana side. It's important to estimate this correctly to ensure that the callback can be executed without running out of resources.

After defining the contract call and callback, we now construct the payload:

Encrypting the Payload

Next, we encrypt the payload using ChaCha20-Poly1305. Then, we hash the encrypted payload into a ciphertextHash using Keccak256.

Signing the Payload with Phantom Wallet

Next, we use Phantom to sign the payloadHash using signMessage.

Internally, Phantom Wallet only allows for ASCII encoded strings to be signed to prevent any wallet drainers from signing arbitrary bytes. For us this means that we take the payloadHash and base64 encode it. Phantom then actually directly signs the base64 string (NOT: the payloadHash directly) of the payloadHash to get the signature. Keep this in mind when verifying the signature against the payloadHash.

Packing the Transaction & Send

Lastly, we pack all the information we collected during previous steps into an info struct that we send into the Solana Gateway program. We encode the function data. Finally, we set the tx_params. Please make sure to set an appropriate gas amount for your contract call, here we used 150k gas. For the value of the TX, we send over the estimated callback gas that we calculated above.

Now that you know how to correctly format and package data for the Solana Gateway program, let's learn how to connect your program to a frontend 🚀

Connecting Your Solana RNG Program to Frontend

Open a new terminal window and cd into solana-rng/solana-frontend:

Install the dependencies:

Initializing the Solana Client

Now it's time to run the progam! In the terminal:

Congrats! You now have your very own Solana RNG program deployed on Secret Network and can request encrypted random numbers on Solana!

Summary

In conclusion we constructed and encrypted a payload for SecretPath for Solana direct in the Frontend as well as calling the SecretPath gateway program.