Treasury oversight
Treasury policy, Safe approvals, and public execution context
The treasury layer should show how funds move from approved governance decisions into controlled multisig execution. This page is for budget guardrails, signer accountability, transaction review, and treasury transparency—not for operating the external energy system itself.
Registered Safes
2
No Safe addresses have been configured yet.
Approval baseline
3/5
Major treasury actions should clear the founding Safe approval threshold before execution.
Primary network
Ethereum
Canonical governance and treasury references currently resolve against the primary organization network.
Primary Safe
Pending
Configure the treasury Safe in Settings to turn this page into a live execution registry.
Treasury operating model
Guardrails that should be visible before any spend is executed
Treasury pages should make policy legible to members and signers: what can be spent, who approves it, what risk disclosures attach to it, and how the record is published back into governance.
Policy guardrails
activeTreasury actions should remain constrained by approved proposals, named budget lines, signer review, and time-delayed execution where appropriate.
- On-chain treasury with continuous public visibility
- Predefined budget categories for operations, security, liquidity, and grants
- Disbursements linked to approved proposals
- Emergency powers capped by value, scope, and duration
- Independent audits and staged upgrades with timelocks
- Execution authority should follow approved proposals rather than ad hoc operator discretion
RWA-linked disclosures
plannedWhere proposals touch eKWH, reserves, or oracle-linked settlement assumptions, the treasury surface should disclose the governance-relevant context without implying the DAO performs external regulated operations.
- Show collateral, reserve, and oracle reference notes when treasury policy depends on them
- Keep commercial energy operations outside the DAO execution path and outside signer authority
- Publish supporting disclosures alongside treasury proposals, not as marketing copy on the homepage
- eKWH represents verified real-world energy units
- This portal presents governance context; operational energy settlement remains outside DAO execution
Execution path
How treasury decisions should move through the portal
This keeps the governance flow explicit: proposal approval first, Safe execution second, public reporting immediately after.
1. Proposal approval
liveTreasury-impacting actions should originate in an approved proposal pack with rationale, budget scope, risk notes, and implementation detail.
- Reference the governing proposal and supporting documents
- State whether the action is operational, liquidity, security, grant, or reserve-related
- Confirm signer instructions only after voting closes successfully
2. Safe execution
activeApproved treasury actions should resolve to a named Safe, signer threshold, and verifiable transaction trail.
- Route major transactions through the primary treasury Safe
- Use purpose-specific Safes only where the policy framework allows it
- Keep signer roles aligned with council and treasury responsibilities
3. Public reporting
plannedAfter execution, the portal should publish the result back into the governance record so members can verify what happened and why.
- Record the executed transaction hash or Safe reference
- Link the completed action back to the proposal and policy basis
- Expose balances, flows, and approval history for transparency review
Registered Safes
Treasury and operations multisig registry
These entries are pulled from organization settings. Once addresses are configured, this page becomes the internal reference layer for signer accountability, explorer checks, and Safe handoff.
Unnamed Safe
Ethereum • Purpose pending
Address
No Safe address configured yet
- Signer scope: Pending governance assignment
- Network context: Ethereum
- Waiting for settings entry before execution links can resolve
Unnamed Safe
Polygon • Purpose pending
Address
No Safe address configured yet
- Signer scope: Pending governance assignment
- Network context: Polygon
- Waiting for settings entry before execution links can resolve