A developer-owned workspace for Solidity compilation, voluntary EVM migration, public testnet inspection and no-value testing tokens.
QSL Foundation is merged: Intent, Capability, private-state primitives, verifier boundaries and settlement adapters are now documented at QSL Sovereign Layer status ↗. Production proof cryptography and Public Testnet QSL deployment remain gated.
Public QENOVRA testnet is not configured. Transaction broadcasting and faucet are disabled.
01 / CONTRACT STUDIO
Compile & deploy Solidity
Build small, self-contained Solidity contracts with a pinned compiler. Inspect the ABI and bytecode, then send a deployment transaction from your own wallet to the verified public QENOVRA testnet.
Compiler rule: Solidity 0.8.26 is the Contract Studio reference compiler, not a chain-wide requirement. Existing projects may use another compatible Solidity version locally. For the current QENOVRA Public Testnet, explicitly target shanghai, and when verifying source choose the exact compiler version that produced the deployed bytecode.
Optional: upload up to 12 .sol files (72 KB total). Relative import paths are preserved when you choose a project folder. Files stay in your browser until you compile.
Compiler outputs and safety warnings appear here.
Your own wallet signs deployment. Unlinked libraries require manual tooling.
Wallet never sends its private key to the website or AI.
DEPLOYED CONTRACT / INTERACTION
Read & write the deployed contract
Contract calls use the ABI you just compiled. Read calls use eth_call; write calls are signed by your own wallet and appear in the public explorer.
Deploy a contract to enable ABI-driven interaction.
02 / VERIFIED MIGRATION
Prove you control the source contract.
Only official verified controllers can use the QENOVRA migration workflow. A copied source file is not ownership evidence. An approved testnet migration creates a new contract; balances, approvals, liquidity and old users remain on the source chain unless separately migrated.
Proxy admins, contract-based owners and multisigs require additional governance checks. Verified-source lookup needs an explorer API key; secure verification needs dedicated source RPC and challenge storage.
03 / READ-ONLY EXPLORER
Inspect the public testnet.
A lightweight read-only RPC viewer for current blocks, transaction details, receipts and account balances. Use the official Blockscout-compatible explorer when available; direct RPC remains the source of truth for chain state.
The public testnet provides no-value faucet tokens. The faucet uses a separate low-balance server wallet, CAPTCHA, persistent per-address/IP limits and a global transaction lock. No mainnet token is distributed here.
One claim per address and IP per 24 hours.
Faucet not yet funded/configured. Do not reuse any internal QA keys.
05 / LOCAL TOOLING
Use Hardhat or Foundry with QENOVRA.
Bring your own project: develop Solidity in your own editor/toolchain, then upload the required .sol sources here or deploy directly by RPC. Read the project guide ↗
New developer? Start from installation and follow the complete zero-to-deploy guide. Open Developer Quickstart ↗
The public testnet is standard EVM JSON-RPC. Keep signing keys local and use a dedicated no-value testnet wallet. The templates below pin the same Solidity/EVM settings used by Contract Studio.
Hardhat
Chain ID 7992501, RPC https://rpc-testnet.qenovra.com. The downloadable sample uses Solidity 0.8.26, EVM shanghai, optimizer 200 runs. 0.8.26 is a sample baseline, not a mandatory compiler for every project. Use your project's exact compiler version and keep the EVM target on shanghai until QENOVRA announces an EVM upgrade.
Use the same RPC. The sample template uses Solidity 0.8.26 and shanghai; existing projects may use a different compatible Solidity compiler. Keep evm_version = "shanghai" for the current testnet and verify with the exact compiler version used for deployment. Keep private keys in a local keystore or hardware wallet—not in foundry.toml.