Static crawler version. Interactive docs are available at https://docs.memewar.zone/treasury.

Treasury Structure

How MemeWarzone separates reward routing, protocol revenue, Owners Safe policy, and Ops Safe execution.

MemeWarzone treasury design should be boring on purpose.

The system separates reward routing from protocol revenue and operations.

Core principle

TreasuryRouter routes fees first.

Protocol revenue is what remains after League, recruiter, airdrop, and Squad Pool allocations.

fee amount -> TreasuryRouter -> reward buckets + ProtocolRevenueVault
ProtocolRevenueVault -> Owners Safe policy
Owners Safe -> Ops Safe and weekly distribution policy

Routing layer

TreasuryRouter can route to:

| Destination | Purpose |

| --- | --- |

| LeagueTreasury | League prizes |

| RecruiterRewardsVault | Recruiter reward allocations |

| CommunityRewardsVault | Warzone Airdrops and Squad Pool balances |

| ProtocolRevenueVault | Protocol revenue remainder |

This means protocol revenue is not the full fee. It is the routed remainder.

Owners Safe

The Owners Safe is the main treasury and governance wallet.

Direction:

Ops Safe

The Ops Safe is for day-to-day execution.

Target balance: 50 BNB.

Policy direction:

This gives operational flexibility without exposing the full treasury.

Weekly payouts

Weekly treasury movement should follow a fixed policy:

  1. Normalize Ops Safe.
  2. Retain the configured treasury buffer.
  3. Distribute the remaining configured amount to predefined payout wallets.

Read: **[Weekly Distribution](/treasury/weekly-distribution)**.

Developer wallets

Developer EOAs can deploy contracts and prepare transactions.

They should not receive protocol revenue directly.

Why this matters

This structure reduces: