qdit (@tryqdit) header
qdit (@tryqdit) profile picture

Proof-backed milestones for Soroban Teams https://teapawt.net/t.co/6gGFd9UAi1 grant recipient from @StellarOrg

Joined October 2026
Inside v2 Last week we showed what our new contract does. This one is how it works: the rules, the hashing, what our verifier trusts, and how it reaches the app ๐Ÿงต๐Ÿ‘‡
1
10
Five steps to the app The app still anchors through v1. The plan to move it is written and open for review, nothing built yet: read v2 โ†’ register on v2 โ†’ approve through v2 โ†’ batch โ†’ opt-in for existing projects. v1 records stay readable forever.
1
1
Every rule in this thread is written down Check a hash ๐Ÿ‘‰ qdit.app/verify
Week three, shipped ๐Ÿš€ Five things that landed on qdit between Nov 12 and Nov 20 ๐Ÿงต๐Ÿ‘‡
1
1
4
262
Don't trust us. Check the chain @qdit/verify checks a qdit milestone without our app or database. It reads the contract straight from Soroban RPC, so it needs no key and no fee, and it tells you why a check fails.
1
12
Anyone can check a hash Paste a transaction hash at qdit.app/verify and the network answers. No account needed. The landing page now shows live sign-ups (80 builders and counting), and qdit links get a proper preview card. Try it ๐Ÿ‘‰ qdit.app/verify
11
80 builders have joined qdit so far We're seeing more projects being created, tasks tracked, and milestones verified on-chain. A quick look at our numbers: โ†’ 66 projects created โ†’ 229 tasks tracked โ†’ 635 on-chain contract calls, zero failures
1
1
48
~0.0695 XLM per transaction (last 40 anchors) Every milestone carries a proof anyone can check. Track the work. Keep the proof.
1
30
โ†’ ~0.0695 XLM per transaction (last 40 anchors) We're building qdit around one idea: every milestone should have proof anyone can independently verify. Track the work. Keep the proof.
10
Week two, shipped ๐Ÿš€ Three on-chain upgrades that landed on qdit between Nov 8 and Nov 12 ๐Ÿงต๐Ÿ‘‡ Built on @StellarOrg & @PHI_Stellar
1
1
2
49
One root, every proof still checks out Each milestone in a batch can be verified on its own: a few hashes lead from it to the root on chain. It ships as @qdit/merkle and the qdit-batch CLI. Approvals still happen per milestone.
1
7
A new wallet gets a fix, not an error A wallet with no account on the network used to hit a raw "Account not found" when anchoring. Now qdit tells you what's wrong and offers to fund it with Friendbot in one click. Try it ๐Ÿ‘‰ qdit.app
6