Ecosystem Revenue Flows
FoxxOne runs three revenue streams: validator staking rewards, Portfolio subscription, and Validator Alerts subscription. This page spells out where each stream goes today (Phase 1 — bootstrapping FOXXEY liquidity) and where it will go once FOXXEY is fully live (Phase 2).
Nothing is being burned yet. Any "burn" language on the site refers to the Phase 2 model. Phase 1 is about pouring as much of the subscription revenue as possible into the FOXXEY LP-seed accumulator so the market launches with real liquidity behind it.
Last updated: 2026-07-11
Phase 1 — Now (Bootstrapping FOXXEY Liquidity)
Every payment router splits its incoming subscription revenue 70 / 30 on-chain, into an operator wallet and an LP-seed wallet. The split is immutable — it lives in the router contract, not in an admin toggle. During Phase 1 the operator has committed to defer the 70% ops share and route it into the same LP-seed accumulator as the immutable 30% slice. In other words: 100% of paid subscription revenue currently accumulates in the FOXXEY LP-seed wallet. No wages, no reimbursements, no draws from subscription revenue during Phase 1.
The validator staking rewards work slightly differently — see the table below. The only cash currently flowing to the operator personally is the 15% slice of validator rewards after the auto-compound restakes the other 70%.
| Stream | Contract split | Where the revenue actually goes today |
|---|---|---|
| Validator staking rewards (Infinite validator) | 70 / 30 via authz auto-compound |
70% auto-restaked to the validator
30% → 15% to the operator + 15% to the LP-seed accumulator |
| Portfolio subscription — on-chain 42 | 70 / 30 via FoxxOnePaymentRouterV1 | 100% to the LP-seed accumulator. The 30% slice is immutable to the LP-seed wallet; the 70% ops slice is voluntarily deferred to the same accumulator during Phase 1. |
| Validator Alerts subscription — on-chain 42 | 70 / 30 via FoxxOnePaymentRouterV1 | 100% to the LP-seed accumulator. Same policy as Portfolio. |
| Validator Alerts subscription — Stripe | Manual | Currently unused. Every paying user has taken the on-chain 42 path. If any Stripe subscription arrived, it would be split off-chain to match the on-chain policy above (100% to LP-seed during Phase 1). |
Phase 2 — Once FOXXEY Is Live
When Don't Panic Finance v4 launches and the FOXXEY market has real liquidity — the LP-seed
accumulator is paired with FOXXEY to seed the initial pool, the LP tokens are burnt
(sent to 0x…dEaD), and the market is self-sustaining. From that point the flows
shift as follows.
| Stream | Contract split | Where the revenue will go |
|---|---|---|
| Validator staking rewards | 70 / 30 via authz auto-compound |
70% auto-restaked to the validator
30% → 15% operator + 10% FOXXEY staker rewards + 5% buyback-and-burn |
| Portfolio subscription — on-chain 42 | 70 / 30 via FoxxOnePaymentRouterV1 |
70% funds infrastructure + operator wages
30% routes through a permissionless on-chain buyback-and-burn sink |
| Validator Alerts subscription — on-chain 42 | 70 / 30 via FoxxOnePaymentRouterV1 | Same as Portfolio — 70% infra/wages, 30% buyback-and-burn sink. |
| Validator Alerts subscription — Stripe | Manual | Would be split off-chain to match the on-chain policy (70% infra/wages, 30% buyback-and-burn). |
Why Phase 1 Looks Like That
Two priorities during the bootstrap window:
- Give the FOXXEY LP the biggest possible seed at launch so the initial pool is deep enough to absorb organic trading rather than getting eaten by the first arbitrage bot to notice a thin market.
- Make it obvious the operator is not extracting subscription revenue while asking users to pay. The 70% ops share is documented as being deferred until the token is live and self-sustaining — no room for a "was he taking wages this whole time?" conversation later.
Under Phase 2, subscription revenue funds normal operations: infrastructure, monitoring, alert development, and operator wages. The bootstrap deferral ends when the FOXXEY market is live.
Contract Addresses
- Portfolio payment router —
0x0d1E66935C10Fe61Fa410b0cDe3f50582b031B3F
Immutable 70 / 30 split. Deployed once, no admin, no upgrade path. - Validator Alerts payment router —
0xc46B052A170ca8d108ee740cbe1d2058EEf0D8aA
Same contract source as the Portfolio router. Also immutable 70 / 30. - Shared operator wallet (receives the 70% slice) —
0x4f4909c2EeAfe953750A7471Ae3D36165aC7c195
Currently forwarding all received subscription revenue to the LP-seed accumulator. - Shared LP-seed accumulator —
0x16c6c90FB351Faf23bf225785e2e08686bDcc2c3
Destination for the immutable 30% router slice + the deferred 70% ops slice + the 15% LP-seed slice from validator rewards.
Everything above is verifiable on the Infinite Drive chain.
When Does Phase 2 Start
Phase 2 begins when the FOXXEY market is live on Don't Panic Finance v4: LP-seed accumulator is paired with FOXXEY, initial pool is seeded, LP tokens are burnt, and organic trading is possible. From that point, the operator wallet stops forwarding to LP-seed and starts covering real operational costs — and the validator-reward 30% slice starts routing to staker rewards + buyback-and-burn instead of LP-seed.
Nothing is being burned during Phase 1. Any burn tx hashes referenced elsewhere on the site describe the Phase 2 model. When Phase 2 begins, this page will be updated with the trigger date and the first burn tx hashes will be linked here.
Related
- Auto-compound Validator Rewards Guide — how the 70 / 30 validator-rewards split is set up (same authz pattern any Cosmos operator can run).
- Portfolio subscription — Pay with 42 panel shows the router address and live 70 / 30 split preview.
- Validator Alerts subscription — same for the alerts router.
- FOXXEY Staking — where the staker-reward slice will land in Phase 2.