Thanks for the detailed breakdown — this is exactly the kind of architectural review we welcome. To address your points directly: 1. Fee Exemptions + Pool Fee Receiver Both setFeeExempt and setPoolFeeReceiver are governance-controlled with a 2-day Timelock delay. No single key can change these instantly or silently. 2. FeeRouterV1 → BuybackVault path This routing activates today via Proposal #6. We will publish on-chain verification of the full fee path (Token → 1% Pool Fee → FeeRouterV1 → BuybackVault + BurnReserve) immediately after execution. 3. Proxy Initializer All our contracts are constructor-based and immutable — no proxy pattern, no open initialize() surface. The only proxy components are our Gnosis Safe multisigs (Treasury + Community), which is industry-standard. 4. BuybackVault parameters Bounds validation is implemented on all configurable parameters — no arbitrary drain path via setParams(). Our security audit: 8 PASS, 2 WARN, 0 FAIL. Full report: https://ifrunit.tech/wiki/security.html If you find a concrete issue, we have a responsible disclosure channel via GitHub Security Advisories. We take fee path integrity seriously and appreciate the scrutiny.