Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn the basics of working with the EVM Developer Toolkit
Learn how to connect your Metamask wallet address to a Secret wallet address.
Connect your Metamask wallet here to receive your Secret testnet wallet address
Fund your Secret testnet wallet address with the testnet faucet
Now you have a Secret testnet wallet address that you can use to sign transactions with your Metamask wallet!
Secret Network currently supports two cross-chain messaging solutions:
(recommended)
There are currently 10+ supported chains. See the to review supported chains.
See the Axelar to review supported chains.
Secret Network's EVM Toolkit is a cross-chain messaging and confidential computation SDK for EVM developers.
The toolkit allows EVM developers to build novel cross-chain applications such as private DAO voting mechanisms, secure random number generation (Secret VRF), confidential data access control via EVM NFTs, encrypted DeFi order books, and more.
Secret Network currently supports two cross-chain messaging solutions:
SecretPath (recommended)
There are currently 10+ supported chains. See the Gateway contracts to review supported chains.
Axelar GMP
See the Axelar Gateway contracts to review supported chains.
To use SecretVRF (Random Number Generation) over SecretPath please checkout this tutorial Implementing VRF into any EVM Contract.
If you like to use Encrypted Payloads to store data in a KV store, please look at the Key-Value store Developer Tutorial.
Here you'll find a more in-depth overview with a detailed description of what the two core primitives (Gateways & Relayers) do. First, let us give you the core idea on what SecretPath really hinges on.
The core idea of SecretPath is the following:
The "master private gateway" is a confidential smart contract living on Secret Network.
Since this contract is confidential by default , we can store a (secret) private key, which only this smart contract can use to sign messages/packets and is unknown to the operators or to any contract administrators.
The only trust assumption that we have for this bridge model to work is therefore that the private key does not leak out the TEE (trusted execution environment)/confidential computation environment. In case the TEE breaks and that private signing keys could potentially leak, the encryption and verification keys can be rotated to new ones, keeping the bridge intact. Since we only rely on a smart contract to handle the core bridging functionality, we call this trustless. Some may argue that since we are using TEE's, we are not completely trustless but instead trust-minimized.
Everything else around this "master private gateway" is untrusted. We only use a lot of consistency checks and hashing to ensure that data weren't manipulated along any transmission path.
As outlined in the overview, the primary functions of the Gateway are:
For the "master public gateway" that is on a public blockchain, that means only verification of signatures. In our case, this public gateways verifies all secp256k1 signatures signed by the user or by the master private gateway.
The private master gateway does verification of the secp256k1 signed and encrypted user payloads. It also signs all outgoing messages using secp256k1 so that other user made private contracts as well as the public gateway contract can verify the validity of the message/packet.
Both gateways also handle serialize/deserialize operations. They convert contract inputs into correctly formatted packets and vice versa, while also doing the appropiate conversions between base64 (mainly used for secret) and hex (mainly used for EVMs) inputs.
Third, gateways on privacy-preserving chains can re-encrypt their inputs under the key of the final compute contract. The master private gateway can handle encrypted or unencrypted payloads. In the case of encrypted payloads, the payload is encrypted using a shared key that is generated via ECDH from a users randomly generated private key and the gateways encryption public key. We use the well known Chacha20-Poly1305 to do the symmetric encryption using that shared key.
SecretPath consists of two core primitives: relayers and gateways.
Gateways are the onchain smart contracts that handle the broadcasting, receipt, packaging, and verification of messages. Gateways are also the mechanism by which application developers will interface with the SecretPath protocol.
These gateways are relatively simple and generic, primarily consisting of two capabilities. First, gateways can handle signature operations. For gateways on public blockchains, that means verification; for those on privacy-preserving blockchains, that means verification as well as signing. Second, gateways handle serdes operations: converting contract inputs into correctly formatted packets and vice versa.
Relayers watch for messages on one chain and then call another chain with that message. For SecretPath, the primary security-related concern is liveness, not resistance to node collusion or censorship. The relayer is not tasked with relaying funds/tokens from one chain to another, but rather with watching for encrypted messages that need to be passed. The relayer does not have access to encryption keys that can decrypt these messages or signing keys to generate new valid ones, meaning that the relayer cannot compromise the data in security or correctness.
The most a relayer can do is to not transmit the data as requested, which would cause liveness problems for the network, but would not compromise user funds, smart contract applications, or sensitive data. This also makes the requirements for running a relayer significantly lower: a relayer needs only to be able to watch for transactions on host chains and create transactions on destination chains based on those host chain transactions.
Gateways are the onchain smart contracts that handle the broadcasting, receipt, packaging, and verification of messages. Gateways are also the mechanism by which application developers will interface with the SecretPath protocol.These gateways are relatively simple and generic, primarily consisting of three capabilities.
First, gateways can handle signature operations. For gateways on public blockchains, that means verification; for those on privacy-preserving blockchains, that means verification as well as signing.
Second, gateways handle serialize/deserialize operations: converting contract inputs into correctly formatted packets and vice versa.
Third, gateways on privacy-preserving chains can re-encrypt their inputs under the key of the final compute contract.
For more background on how the high-level architecture of SecretPath differs from that of other interoperability networks, see section 4 of the Snakepath whitepaper.
Learn how to use Axelar General Message Passing in order to send messages between EVM chains and Secret Network
Learn how to use Axelar General Message Passing in order to send messages between EVM chains and Secret Network
Axelar enables secure interchain communication and token transfers, spanning consensus methods including Cosmos and Ethereum. Through the use of General Message Passing (GMP), developers building on Ethereum can execute smart contracts on Secret and vice versa. This means complete composability across Web3.
With GMP you can:
Call a contract on chain B from chain A.
Call a contract on chain B from chain A and attach some tokens.
Need help with using SecretPath or want to discuss use cases for your dApp? Please ask in the Secret Network Telegram or Discord.
SecretPath is a protocol for lightweight, secure, privacy preserving message-passing between chains. Its purpose is to serve as a critical building block for bringing private data onchain in a useful yet privacy-preserving manner.
In technical terms, SecretPath is a message passing system for non-malleable, trustless interchain message passing. In more practical terms, SecretPath enables public chains to call arbitrary functions on private compute chains while preserving the privacy of the inputs and validity of the outputs. SecretPath is built using a primitive that we call TNLS ("Transport Network Layer Security") which is effectively a blockchain derivative of the TLS protocol.
SecretPath itself does not store or compute over data. Rather, it connects public blockchains and their applications to privacy-preserving computation networks. This design allows public blockchain applications to build and operate private computation contracts on privacy-preserving chains while keeping their primary smart contract logic and liquidity on public blockchains.
Ultimately, SecretPath enables the building of new applications that combine the transparency, UX, and latency benefits of public blockchains with the trust-minimized and private computation features of privacy-preserving blockchains.
The following sections provide a detailed technical overview of the current relayer and gateway architecture for SecretPath.
To get an overview of the Architecture go here: Architecture Overview
If you like to use SecretVRF in the most elegant way for you as an EVM developer, go here:VRF Developer Tutorial
To review supported EVM chains, go here: Supported Networks
As an user and developer, all you need to know is how to send messages to one gateway/receive messages from a gateway, which will be covered in those respective documentation sections. More tutorials with encrypted payloads are coming soon.
As a maintainer, you might want to look more closely at the relayer section of the codebase as well here: https://github.com/SecretSaturn/SecretPath
You can try a demo of SecretPath that bridges Secret VRF into EVMs here: vrfdemo.secretsaturn.net
This documentation was adapted from https://fortress-labs.gitbook.io/snakepath, courtesy of Leor Fishman.
Learn how to use Axelar General Message Passing in order to send messages between EVM chains and Secret Network
In this tutorial, you will learn how to use Axelar GMP to send a string
between Polygon and Secret testnets. To learn more about the flow architecture, see the Axelar documentation here.
For GMP to work, both chain A and chain B must be EVM or Cosmos with a deployed Axelar Gateway contract. For this tutorial we will be using the Polygon testnet Axelar Gateway contracts. We will go into this in more detail momentarily.
Have Metamask installed, Polygon Mumbai Network added to your wallet, and your wallet funded with Polygon tokens.
Add Polygon Mumbai Network to your Metamask wallet by navigating to the Polygon testnet explorer and clicking "Add Mumbai Network" in the bottom righthand corner of the homepage.
In order to execute a smart contract on Secret network, you must first upload and instantiate a smart contract on Polygon that can execute messages using Axelar GMP. Axelar has a github repository of example contracts that can be used for GMP. We will be uploading the SendReceive.sol contract to Polygon for this demo.
The Cosmwasm smart contracts in this Axelar repository are not compatible with Secret Network out of the box due to dependency issues. However, we will modify the SendReceive contract to be compatible with Secret Network.
To upload the contract, we will use Remix Online IDE, which is a powerful toolset for developing, deploying, debugging, and testing Ethereum and EVM-compatible smart contracts.
First, navigate to Remix and create a new blank workspace:
Next, create a new file called SendReceive.sol
and paste the Axelar GMP solidity code. This will autofill your workspace with the necessary dependencies for your SendReceive.sol contract 🤯
Now all that's left is to compile and upload the contract. Navigate to the Solidity compiler using the sidebar and click "Compile SendReceive.sol". Then, navigate to "Deploy and run transactions." Toggle the Environment from "Remix VM (Shanghai)" to "Injected Provider - MetaMask" and make sure that in your MetaMask wallet you have currently selected Mumbai network.
The constructor
of SendReceive.sol contains 3 variables that you must now input in order to instantiate the contract and link it to Axelar's Polygon gateway contract and gas receiver contract, as well as the Polygon Mumbai chain name:
Input these strings like so and then click "Transact":
Upon successful instantiation, the contract address will be returned in the Remix terminal, which you can then view on Polygonscan. And the deployed contract can now be interacted with in the "Deployed Contracts" window:
Congrats, you've just deployed an Axelar GMP-compatible contract to Polygon testnet that can send and receive messages to and from a Secret Network smart contract 🎉
Now that you've uploaded a GMP-compatible contract to Polygon, let's do the same on Secret Network so that the contracts can communicate with each other across the Cosmos!
First, clone this Secret Network examples repository:
Then, cd
into the examples/secret-ethereum-gmp
folder
and compile the contract by running make build-mainnet
in your terminal.
If this is your first time working with a Secret contract, visit the Getting Started docs to properly configure your developer environment.
Now, open a new terminal window and cd
into examples/secret-ethereum-gmp/node
and then run npm install
to install the package.json
dependencies.
Create a .env
file in examples/secret-ethereum-gmp/node
and add your wallet mnemonic in order to upload the contract:
You can then upload and instantiate the contract by running node index.js
.
Upon successful instantiation, a Secret contract address is returned that you can then use to send messages to and from Polygon:
Now let's send a string
from Polygon to Secret! 🚀
Now that you have a GMP-compatible contract instantiated on Secret Network, you have all of the variables needed in order to send a cross-chain message using the SendReceive.sol
contract.
In order to send messages using Axelar GMP, the user prepays the relayer gas fee on the source chain to Axelar’s Gas Services contract.
You can do this in Remix by navigating to the "Deploy and run transactions" tab in the sidebar and adding gas to prepay the gas fee.
To make sure you have enough gas, add .40 Matic, (roughly .20 USD or 400000000000000000 Wei), to the transaction:
Now all that's left is to execute the transaction! From the "Deployed contracts" section of Remix, open the dropdown for the send
function, which should have three inputs: destinationChain
, destinationAddress
, and message
. Input the following:
Once you have inputed these strings and your contract address, select "transact." Congratulations! You've just sent a string
from Polygon to Secret Network! 🎉
Use Polygonscan to track the transaction on Polygon. Here is an already deployed contract for reference. Transaction times vary depending upon Poygon network congestion; you might want to "speed up" the transaction in Metamask.
Now that you've successfully executed a cross-chain message from Polygon to Secret using Axelar GMP, let's query the message on Secret Network to see if the message was actually received by the Secret contract.
First, confirm that the transaction has been successfully relayed by Axelar.
The Axelarscan status diagram indicates the following 5 steps were executed successfully:
Once the transaction has been executed successfully, you can use Secret.js to query the message:
To execute this query, navigate to the query.js
file in examples/secret-ethereum-gmp/node
and replace the contractAdress
and contractCodeHash
with your contract address and code hash, respectively.
Then run node query
.
If the message was executed successfully, the query will return the Ethereum wallet address that sent the transaction as well as the message that the wallet included:
Great work! Now let's send a string from Secret to Polygon!
To execute the SendMessageEvm transaction, navigate to the execute.js
file in examples/secret-ethereum-gmp/node
and replace the contractAdress
and contractCodeHash
with your contract address and code hash.
Then, update destinationAddress
to your Polygon contract address, and myMessage
to the message that you want to send:
Next, in order to send a GMP message from Secret to Polygon, you need to acquire some AXL tokens and include the correct IBC denom representing those tokens to your transaction to pay for gas, so that the message can be executed over IBC
Learn more about IBC denoms here.
The correct IBC denom is already included in the secret.js transaction, but in order for it to execute successfully, you need to have this IBC denom funded in your wallet. To add this token to your wallet, you can send Axelar tokens to your Secret wallet address over IBC.
If this is your first time sending Axelar testnet tokens over IBC, see an Axelar Gas Token video tutorial here, which guides you through the following steps:
Add Axelar testnet to your Keplr wallet by visiting Axelar Satellite (upon visiting the website, a Keplr notification will pop up that says, "https://testnet.satellite.money would like to add blockchain axelar-testnet-lisbon-3 to Keplr")
Procure AXL testnet tokens from the Axelar faucet.
Send AXL testnet tokens to your Secret testnet wallet address over IBC using Axelar Satellite.
Upon successful transfer, you should now see the new AXL IBC token in your Keplr Wallet:
Once you have properly configured your execute.js
file and procured the IBC denom needed to execute the transaction, all that's left is to run node execute.
The transaction should return a transactionHash
as well as data about the IBC routing:
Now, navigate to Axelarscan to monitor the status of the transaction.
And for good measure, view the transaction on Polygonscan to see that the message was received!
To actually see the message that you sent, click on "Click to see more":
And then at "Input Data", view the input as UTF-8 to reveal the decoded message! 👀
Congratulations! You now have all of the tools to send a message from Secret Network to Polygon using Axelar GMP! 🎉
In conclusion, Axelar's General Message Passing (GMP) offers a powerful solution for achieving secure interchain communication and token transfers across diverse blockchain ecosystems, including Cosmos and Ethereum. With GMP, developers can seamlessly execute smart contracts on one blockchain from another, fostering complete composability within the Web3 landscape. This documentation has guided you through the process of deploying GMP-compatible contracts on both Polygon and Secret Network, illustrating how to send messages across these networks. By following these steps, you have unlocked the potential for seamless interoperability and enhanced functionality in your blockchain applications. Axelar GMP paves the way for a more interconnected and efficient blockchain ecosystem. Congratulations on your successful journey with Axelar GMP!
If you run into any errors or questions, ping the #dev-issues channel on Secret Network's Discord and somebody will get back to you shortly 😊