Start here

Q-Day Drill registration closes on 17 November at 23:59 UTC. Register a drill account before then if you want to compete for Q-Day Survivor. How the drill works

1. 1

   Get ready

   You need three accounts before you register. Setting them up first takes a few minutes and saves you from getting stuck halfway.

   • A GitHub account. You sign in with it and your project lives in a GitHub repository.
   • An X account. You connect it once and share your progress there with #BuildBeforeQDay.
   • The QoreX wallet: the phone app or the browser extension. Switch it to Testnet before you start.
   • For coding: Node.js 20 or newer, or the toolchain of the language you want to use (Python, Rust, Go, Java, Kotlin, Swift or Solidity).

   Get QoreX

2. 2

   Register in four steps

   Registration is free and has four parts. You can leave and come back: the page remembers where you stopped.

   • Sign in with GitHub. Your email comes from GitHub and is never shown to anyone.
   • Your details: choose your level (Quantum Pass, Intermediate, Advanced or Expert) and whether you build solo, with a team or are looking for one. Confirm you are 18 or older and accept the Terms.
   • Connect X: sign in with X, or publish the short verification post the page gives you and paste the link to it.
   • Connect QoreX on Testnet: approve the request in your wallet. If your wallet's post-quantum key is not registered on testnet yet, it sends a tiny proof transaction to your own address instead, which needs about 0.1 test QOR for the fee. Get it from the faucet first.
   • On a phone, open the registration page inside the QoreX app's browser so the wallet can connect.

   RegisterFaucet

3. 3

   Get test tokens and set up the network

   Everything in the fest runs on the QoreChain testnet. Test tokens are free and have no value.

   • Test QOR from the faucet pays your transaction fees.
   • The fest faucet also gives fUSD, fETH and fBTC test tokens once every 24 hours, for apps that need assets to move around.
   • If you connect a tool or an EVM wallet yourself, use the network details below.
   • The explorer shows every transaction and account, which is the quickest way to check that something you sent went through.

   Chain id

   qorechain-diana

   EVM chain id

   9800

   https://rpc-testnet.qore.hostCopy

   https://api-testnet.qore.hostCopy

   https://evm-testnet.qore.hostCopy

   FaucetFest test tokensExplorer

4. 4

   Build your first app

   The fastest start is the starter template: it creates a working app wired to the testnet, which you then change into your own project.

   • Run the command below, or install the SDK for your language from the Kits page.
   • Follow the quickstart to send your first hybrid-signed transaction: it carries a classical signature and a post-quantum signature together.
   • Using an AI coding assistant? The QoreChain MCP server gives it the chain's tools and docs.
   • The live workshops walk through each level step by step.

   npx create-qorechain-dapp my-dappCopy

   SDK quickstartAll kitsMCP serverDocumentation

5. 5

   Build solo or form a team

   Each category has its own team size, from solo up to four people. Check the size for your category before you invite anyone.

   • Every member registers on their own, with all four steps done.
   • Once you have created your project, invite teammates by their GitHub username from My space. They accept from their own My space.
   • Looking for teammates? Turn on Looking for a team in My space and browse the Find a team page. Contact goes through the platform and emails are never shown.

   Find a teamCategories and team sizes

6. 6

   Create your project early

   Create your project as soon as you know what you want to build, even before you write code. Start with the name, a description and your plan, then add the rest as you go, until 2 December.

   • Description and How it's made: at the start, say what you plan to build and how you will approach it. You don't need to know every kit yet; update both as the project takes shape.
   • One category. It decides the category bounty you compete for; special awards are open to every project.
   • A public GitHub repository with an MIT or Apache-2.0 licence and a README. You can link it later, but it is required by the deadline, and your commits show up once it is linked.
   • A cover image in 16:9, at least 1200 x 675 pixels, JPG, PNG or WebP, up to 5 MB. Optional: without one, we generate a cover with your project's name.
   • A video of up to 3 minutes showing the project working. It is required. You can add it any time before the deadline.
   • At least one testnet address your project uses (qor1...), so we can see it on chain.
   • The kits and network features you use. We confirm them from your repository, so only tick what is really in the code.
   • Install the QoreChain Build GitHub App on your repository from My space so your commits appear in the feed straight away.

   New projectMy spaceFull rules

7. 7

   Join the Q-Day Drill

   On 18 November, a bot plays an attacker who has recovered the classical key of your drill account and tries everything that key alone can do. The five projects that keep working and lose the least win the Q-Day Survivor award.

   • Pick a testnet account your project uses, a fresh one that has never held mainnet funds, with its ML-DSA-87 post-quantum key registered.
   • From your project page, register the drill account's classical private key and up to 5 contract addresses to attack. Registration closes on 17 November at 23:59 UTC.
   • The key you enter goes to the attacker bot and is published after the drill. Never use a key that matters.
   • During the drill, make a normal transaction from the drill account to show your project still works, and submit its hash on your project page by 19 November.

   My space

8. 8

   Keep building in public

   Progress you share during the fest helps the jury see how the project came together.

   • Post updates from My space: a short note, a link or one of your posts on X.
   • Take part in Ship Weeks challenges from My space for extra badges.
   • Join the live workshops and ask your questions there.
   • Share your progress on X with #BuildBeforeQDay.

   My spaceWorkshops

9. 9

   Be ready for the deadline

   Everything must be in place by 2 December at 23:59 UTC. There is no separate submit button: at the deadline your project becomes read only, and that version is what we check.

   • From 3 December to 5 December we check every project: public repository, licence, README, cover image, video, testnet addresses, team size, every member registered, commits made during the fest and kits we can detect.
   • Finalists may get a change request from the jury, with 48 hours to answer from the project page.
   • Judging runs from 6 December to 15 December. Winners are announced on 16 December.

   Full rules