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
Every rule in this thread is written down Check a hash 👉 qdit.app/verify
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
Records stay live, by design Stellar archives storage nobody touches. In v2, every write extends the record, the project, its roster and the contract to 120 days. An idle record is archived, not deleted, and anyone can restore it with one command.
1
3
What @qdit/verify trusts, and what it doesn't It doesn't trust our app, our database, a proof file's own root, or look-alike copies of our contract. It does still trust the RPC node, because simulation results aren't signed. So you can point it at your own.
1
6
What one leaf locks in place Every milestone in a batch becomes one leaf: a domain tag, the project, the milestone, its version and its proof hash. Each field blocks a specific trick, like replaying a proof on another project. And a lone last node is promoted, never duplicated
1
8
You approve the hash you saw 👀 An approval names the exact proof hash the approver reviewed. If someone resubmitted in the meantime, the call is refused (ProofMismatch). A resubmission clears every approval, any one approver can reject, and Approved is final.
1
9
No admin. No back door milestone_proof_v2 has no admin key, no override and no upgrade entry point. Every write needs the signer's own signature, and roles come from storage, never from an argument.
1
10
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
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
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
120 milestones, one transaction We anchored a 120-milestone batch on the new contract for 0.08 XLM total, and all 120 inclusion proofs checked out on chain. Re-running the benchmark on the current contract: 120.3x lower fee at 100 milestones. Every tx is linked in the repo.
1
18
Approvals that need the whole team 🤝 Our new Soroban contract keeps each project's roster on chain. Submitters anchor proofs, approvers sign them, and a milestone is approved only when enough approvers sign the same proof hash. All 14 contract calls are covered by our testnet
1
2
39
Week three, shipped 🚀 Five things that landed on qdit between Nov 12 and Nov 20 🧵👇
1
1
4
262