How requests become candidates and locked tokens become votes.
A token’s configured tax proceeds reach its vault. Platform, creator, buyback, and strategy allocations follow the deployment’s published configuration. Exact rates are shown only when available from that configuration.
A hook returns a plan; the vault validates and executes supported actions. A hook cannot directly spend the vault’s assets.
A holder writes a request. AI processing produces a candidate that must pass the configured compilation, simulation, and review checks. A local draft is neither a published proposal nor proof of completed checks.
Each round fixes its voting token when it opens. Voting and token recovery use that historical token even if the current vault token changes. During voting, tokens are transferred into the ballot. Voting power is based on the amount actually received, so transfer taxes are accounted for. Tokens remain locked until the round ends and can then be recovered under the ballot’s rules. Changing a choice does not create additional weight.
Round times, eligibility, candidate limits, and quorum come from the configured ballot. A “keep current strategy” candidate preserves the existing strategy. Finalization and strategy activation are separate steps.
The project dev can manage configured operators, pause execution, cancel pending changes, roll back eligible versions, and upgrade the vault system through the configured upgrade authority. These powers can affect future strategy behavior.
Asset rescue is restricted to unencumbered project assets. Holder claims, creator claims, voting deposits, and other established liabilities remain reserved; rescue cannot erase those debts. Actual roles and rescue limits must match the deployed contracts.
The ballot is the routine strategy proposer. The immutable protocol Guardian also has an emergency proposal path outside the ballot. That path can queue a replacement strategy; it does not edit votes or withdraw voting deposits. Activation follows the configured public delay. The dev’s emergency controls are separate from community selection.
The vault checks approved action types, assets, recipients, spending budgets, reserves, and transaction constraints. Values are configuration, not promises of investment performance.
AI output and simulations can miss failures. Market prices, external protocols, keeper availability, and upgrade authority introduce additional dependencies. Source and test evidence must be inspected for the exact deployed version.
Live records come from the connected index API. Each response shows its origin and observation time. An empty index, an unavailable service, and an unknown chain value are distinct states. The interactive demo uses clearly labelled fictional data.
This interface prepares drafts and reads public state. A wallet transaction requires exact chain, account, target, calldata, value, and contract permissions to be checked against the project manifest.
Review the exact request above. Each step is simulated before your wallet opens. A receipt, matching event, and state readback are required for confirmation.
No transaction has been sent.