Treasury - FUNDOOR

Current Holdings

Treasury Seeding - Phase 1

FUNDOOR has just launched. Treasury holdings will be acquired after the 3-month creator cliff unlocks.

Creator allocation (20% treasury fund) is locked by Fundry's smart contract. Once unlocked, the community will vote on the first holdings through governance.

In the meantime, 1.2% creator fee from all trades is accumulating for staking rewards.

Treasury Timeline

Now - Month 3

Accumulating

Trading fees (1.2%) accumulate and flow to staking rewards. Creator tokens are locked.

Month 3

Cliff Unlocks

Creator allocation unlocks. Treasury fund (20%) becomes available to acquire Fundry tokens.

Month 3-4

First Holdings

Community votes on first 5-10 treasury holdings. Governance system activates.

Month 5+

Full Index

Expand to 10-50 holdings. Regular rebalancing. Full community governance.

Treasury Rules

Max Single Holding

15%

No single token can exceed 15% of treasury to prevent concentration risk.

Minimum Holdings

10

Treasury must hold at least 10 different tokens for baseline diversification.

Maximum Holdings

50

Cap of 50 tokens to maintain manageable portfolio and meaningful positions.

Rebalancing

Monthly

Regular rebalancing or triggered by governance vote when needed.

Revenue & Staking Rewards

Protocol revenue from the 1.2% creator fee is distributed to stakers through weekly reward periods.

Revenue Source

FUNDOOR receives 1.2% of all $DOOR trading volume as creator revenue. This is automatically sent by Fundry's smart contract whenever someone buys or sells $DOOR.

Weekly Reward Periods

Each week, accumulated revenue is deposited into a new reward period. Stakers earn their share based on their TWAB (Time-Weighted Average Balance) proportion during that period.

TWAB Distribution

Your share = (Your TWAB / Total TWAB) x Reward Pool. Staking earlier in a period means more time to accumulate TWAB and a larger reward share.

Claim Process

At the end of each period, a Merkle tree is generated. You can then claim your rewards using a Merkle proof - fully on-chain and trustless.