Current status
| Area | Status |
|---|---|
| Wallet connection | Reown and WalletConnect integration |
| Token and public financial operations | Awaiting launch and activation |
| Initial secondary market | USDG then SPY selected; budgets and full release approval pending |
| Stock-token pool order | SPY → NVDA → AAPL; selection approved |
| Independent security review | Not completed |
The configured sequence
- First, the native Degen launch creates ETH / FLOW, the venue that produces eligible creator fees.
- Next, Flowbank activation uses the separately funded seed budget to seed FLOW / USDG and then FLOW / SPY as V3 pools, after route and budget verification.
- Afterwards, two-thirds of received creator fees deepen the selected pools according to the current stage weights. One-third goes to the team.
- NVDA follows SPY; AAPL follows NVDA. The final target is USDG 50%, SPY 25%, NVDA 15% and AAPL 10% of new liquidity capital. Phase changes require funding, verified routes, external demand and governance configuration.
When liquidity is added
The current worker policy checks for work every five minutes. It defers an allocation below its minimum capital threshold, currently 0.001 ETH unless configured otherwise, and respects per-cycle and daily spending limits.
The worker acquires both sides of liquidity, checks the pool price and adds to the existing protocol position. A price deviation can delay an addition while the fee-harvesting and reward process continues. Creator fees, not gross volume alone, are the spendable budget.
Before token launch
- Approve the reward policy, eligible markets and holder exclusions.
- Configure governance, team and creator/operator addresses and spending limits.
- Fund seed liquidity and transaction gas, and configure a production archive RPC.
- Complete independent review, production deployment, monitoring and a rehearsal of the intended configuration.
Fast token binding
The prepared commands verify the new token and creator-fee registration, bind the address once, seed the selected market and publish an active deployment manifest. The website detects activation without a rebuild.
The exact activation command took about 43 seconds in a local-fork rehearsal. That is a measured test result, not a production timing guarantee. Wallet connection does not bypass any activation gate.