Veridian Contracts is an original Soroban workspace for recording transparent project goals and contribution commitments on Stellar. It stores public project state and emits events, while wallet UX, indexing, evidence, and payout policy remain separate concerns.
- Registers multiple projects under numeric identifiers.
- Requires the declared owner to authorize registration.
- Stores a project name, goal, owner, raised amount, and active flag.
- Records positive contribution amounts after contributor authorization.
- Allows the owner to pause or resume a project.
- Allows the owner to update project metadata without lowering the goal below the amount already recorded.
- Stores milestones and lets the owner add or complete them with auditable events.
- Exposes project and milestone read methods for the backend indexer.
- Emits
project,status, andcontributionevents for indexers.
The registry does not transfer tokens, custody funds, or declare that an off-chain payment is final. It records an auditable commitment signal. Any payout, refund, or dispute mechanism should be a separate audited change with its own threat model.
Frontend -> Backend read model -> Soroban RPC -> ProjectRegistry
|
+-> events -> indexer -> read model
The root Cargo workspace is initialized with contracts/project-registry as its first member. The contract creates an empty milestone vector for every registered project, so indexers can query a stable project-plus-milestone shape from the first transaction.
- Add milestone evidence hashes and event history.
- Add controlled project metadata updates.
- Add generated clients shared with the backend repository.
- Add a separately reviewed payout adapter rather than coupling custody to registry storage.
Open an issue before contract work, include authorization and storage reasoning, create a branch from develop, and submit a focused pull request into develop. Never commit secret keys or deployed credentials. Drips recognition is controlled by the applicable program and maintainers.
MIT. See LICENSE.