rewrite governance section

docs/docs/governance/community-forum.mdx

@@ -0,0 +1,24 @@
+---
+title: Community Forum
+description: How to navigate the StakeWise Forum — categories, tags, and how discussions turn into governance proposals.
+---
+
+# Community Forum
+
+The [StakeWise Forum ↗](https://forum.stakewise.io/) is the home of StakeWise DAO governance. It's where ideas are first proposed, refined through community discussion, and eventually written up as formal **StakeWise Improvement Proposals (SWIPs)** before being put to a Snapshot vote.
+
+If you want to influence the direction of the protocol — whether by suggesting a change, giving feedback on a proposal, or simply staying informed — the forum is the place to start. Anyone can register and post.
+
+## Categories
+
+The forum is organized into five main categories:
+
+- **Proposals** — formal SWIPs submitted for community review. Each post here represents a concrete proposal moving through the [voting process](./voting-process).
+- **Ideas** — early-stage discussion of changes that could eventually become proposals.
+- **Ecosystem** — community initiatives, grants, integrations, and partnerships that grow the protocol's reach.
+- **Node Operators** — discussion of node operators, validator allocations, and operator-specific topics.
+- **Uncategorized** — general discussion that doesn't fit the other categories.
+
+:::custom-stakewise[Join the Conversation]
+Browse current discussions and post your own ideas on the [StakeWise Forum ↗](https://forum.stakewise.io/).
+:::

docs/docs/governance/intro.mdx

@@ -1,30 +1,14 @@
 ---
 title: Governance
-description: Understand StakeWise governance — how SWISE token holders vote on fees, oracle management, upgrades, and other protocol decisions.
+description: How SWISE token holders vote on protocol parameters and upgrades through the StakeWise DAO.
 ---
 
 # Governance
 
-StakeWise is governed by its community through the **SWISE** token. The governance system empowers token holders to shape the protocol's future by voting on key parameters and proposals.
+StakeWise is governed by its community through the **SWISE** token. Holders — collectively known as the [StakeWise DAO](./stakewise-dao) — vote on key parameters and upgrades that shape the protocol's future.
 
-## How Governance Works
-
-The StakeWise DAO is responsible for making critical decisions about the protocol, including:
-
-- Setting fees and commissions
-- Managing oracles and node operators
-- Approving protocol upgrades and new features
-- Controlling the DAO Treasury
-
-Governance decisions are implemented through **StakeWise Improvement Proposals (SWIPs)**, which are discussed and voted on by SWISE token holders.
+Every decision is implemented through a **StakeWise Improvement Proposal (SWIP)**, discussed on the [community forum](./community-forum) and voted on by SWISE holders through the [DAO voting process](./voting-process).
 
 :::custom-stakewise[Participate in Governance]
-Join the conversation and vote on proposals at [StakeWise Forum ↗](https://forum.stakewise.io/) and [StakeWise Snapshot ↗](https://vote.stakewise.io/#/)
+Join the conversation and vote on proposals on the [StakeWise Forum ↗](https://forum.stakewise.io/) and [StakeWise Snapshot ↗](https://snapshot.box/#/s:stakewise.eth/).
 :::
-
-## Governance Structure
-
-The governance system consists of two main components:
-
-- **[StakeWise DAO →](./stakewise-dao)**: The community-driven governance mechanism powered by the SWISE token
-- **[DAO Treasury →](./dao-treasury)**: A multi-signature wallet managed by a committee that executes approved governance decisions

docs/docs/governance/stakewise-dao.mdx

@@ -1,52 +1,20 @@
 ---
 title: StakeWise DAO
-description: Learn about StakeWise DAO governance, the role of the community, SWISE tokenomics, and how protocol parameters are decided.
+description: Learn about StakeWise DAO governance, the role of the community, and how protocol parameters are decided.
 ---
 
-import Image from '@theme/IdealImage'
-
 # StakeWise DAO
 
-<p style={{fontSize: '1.2em', color: 'rgba(var(--moon-rgb), .5)', marginTop: '-10px', marginBottom: '20px'}}>Learn the basics of StakeWise DAO governance</p>
-
-## Community-first approach
-
-The sole purpose of StakeWise's existence is to make staking as seamless and profitable as possible.
-
-Community feedback and adoption matter a lot for achieving this goal, and therefore StakeWise aims to create a cohesive community of stakers by putting the governance of the protocol in their hands.
+Because community feedback drives protocol adoption, StakeWise places governance directly in the hands of its stakers who [vote](./voting-process) on how the protocol evolves. Voting power in the DAO comes from the [SWISE token](./tokenomics).
 
 ## Role of the DAO
 
-The DAO's job will be to govern the important system parameters like:
-
-- fees paid by stakers,
-- commissions paid to node operators,
-- onboarding and offboarding of oracles and node operators,
-- principles of liquidity mining campaigns,
-- whitelisting of gauge contracts,
-- Insurance Fund payout triggers,
-- approval of contract changes for the introduction of new features, and more.
-
-When choosing these parameters, the community will need to optimize for both its immediate interests as stakers and the long-term success of the protocol through a correct choice of parameters.
-
-## Tokenomics
-
-:::custom-info[$SWISE Token Contract]
-`0x48C3399719B582dD63eB5AADf12A40B4C3f52FA2`
-:::
-
-<Image img={require('/img/tokenomics.png')} alt="Token Allocation & Emission Chart" />
-<p style={{textAlign: 'center', fontSize: '0.9em', color: 'rgba(var(--moon-rgb), .5)', marginTop: '5px'}}>Token allocation and emission</p>
-
-Alignment of interests of the platform and its participants shall happen through an allocation of 51% of the governance token supply to the community and the existence of basic mechanisms that allow gaining voting power by simply staking with StakeWise. Other token holders will be investors and the development team behind StakeWise.
-
-**Total supply:** 1,000,000,000 $SWISE
-
-**Vesting & allocation:**
-
-- **Community:** 510,000,000 $SWISE, 4-year vesting
-- **Investors:** 251,500,000 $SWISE, 6-month cliff + 18-month linear vesting
-- **Team:** 217,000,000 $SWISE, 6-month cliff + 42-month linear vesting
-- **Future fundraise:** 21,500,000 $SWISE, available immediately
+The DAO is responsible for the key parameters that shape how StakeWise operates:
 
-The starting date for the emission is April 1st, 2021.
+- fees paid by stakers
+- commissions paid to node operators
+- onboarding and offboarding of oracles and node operators
+- principles of liquidity mining campaigns
+- whitelisting of gauge contracts
+- payout triggers for the Insurance Fund
+- approval of contract changes that introduce new features

docs/docs/governance/tokenomics.mdx

@@ -0,0 +1,25 @@
+---
+title: Tokenomics
+description: SWISE token allocation, vesting schedules, supply, and contract address.
+---
+
+import Image from '@theme/IdealImage'
+
+# Tokenomics
+
+:::custom-info[SWISE Token Contract (Ethereum mainnet)]
+`0x48C3399719B582dD63eB5AADf12A40B4C3f52FA2`
+:::
+
+<Image img={require('./img/token_allocation_chart.png')} alt="Token Allocation & Emission Chart" />
+
+**Total supply:** 1,000,000,000 SWISE
+
+To align the interests of the protocol and its participants, the largest share of the SWISE supply is reserved for the community, with the remainder split between investors and the StakeWise team.
+
+- **Community:** 510,000,000 SWISE, 4-year vesting
+- **Investors:** 251,500,000 SWISE, 6-month cliff + 18-month linear vesting
+- **Team:** 217,000,000 SWISE, 6-month cliff + 42-month linear vesting
+- **Future fundraise:** 21,500,000 SWISE, no vesting
+
+Token emissions began on April 1, 2021.

docs/docs/governance/treasury.mdx

@@ -0,0 +1,45 @@
+---
+title: Treasury
+description: The StakeWise DAO Treasury — assets controlled by SWISE holders and deployed through governance votes.
+---
+
+# Treasury
+
+The StakeWise DAO Treasury is a transparent, on-chain pool of assets controlled directly by SWISE token holders. Secured by smart contracts, it holds the protocol's capital — primarily **osETH** and **SWISE** — and exists to ensure the protocol's longevity and self-sustainability.
+
+:::custom-info[Treasury Addresses]
+- **Ethereum:** [0x144a98cb1CdBb23610501fE6108858D9B7D24934 ↗](https://etherscan.io/address/0x144a98cb1CdBb23610501fE6108858D9B7D24934)
+- **Gnosis:** [0x8737f638E9af54e89ed9E1234dbC68B115CD169e ↗](https://gnosisscan.io/address/0x8737f638E9af54e89ed9E1234dbC68B115CD169e)
+:::
+
+## How Spending Is Decided
+
+The Treasury's operational framework relies on smart contracts and social consensus: no single individual can unilaterally withdraw assets, and every spend follows the same path. Each expenditure is proposed and discussed on the [community forum](./community-forum), then approved by SWISE holders through a [Snapshot vote](./voting-process). Every outflow leaves a verifiable record of how the DAO has chosen to allocate its capital.
+
+In practice, those decisions have taken many forms:
+
+- [SWIP-38 ↗](https://forum.stakewise.io/t/swip-38-deploy-400-oseth-from-the-stakewise-dao-treasury-into-fluid-for-protocol-owned-liquidity/2008) — transferred 400 osETH from the Treasury to the Liquidity Committee to seed protocol-owned liquidity for osETH on [Fluid ↗](https://fluid.io/), so the DAO acts as its own liquidity provider instead of renting liquidity through token incentives.
+- [SWIP-30 ↗](https://forum.stakewise.io/t/swip-30-gradually-replace-swise-liquidity-incentives-with-oseth-from-treasury/1794) — began gradually replacing SWISE token emissions to liquidity providers with osETH paid out of protocol revenue, reducing dilution while keeping incentives in place.
+- [SWIP-31 ↗](https://forum.stakewise.io/t/swip-31-issue-development-grant-for-stakewise-labs/1881) — issued a 12-month grant of 500 osETH and 500 osGNO to StakeWise Labs in 2025 to cover engineering, business development, and operational costs, supplementing the team's node-operating revenue.
+
+## Multisig
+
+The Treasury is a [Gnosis Safe ↗](https://safe.global/) multisig with 7 members. It uses the [SafeSnap module ↗](https://docs.snapshot.box/v1-interface/plugins/safesnap-reality) — which lets approved Snapshot votes trigger Safe transactions — to execute decisions on-chain.
+
+Because any account can submit a transaction to the Safe via SafeSnap, the committee's role is to monitor proposed transactions and reject any that fall outside what the DAO has approved. Rejecting a transaction requires **4 of 7 committee members** to co-sign.
+
+### Current Committee Members
+
+- [Ali Nuraldin ↗](https://x.com/Ali_run) (0x7E36F1fF26cffD6906c11Cd7Eca5f6E993Ba6CE3)
+- [Andreas Dittrich ↗](https://www.linkedin.com/in/andreas-dittrich-eu/?originalSubdomain=de) (0xc0c9707B552C6970f66Ab91D563Bf9b6048E9da6)
+- [Auryn Macmillan ↗](https://x.com/auryn_macmillan) (0x9Aa6Db877742aD8D8c7fE209F561fbd2bE19D5F4)
+- [Dmitri Tsumak ↗](https://x.com/tsudmi) (0x61B01a33Aea3e827B3941Ab097778bd3FA48a332)
+- [Gleb Dudka ↗](https://x.com/gleb0x) (0xC46e791d4fB1207fAB8Cb0e44889127138539c69)
+- [Mikko Ohtamaa ↗](https://x.com/moo9000) (0x9cC9c3de8e710781983a65b90B7efEaaD2D3D7D8)
+- [Otto de Voogd ↗](https://x.com/ottodv) (0x1C86117156Ba31b5d62f02eB56bE9aC5a06610d3)
+
+### Former Committee Members
+
+- [Anthony Sassano ↗](https://x.com/sassal0x) (0x648aA14e4424e0825A5cE739C8C68610e143FB79)
+- [Jascha Samadi ↗](https://x.com/jaschasamadi) (0x152E9Af50257Fc12a84Bb47241cc0bd01ECD2ac1)
+- [Miko Matsumura ↗](https://x.com/mikojava) (0xA2E49855d672C3258A8442FA15F9Bc28f5A55980)

docs/docs/governance/voting-process.mdx

@@ -0,0 +1,82 @@
+---
+title: Voting Process
+description: How StakeWise DAO governance works — from idea to Snapshot vote, on-chain execution, bonds, and the escalation game.
+---
+
+import Image from '@theme/IdealImage'
+
+# Voting Process
+
+The StakeWise DAO is governed entirely by its community. Anyone can propose changes to the protocol, and SWISE holders decide whether those changes are accepted. The sections below describe how an idea becomes a governance vote.
+
+## Governance Process
+
+<Image img={require('./img/from_idea_to_execution.png')} alt="From Idea to Execution Chart" />
+
+Every proposal moves through three phases:
+
+### Phase 1 — Ideation
+
+Anyone can start a proposal by posting an idea in the **Ideas** category with the `phase-1` tag. The goal of this phase is to refine the idea through community input, stakeholder feedback, and discussion. There is no formal threshold to move forward — only the need for visible community support.
+
+### Phase 2 — Specification
+
+Once an idea has been refined, the proposer writes it up as a formal **StakeWise Improvement Proposal (SWIP)** using the template below and posts it in the **Proposals** category with the `phase-2` tag. An informal forum poll then measures DAO sentiment over **5 days**. To advance to Phase 3, the poll must close with more votes in favour of the change than against; otherwise the proposal is dismissed.
+
+:::custom-notes[SWIP Template]
+Every formal proposal posted in the **Proposals** category follows this structure:
+
+- **Executive summary** — a short, plain-language overview of what the proposal does.
+- **Motivation** — the problem the proposal solves and why it matters.
+- **Specification** — the precise details of the proposed change.
+- **Considerations** — risks, trade-offs, and alternative approaches.
+- **Vote & discussion** — the question put to the DAO and the space for community input.
+
+Following this structure makes proposals easier to evaluate and helps them advance through the governance phases.
+:::
+
+### Phase 3 — Snapshot
+
+A **Snapshot vote** opens for **7 days**, sourcing the decision from SWISE holders. The SWIP is updated with a link to the vote and the `phase-3` tag to signal that DAO action is required. The proposal passes if YES votes outnumber NO votes, subject to the quorum rules below.
+
+:::custom-info[Who can submit and what counts]
+- **Submission threshold:** anyone holding at least **1,000,000 SWISE** can submit a proposal and start the vote.
+- **Validity:** for the result to count, **YES votes must exceed NO votes**, and at least **3,000,000 SWISE** must participate in total.
+:::
+
+## On-Chain Execution
+
+Not every proposal has on-chain effects — some are signalling-only. Proposals that *do* include on-chain actions are secured by a bonding mechanism that guarantees the on-chain action matches the actual Snapshot result.
+
+Execution moves through four steps:
+
+### Step 1 — Bond Submission
+
+After the Snapshot vote ends, anyone can post a **1,000,000 SWISE bond** asserting the vote's outcome (for example, *"the vote ended YES"*). This submission opens the escalation game.
+
+### Step 2 — The Escalation Game
+
+<Image img={require('./img/escalation_game.png')} alt="Escalation Game Chart" />
+
+A **24-hour countdown** begins. During that window, anyone who disagrees with the submitted answer can challenge it by posting the opposite answer — but they must put up **double the previous bond**. Every challenge resets the 24-hour timer and doubles the required bond again:
+
+`1M SWISE → 2M → 4M → 8M → …`
+
+There is no formal cap; the progression continues until no one challenges within the 24-hour window. When the timer finally runs out, the last-standing answer wins, and **the winning side claims the losing side's bonds**.
+
+:::custom-info[Why This Works]
+The escalation game is an economic mechanism for settling disputes about a vote's result. Anyone can challenge an incorrect answer, but each challenge is twice as expensive as the previous one.
+
+Because the community that voted for the true outcome has a much larger economic power than any single attacker trying to flip the result, defending the true answer is always cheaper than overturning it.
+:::
+
+### Step 3 — Multisig Cooldown
+
+Once the escalation game settles, a **24-hour cooldown period** begins. During this window, the [DAO multisig](./treasury#multisig) can reject the result.
+
+### Step 4 — Execution
+
+After the cooldown ends:
+
+- **Anyone** can execute the vote on-chain (execution costs gas).
+- **Winning bonders** can withdraw their bonds along with the bonds claimed from the losing side.

redirects.ts

@@ -35,4 +35,8 @@ export default [
     from: '/operator/additional-actions/add-extra-rewards',
     to: '/operator/manage-vault/add-extra-rewards',
   },
+  {
+    from: '/docs/governance/dao-treasury',
+    to: '/docs/governance/treasury',
+  },
 ]

sidebars.ts

@@ -65,7 +65,10 @@ const sidebars: SidebarsConfig = {
       },
       items: [
         'docs/governance/stakewise-dao',
-        'docs/governance/dao-treasury',
+        'docs/governance/tokenomics',
+        'docs/governance/community-forum',
+        'docs/governance/voting-process',
+        'docs/governance/treasury',
       ],
     },
     'docs/glossary',

src/theme/Admonition/Types.js

@@ -29,7 +29,7 @@ const AdmonitionTypes = {
   'custom-notes': (props) => <CustomAdmonition iconSrc="/icons/stakewise/notes.png" {...props} />,
   'custom-tips': (props) => <CustomAdmonition iconSrc="/icons/stakewise/tips.png" {...props} />,
   'custom-warning': (props) => <CustomAdmonition iconSrc="/icons/stakewise/warning.png" {...props} />,
-  'custom-stakewise': (props) => <CustomAdmonition iconSrc="/icons/stakewise/logo.png" {...props} />,
+  'custom-stakewise': (props) => <CustomAdmonition iconSrc="/icons/stakewise/sw_logo.gif" {...props} />,
 };
 
 export default AdmonitionTypes;