Devnet Testing Phases
For the Multi-Ledger Rollup to transition from it's current "Devnet" implementation to its public "Testnet" phase, it will need to pass a variety of public tests which will be performed in a particular testing schedule.
Note that each phase will be analysed carefully at multiple levels (smart contract, rollup, accounts,...) to ensure multi-ledger consistency. And therefore we will proceed through these key tests at a reasonable pace.
The key tests are summarised below (more maybe added if required):
| Test | Description | Notes |
|---|---|---|
| Proxy Contract Connections | Public test to integrate to selected proxy contracts | |
| QNT Deposits | Public test to ensure that QNT tokens (from Ethereum Sepolia Testnet) correctly maps to native tokens of the Multi-Ledger Rollup for multiple users | |
| ETH Deposits | Public test to ensure that ETH tokens (from Ethereum Sepolia Testnet) correctly maps to ETH tokens of the Multi-Ledger Rollup for multiple users | |
| POL Deposits | Public test to ensure that POL tokens (from Polygon Amoy Testnet) correctly maps to POL tokens of the Multi-Ledger Rollup for multiple users | |
| AVAX Deposits | Public test to ensure that AVAX tokens (from Avalanche Fuji Testnet) correctly maps to AVAX tokens of the Multi-Ledger Rollup for multiple users | |
| Multi-Ledger Token Deposits | Public test to ensure that the same token with three different versions (one on Ethereum Sepolia Testnet, one on Polygon Amoy Testnet and one on Avalanche Fuji Testnet) correctly maps to one single token on the Multi-Ledger Rollup for multiple users | |
| Multi-Ledger Rollup Contract Upgrade Tests | Public test to ensure upgradeability of all of the smart contracts on the connected blockchains, to incorporate new features | |
| Multi-Ledger Rollup Node Upgrade Test | Public test to ensure that the Multi-Ledger Rollup nodes can be upgraded for new features | |
| Deploy whitelisted smart contract test | Any Multi-Ledger Rollup user can deploy one of the Quant whitelisted smart contracts | |
| Deploy bespoke smart contract test | Any Multi-Ledger Rollup user can deploy one of their own smart contracts | |
| Deployed smart contract permissions check | Any Multi-Ledger Rollup user can promote their deployed smart contract to permissioned access, and can request their smart contract to be public | |
| Smart contract permissions check | Any Multi-Ledger Rollup user with a deployed smart contract can whitelist other users to read and write to this smart contract. Before being whitelisted, other users cannot access this smart contract | |
| Default smart contract access test | Any Multi-Ledger Rollup user can always read and write to public smart contracts and any smart contracts that this user deployed | |
| Account permissions check | Any Multi-Ledger Rollup user can read the transaction history and the QNT balance of the accounts that it has used | |
| QNT Withdrawals | Public test to ensure that QNT tokens (from the Multi-Ledger Rollup) can be correctly withdrawn back to the Ethereum Sepolia testnet for multiple users | |
| ETH Withdrawals | Public test to ensure that ETH tokens (from the Multi-Ledger Rollup) can be correctly withdrawn back to the Ethereum Sepolia testnet for multiple users | |
| POL Withdrawals | Public test to ensure that POL tokens (from the Multi-Ledger Rollup) can be correctly withdrawn back to the Polygon Amoy testnet for multiple users | |
| AVAX Withdrawals | Public test to ensure that AVAX tokens (from the Multi-Ledger Rollup) can be correctly withdrawn back to the Avalanche Fuji testnet for multiple users | |
| Multi-Ledger Token Withdrawals | Public test to ensure that a multi-ledger token can be correctly withdrawn to the blockchain that the user chooses to (one of Ethereum Sepolia Testnet, Polygon Amoy Testnet or Avalanche Fuji Testnet) for multiple users |
Updated 5 days ago