GENNY / COMMITMENT 002

Shared treasury.

The team can propose a spend. The vault executes it only after the required approvals. The community follows the rule and its results.

◌ SAMPLE DATA · NOT VERIFIED

Example approval thresholdDEMO VIEW

2 / 3

Two independent signers must approve an ordinary treasury transfer in this example policy.

RULE: No single signer can move the example treasury funds under its ordinary transfer path.*

Pending proposals

EXAMPLE PROPOSAL #001AWAITING APPROVAL

Fund the community campaign

An illustrative spend request. A real proposal would show the asset, amount, destination, purpose, proposer, creation time, and exact transaction payload before signers approve it.

1 / 2 REQUIRED APPROVALS · DEMO

RECIPIENTUnspecified in demo

EXECUTIONBlocked until threshold

What the community sees

Proposal details appear before funds move. After execution, the same card links to the confirmed transaction. If rejected or expired, its history remains visible.

Signer 01Example approval

Signer 02Awaiting

Signer 03Awaiting

Treasury activity

ActionSourceAmountStatus

Campaign fundingExample proposal #001Team treasuryUnspecifiedAWAITING APPROVAL

Executed transfersNone in this demo——NO LIVE DATA

01 / VAULT ADDRESS

Inspect the funds.
A real page links to the treasury account and token balances.

02 / RULE HISTORY

Inspect the control.
Threshold, signer, and timelock changes remain visible.

03 / EXECUTION PROOF

Inspect the spend.
Each executed proposal links to its on-chain transaction.

*Example rules only. A real multisig can have other roles, permissions, spending limits, recovery paths, and upgrade rights. GENNY must display the actual deployed configuration and disclose any path that can bypass a threshold. Shared approval limits single-key control; it cannot guarantee that signers will make good decisions or remain independent.