- 1 Enter information
- 2 Record milestones
Fill in the sample fields below (examples are pre-filled — adjust freely).
Technical details
Each state transition builds a data object (fund info + status + step index), canonicalized and keccak256-hashed into its own on-chain record. Milestones sharing a fund ID form a sequential audit trail; the server-side relayer awaits confirmation of each transaction before the next to avoid ordering conflicts.
How it works
- 1
Declare the fund
Fund ID, beneficiary, disbursal amount.
- 2
Record each milestone
Approved → Disbursed → Received, one proof each.
- 3
Get an immutable log
The chain becomes a transparent audit trail for all parties.
The problem you face
- Funds pass through many stages (approve, disburse, confirm) but each party keeps its own record.
- At reconciliation there is no shared “source of truth”, breeding suspicion and delays.
- One link can be misrecorded or altered without the others noticing.
What you gain
- One trusted shared log. Everyone looks at one unified, time-ordered chain of proofs.
- No mid-way edits. Each recorded milestone is fixed; any cover-up leaves a trace.
- Faster reconciliation. A clear trail shortens checks and accountability.
Real-world scenario
Grant fund & contractor
A fund disburses 1.2B VND to a logistics contractor. Each milestone — approval, transfer, receipt confirmation — becomes a timestamped proof. At audit, all three parties reconcile against one chain, instead of stitching together scattered emails and spreadsheets.
Frequently asked questions
Must all parties use this software?
Not required. Anyone can verify a recorded proof without an account.
What if a milestone is recorded wrong?
You record a new corrective milestone; the old record remains, keeping the full history transparent.
Are amounts exposed publicly?
Only each milestone’s fingerprint is public, not the detailed content.