Testnet Guide
Last updated
Last updated
This guide will walk you through the process of interacting with Curie Testnet.
To get started, make sure you have MetaMask installed, added the Polygon Mumbai Network, and test tokens in your wallet.
Install MetaMask: Install the MetaMask wallet extension in your browser.
Add Network: For this tesnet, we use Polygon Mumbai Network.
In MetaMask, click on the network selection icon in the upper left corner and choose Add network.
Select Add a network manually.
Enter the following fields and click Save.
Network Name: Matic Mumbai
New RPC URL: https://rpc-mumbai.maticvigil.com/
Chain ID: 80001
Currency Symbol: MATIC
Block Explorer URL: https://mumbai.polygonscan.com/
Once added successfully, you will be switched to Polygon Mumbai Network.
Requesting Testnet Tokens: To request testnet tokens, submit your Metamask wallet address using this form. We will send you a set of test tokens: CI and DIA.
Adding CI and DIA Test Tokens to MetaMask: On MetaMask, click + Import Tokens.
Enter the following fields:
Token contract address: 0x0B9373fe8F12df3bBE2342336a20C4D26cb695F2
Token symbol: CI
Token contract address: 0xB5D73C9864223197AD8A1de1e743064D340670c7
Token symbol: DIA
Once added, you should see the tokens listed in your wallet. Please allow up to 24 hours to receive your tokens via the faucet. Happy testing!
To begin testing, follow these steps:
Visit the Testnet page.
Connect your MetaMask wallet.
Select either CI or DIA token and enter a swap amount. Make sure the entered amount is less than your token balance.
Select the other token and Request approval. Sign on MetaMask to approve.
Once approved, go back to Curie then click Swap. Sign again on MetaMask.
While the swap is processing, you'll see a round and order number (See Image). This indicates where the transactions will be placed in the bundle.
After the swap is completed, a green check mark will pop up in the bottom right corner. Head to History and Completed section, where you can confirm the same commitment number was processed as promised.
Users encrypt transactions to prevent the sequencer from manipulating the transaction order. To ensure a secure and trustless process, we use cryptography and zero-knowledge proofs to verify the integrity of the encryption.
The round and order numbers shown indicate where the transactions will be placed in the bundle for fast pre-confirmations and transaction inclusion guarantee in the order determined by the sequencer.
To verify that the transactions were ordered properly, we suggest having multiple testers swap simultaneously and checking each other’s order numbers.
We also have a demonstration of how proofs are submitted to DA layer in this video demo, reducing data availability costs for transaction order validation.
