Spending requests
Prepare a clear request with an owner, amount, purpose, and approval path.
Learn moreExplore
Product navigation
Spending requests
Approval trails
Treasury proof
Treasury
Treasury coordination and approval trails.
Create spending requests, route them through the right approvals, and keep a clear record of every payment decision.
Start a treasury workflow.
Prepare a request, route it through review and approval, then keep the decision and payment record together for your finance team.
Start Treasury WorkflowPayment decisions
Review the right payment route before money moves and keep the decision record attached.
Learn morePayroll operations
Coordinate recurring team payments with privacy and a simple proof of completion.
Learn moreStart with the request, review the risk, and continue to payment only when the right people have approved it.
Treasury table
| Asset rail | Allocation | Value | Policy | Runtime state |
|---|---|---|---|---|
| SOL treasury | 0.02 SOL | Testnet rehearsal funded | Timelocked execution / onchain treasury PDA · display uses Testnet evidence, not USD AUM | Live |
| Confidential payroll reserve | USDC/PUSD/AUDD | Intent receipts ready | Umbra/Cloak intent receipts + scoped viewing-key audit posture | Testnet-ready lane |
| Gaming rewards corridor | Proposal-bound | Governed payout route | MagicBlock settlement evidence with proposal-bound distribution review | Routed |
| Operating reserve | Policy-bound | Review before release | Approved spending rules with a preserved decision record | Ready for review |
Treasury Review AI
Treasury execution review
Route notes attached
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
Treasury destination
Execution target pending index evidence
Baseline motion
Pending exact baseline in current evidence packet
Current motion
Pending exact amount from the indexed proposal record
Execution target
Execution target remains governed by the indexed proposal account and current DAO phase.
Recipient has limited treasury history, so destination context should stay visible before execution.
Execution delay is compact, so timing and signer context should stay explicit through execution.
Treasury magnitude is not yet present in the structured proposal payload, so payout risk should stay conservative.
Recipient disclosure is not yet present, so beneficiary validation cannot be completed from the current packet alone.
Backend-indexed proposal record: Confidential payroll batch / April (Executable). Structured execution context reads timelock-hours, execution-target directly instead of inferring them from card prose.