Store event type, tx_trace_id, previous hash, payload hash, signer role, signature, and timestamp.
Money Transparency
Public payments with full cryptographic traceability.
Hashes and signatures live on-chain while sensitive files stay off-chain but remain tied to those commitments so audits can replay the full path.
Architecture
On-chain proofs + off-chain evidence
Events carry commitments, signatures, and links to the prior state. Documents sit off-chain with hashes so integrity checks still bind.
Contracts, invoices, and beneficiary metadata are content-addressed and linked by cryptographic hash.
The trace interface reconstructs full path, validates signatures and hash continuity, and returns policy compliance status.
Lifecycle
Deterministic transaction state machine
Illegal transitions fail and leave a log line. Higher-risk payment classes need more signatures before money moves.
Lifecycle steps
A payment intent becomes immutable after commitment and receives a stable trace identifier.
Role-based approvals are verified against policy thresholds before disbursement can proceed.
Disbursement emits a signed settlement event and references approved intent hashes.
Receipt evidence is anchored and reconciliation closes the chain with compliance summary.
Data Model
Minimum entities for V0-V1
This set covers proof replay, policy checks, and load tests for the early builds.
Top-level program budget commitment entity.
Initial payment proposal with purpose and destination.
Role-scoped authorization for execution.
Executed transfer event with settlement metadata.
Proof of completion from receiving side.
Post-payment consistency validation object.
Machine-readable proof package.
Dispute and review workflow object.