Current status
| Area | Status |
|---|---|
| Multi-page website and demo | Implemented |
| Token launch | Not executed |
| Protocol and community LP contracts | Not deployed |
| Staking / holder distributor | Not deployed |
| Live account and transaction integration | Not connected |
| Security audit | Not performed |
| Native hook and selected DEX | Bytecode and references verified; launch UI path needs rehearsal |
Verify the intended launchpad
The integration targets the native Degen hook verified on Robinhood Chain. The local source projects supplied by the project owner were used to verify the fee claim path and adapt the existing splitter.
The deployed legacy native launcher and selected V3 contracts have been exercised on a local mainnet fork. That test does not verify a newer launchpad UI or ABI. Before launch, confirm the actual launch receipt and creator identity against the prepared configuration.
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.
Reservoir 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.
Primary sources
External documentation was checked on 8 September 2026. Availability and contract details must be verified again before launch.
Degen.zone availability ledgerShroom mechanism and dashboard