// Section 8.8 · Token
Contract Ownership: Retained, by Design
Contract ownership. Retained, by design.
// 8.8 · maintenance key · narrow scope · renouncement planned
Why retention is necessary
// five operational needs · all updatable surfaces
- 1
DEX PAIR ALLOWLIST
Every new DEX pair (V2 alternates, V3 once FoT-supporting, Sushi, Curve-style, CEX router hot-wallets) must be registerable for the tax classifier to handle it. A static allowlist breaks the moment a new liquidity venue lists $PRLX.
- 2
NODEREGISTRYLOCKER EXEMPTION
NodeRegistryLocker must be exempt from the tax. Otherwise operators pay 4% to lock stake and 4% to withdraw it, and reward claims are taxed too, making node staking economically infeasible.
- 3
PROTOCOL-INTERNAL FLOWS
The ParalleliX AI deposit address and reward-settlement flows must be exempt for the same reason. Credit deposits and operator payouts cannot also pay 4% tax on every internal flow.
- 4
TAX-WALLET ROTATION
The contract sends tax to a single taxWallet (the 1/2/1 Dev/Ops/Marketing split is allocated off-chain). If that wallet is ever compromised, the tax stream must be redirectable to a clean multisig.
- 5
EXPLOIT PAUSE
In the event of a confirmed exploit, a transfer pause limits the blast radius before the team coordinates a fix.
Owner scope
// narrow admin surface · bytecode-enforced boundaries
- Add and remove DEX pairs and routers in the FoT classification allowlist.
- Add and remove exempt addresses (NodeRegistryLocker, treasury contracts, audited protocol contracts, the ParalleliX AI deposit address).
- Update the single tax-destination wallet. The 1-2-1 Dev/Ops/Marketing split is allocated off-chain after collection.
- Pause transfers during a confirmed exploit. Rate-limited and event-logged.
- Mint new tokens. No `mint` function exists. Supply fixed at 100,000,000.
- Change the tax rate above the audited maximum (5% aggregate). Current rate is 4%, allocated 1/2/1 off-chain.
- Move tokens out of any wallet that is not the owner's own.
- Burn balances belonging to other addresses.
- Insert governance, voting, or proposal logic.
Path to renouncement
// four trigger conditions · single on-chain transaction
Renouncement is planned, not ruled out. The trigger conditions are explicit.
NodeRegistryLocker has been live and stable for at least one full reward epoch.
All major DEX integrations (V2 launch venues, V3 once FoT support ships, relevant CEX flows) are registered and stable.
The ParalleliX AI settlement path is audited and stable.
The protocol has stopped requiring new admin surface area.
When those conditions are met, ownership is renounced in a single on-chain transaction and the event publishes simultaneously to this document, to tokenomics.md, and to the docs.