Explore the flow
See OrdoCode build and prove a contract, step by step
A demo example — not a live run on your codebase — so you can see the shape of every output before we run the pipeline on your own contract.
Example contract · DAO treasury, 3-of-5 multisig01 · Describe — tell us what the contract should do
→ Product description02 · Review — approve the specification
→ Approved specificationThis is your contract logic written as a specification — structured, unambiguous language your team and OrdoCode both read the same way. It's the source Build and Prove work from.
Scenario: Execute Withdrawal Preconditions – approvals(id) ≥ 3 of 5 current signers – 24h have elapsed since the final approval Postconditions – funds transfer exactly once, for the approved amount – executed(id) becomes true Main Flow 1. Signer calls execute(id) 2. Contract checks approvals ≥ threshold 3. Contract checks the 24h timelock has elapsed 4. Contract transfers funds, marks executed(id) = true Key Invariants INV-CP-001 approvals never drop below threshold mid-execution INV-TL-001 execution is blocked until the timelock fully elapses INV-SEC-002 only the approved amount ever leaves the treasury
03 · Build — generate the contract and tests
→ Solidity code + test suite ⏱ 0:00Shown here: one representative function and its tests, not the full contract — this demo focuses on the withdrawal rule the spec above describes.
04 · Prove — verify the properties that matter
→ Tests + formal proofs ⏱ 0:0005 · Deploy — get the code and the evidence
→ Ready to hand offTreasury.sol — production-ready Solidity, yours to keep.
5 / 5 passing Foundry suite, checked in as test/Treasury.t.sol.
Lean 4 proof package for the property you approved — a machine-checked mathematical proof, not a sample.
Product description and specification — the same terms your team and your auditors both read.
Everything is downloadable as a project you own.