POOLZ PAD V1 · public transparency preview
See how each fee
is allocated.
A clear public record showing how trading fees are divided among liquidity providers, buybacks, ecosystem and team operations, and trader and growth incentives.
Illustrative amounts · proposed rules · no live balances
Investor interface · pre-launch preview
Buyback & Burn
Tracker.
Live on-chain records activate after deployment. Every production cycle will link to its transaction and burn proof.
Illustrative data only
Production rows will expose the vault funding transaction, swap outcome, burn transaction, block number and explorer verification.
01 The buyback share is sent to the approved buyback wallet.
02 A buyback is executed periodically within predefined limits.
03 Acquired POOLZ is burned and the result is published with on-chain proof.
One protocol fee · three outcomes
The split stays
visible.
Of every 1% protocol fee, the proposed model assigns 40% to buyback and burn, 40% to ecosystem and team operations, and 20% to trader and growth incentives. Any small rounding difference will follow the final written rule.
Buyback + burn
0.4000illustrative native unitsFunds are assigned to the approved buyback wallet. A separate controlled operation buys POOLZ and burns the purchased tokens.
Ecosystem + team operations
0.4000illustrative native unitsFunds go only to the approved POOLZ operations wallet recorded in the final configuration.
Trader + growth incentives
0.2000illustrative native unitsFunds may be converted within approved limits and used for reviewed trader rewards and growth incentives.
Evidence trail
From event
to outcome.
A production version should expose the same ordered evidence without asking a community member to interpret raw contract storage.
Fee recorded
Confirmed swap records assign the protocol fee across all three destinations.
Fixed routes only
Any permitted trigger can move available value, but cannot choose or redirect its destination.
Execution reconciled
Buyback output, burn amount or reward conversion is checked against the funded operation.
Backed before active
A reward allocation remains inactive until the complete published amount is funded.
Final record
Versioned totals, dataset evidence and outcomes can be reproduced from the same finalized history.
Public proof boundary
Clear for everyone.
Verifiable by anyone.
Each published result includes the calculation version, source period, configuration and recorded outcome. Public summaries are provided for transparency and can be independently verified against the relevant contracts and source data.
- Source status
- Finalized example
- Configuration
- Version demo-01
- Bucket total
- 1.0000 units
- Outcome status
- Reconciled
Synthetic record · no explorer link or live address
Hard safeguards
Simple rules.
No quiet shortcuts.
The design keeps fee collection separate from later operations and makes invalid accounting states explicit.
No hidden destination
A caller cannot provide a recipient when triggering a protocol-bucket sweep.
No trading-path buyback
The fee hook accounts for fees; it does not swap, burn or distribute rewards inside a user trade.
Finalized history only
Provisional blocks can be repaired, but they cannot settle public totals or reward outcomes.
Mismatch stays visible
Overspending, underfunding or excess claims fail reconciliation instead of being concealed.
Example records now.
On-chain proof after launch.
This interface shows how investors could review fee allocation, buybacks and burns after launch. No real fee balance, transaction or burn is represented by these illustrative pre-launch figures.
- 01Confirm the 40/40/20 protocol allocation and how any rounding difference is assigned in the final written configuration.
- 02Approve the production wallets, fixed destinations and the process for changing them.
- 03Approve the reward currency, conversion limits, distribution schedule and claim window.
- 04Complete testnet reconciliation, independent audit and written production authorization.
