Quantum dApp Hackathon 2026
Build quantum-secure dApps on Quranium, sign in with QSafe, and submit your project for review. The best five earn the Quranium Flagship dApp designation — plus grants, incubation, audits, and ecosystem integration.
From zero to submitted
Seven steps, in order. Everything below is free, runs on testnet, and takes about 30 minutes end to end before you write a line of your own code. Cards with an arrow open the tool in a new tab.
Download QSafe from the Chrome Web Store
Open store ↗QSafe is the post-quantum wallet you sign in with — it holds the SLH-DSA key that signs your login challenge and your contract deploys. Install it, then pin it to your toolbar.
chromewebstore.google.com/detail/qsafe-wallet
Create a wallet and select Quranium Testnet
Open QSafe, create a new wallet (or import an existing recovery phrase), then pick Quranium Testnet from the network selector. Write your recovery phrase down offline — nobody from Quranium will ever ask for it.
- Network
- Quranium Testnet
- Chain ID
- 4062024 (0x3dfb48)
- Currency
- QRN
- RPC URL
- https://tqrn-node1.quranium.org/node
- Explorer
- https://testnet.qrnscan.com
Claim testnet QRN from the faucet
Open faucet ↗Deploys cost gas. Paste your QSafe address into the Google Cloud Web3 faucet and claim testnet QRN — sign in with a Google account, pick Quranium → Testnet. Funds land in under a minute.
Fallback if the Google faucet is rate-limited: faucet.quranium.org. Testnet QRN has no monetary value and is not the prize token.
Sign in to this portal with QSafe
Hit the button below. QSafe pops up with a one-time challenge, you approve it, and your post-quantum signature is verified server-side. No password, no email, no seed phrase ever leaves your machine.
Deploy your smart contract on Qremix
Open Qremix ↗Qremix is Quranium's browser IDE — write, compile, deploy, and debug Solidity without installing anything. It is the fastest path to a deployed contract address, which your submission needs.
- Create a new .sol file and paste your contract.
- Open Solidity Compiler and compile — fix any errors before continuing.
- Open Deploy & Run and set Environment to Injected Provider — QSafe.
- Confirm the banner shows chain 4062024. If it shows anything else, switch networks inside QSafe and reload.
- Hit Deploy and approve the SLH-DSA signature in the QSafe popup.
- Copy the deployed contract address and the transaction hash. You will need both.
Prefer local tooling? Point Hardhat or Foundry at https://tqrn-node1.quranium.org/node — but the deploy transaction still has to be signed by QSafe to be valid.
Check your transaction on QRNScan
Open explorer ↗Paste your transaction hash or contract address into QRNScan, the Quranium testnet explorer. Confirm the status reads Success and that the contract shows up with your wallet as the deployer.
- Transaction view: status, block, gas used, and the raw post-quantum signature blob.
- Contract view: read/write methods you can call straight from the browser to smoke-test your dApp.
- Address view: full transaction history — useful evidence for judges.
A submission whose contract address does not resolve on QRNScan does not pass the hard gate. Check this before you submit, not after.
Submit your project and track review
Go to submit →Fill in your project details, attach your build, and watch it move through Submitted → Under review → Shortlisted → Accepted, with reviewer feedback attached. You can update your entry until the deadline.
Submission checklist
Required
- Public repository — GitHub, GitLab, or equivalent, with a README that explains how to run it.
- Deployed contract on Quranium testnet, using the ql1evm / SLH-DSA signing path. This is a hard gate.
- Project name, track, tagline and description — at least 20 characters of description.
- Project zip — up to 25 MB. Exclude node_modules and build output.
- A working build — judges must be able to run it.
Strongly recommended
- Demo video, 2–4 minutes, unlisted is fine. This is the single highest-leverage thing you can add.
- Live demo URL so judges can click rather than clone.
- Team name and members, with roles.
- Verified contract source so the code on-chain matches the repo.
- A short architecture note on where post-quantum crypto actually sits in your design.
$1,000,000 in QRN
Awards are stated in USD and paid in QRN — the conversion basis is fixed in the official rules. On top of the cash ladder: incubation, security audits, ecosystem integration, follow-on grant eligibility, and a participation POAP for every valid submission.
| Placement | Award | Beyond the prize |
|---|---|---|
| 1st — Flagship dApp | $300,000 | Incubation + audit + ecosystem integration |
| 2nd | $220,000 | Incubation + audit |
| 3rd | $150,000 | Incubation |
| 4th | $100,000 | Grant eligibility |
| 5th | $80,000 | Grant eligibility |
| Best in Track ×6 | $20,000 each | One per track — $120,000 total |
| Bounties & participation | $30,000 | Special bounties + POAP + testnet QRN |
Prize payouts are made in QRN and are subject to identity verification and to the eligibility rules of your jurisdiction. The QRN conversion basis, any vesting, and the full prize terms are published with the official rules.
How you'll be scored
Every submission is scored 1–10 on each criterion and weighted as below. Before scoring starts there is one pass/fail gate: the project must be deployed on Quranium testnet and use the ql1evm / SLH-DSA path.
| Criterion | Weight | What judges look for |
|---|---|---|
| Innovation | 25% | Is this new, or a port of something that already exists? |
| Technical quality | 20% | Code quality, tests, contract safety, correct use of the ql1evm path |
| Real-world utility | 20% | Does someone actually need this? Who is the user? |
| User experience | 15% | Onboarding, clarity, and how the QSafe flow feels |
| Scalability | 10% | Does the design survive real traffic and real data? |
| Quantum security | 10% | How meaningfully does it use post-quantum primitives? |
Everything you need, in one place
QSafe wallet ↗
Post-quantum wallet. Required for login, deploys, and every signed transaction. v4.8.3+.
Qremix IDE ↗
Browser IDE for writing, compiling, deploying and debugging Quranium and EVM contracts.
QRNScan explorer ↗
Testnet explorer for transactions, addresses and contracts — plus read/write contract calls.
Testnet faucet ↗
Google Cloud Web3 faucet for Quranium testnet QRN. Legacy fallback at faucet.quranium.org.
Chain & explorer docs ↗
API references and network documentation for building against Quranium.
Add the network manually
If Quranium Testnet is not already listed in your tooling, these are the exact values.
- Network name
- Quranium Testnet
- RPC URL
- https://tqrn-node1.quranium.org/node
- Chain ID
- 4062024 · 0x3dfb48
- Symbol
- QRN
- Explorer
- https://testnet.qrnscan.com
- Gas price
- 1 gwei
Common problems, fixed
“Sign in with QSafe” does nothing
Almost always an outdated extension. Update QSafe to v4.8.3 or newer, unlock the wallet, and reload this page. If the popup is blocked, click the QSafe icon in your toolbar to bring it forward.
Qremix shows the wrong chain
Switch to Quranium Testnet inside QSafe first, then reload Qremix and re-select Injected Provider — QSafe. The banner must read chain 4062024.
Deploy fails or runs out of gas
Check your balance on QRNScan — you need testnet QRN from the faucet. Gas price on testnet is 1 gwei; if you overrode it manually, clear the override and let the wallet estimate.
MetaMask can't sign my transaction
Expected. Quranium transactions are signed with SLH-DSA, a post-quantum scheme that ECDSA wallets do not implement. Route connect, sign, and deploy through QSafe.
My zip is over the limit
The cap is 25 MB. Delete node_modules, dist, build caches and large media, then re-zip. Host big assets externally and link them in your README.
My transaction is not on the explorer
Give it a block or two, then search the hash again. If it never appears, the transaction was never broadcast — re-deploy and watch for the QSafe confirmation popup before closing the tab.