The protocol modules
| Module | Responsibility |
|---|---|
| Configuration | One-time token binding, governance and activation |
| Fee router | Two-thirds liquidity / one-third team split |
| Liquidity vault | Protocol NFTs, typed swaps, budgets and separate fee inventory |
| Holder distributor | Immutable funded epochs and replay-protected claims |
| Staking contract | FLOW principal and checkpointed USDG streams |
| Combined worker | Creator claims, allocation, harvesting, funding and snapshots |
User ownership
Reown connects the wallet. The dapp reads verified contracts and uses the connected provider to request user-approved transactions. A user’s V3 position NFT is created with the wallet as its owner.
The website does not receive the protocol signer’s private key. Private worker journals and public reward-proof data use separate server storage.
Operator controls and their limits
Protocol spending is restricted to configured assets, typed operations, fixed DEX destinations and daily token budgets. Quotes use deadlines and minimum outputs; acquisition checks bound route impact and pool-price deviation.
These checks are not an independent oracle or comprehensive protection against adverse trading. The operator is trusted within its permitted limits. Governance can change operators, asset policy and pause new operations; there is no timelock in the prepared implementation.
Recovery and verification
The worker records signed transaction bytes before sending them. Recovery reconciles the same transaction hash, and a reverted transaction blocks subsequent spending until investigated.
The prepared flow has passed local-fork tests covering fee claims, secondary pools, funded rewards, user-owned LP exits and activation commands. These tests are not an independent security audit or proof of production readiness.