Launch readiness & open decisions

Current status

Verify the intended launchpad

The original request named degenland.zone. That domain could not be reached during research. The available fee and graduation findings refer to degen.zone; equivalence is unconfirmed.

Degen.zone’s public material is internally inconsistent about mainnet availability. A fee schedule or an example mainnet chain ID is not enough to prove the launch path is operational. Verify deployed factory, hook and graduator contracts, plus a complete successful transaction trace.

Decisions that still need owners

• Token supply, allocation, vesting and final launch venue.
• The intended fee coverage: eligible launch trades or all trades through a custom architecture.
• User-owned LP positions versus a pooled vault with separately owned shares.
• Pool selection, ranges, fee tiers and who may rebalance positions.
• Reward payout asset, holder/staker split and operating-cost policy.
• Holder eligibility, epoch timing, staking locks, cooldowns and claim expiry.
• Custody, governance, emergency withdrawal and incident-response controls.
• Jurisdiction and asset eligibility for the intended user audience.

The path to live transactions

First finalize and verify the architecture. Then test the complete launch, fee collection, liquidity and reward path with non-production assets or a fork. Confirm conservation, entitlements and failure handling before selecting production deployments.

The public release should publish verified addresses, code and audits; activate wallet quotes and transaction handling; and reconcile the indexer against actual chain state. Example balances must never silently become live balances.

What was learned from Shroom

Shroom’s site describes SHROOM pairs, fee collection and compounding. Its public dashboard payload labeled all 48 listed owned pools as V4 during the original research. That does not independently verify their contracts, exact ranges or automation.

HoodPools extends the concept with separate user LP deposits and holder/staker distributions. Those features are proposals for this protocol, not claims that Shroom operates the same design.