Pons doesn’t allow taxes to be changed post-launch.
There is a big group of people claiming that this is the case, but it’s simply wrong.
What I noticed is that some terminals (for whatever reason) route buys and sells through high-tax pools, even though the Pons-initialized @Uniswap V4 pool is not only a) liquid, but also b) a 0% tax pool with a 1% hook fee (as disclosed on all trades).
When a malicious actor tries to vamp said pool, it can show up on terminals as an increased tax. That number then goes up and down depending on misconfigurations within the router and which pool the terminal decides to route through.
I have asked terminals to change this, as it hurts users and causes unnecessary FUD.
Pons has a 1% hooked pool. If you see more than that (unless a deployer set higher taxes at launch), you are being routed through the wrong pools and therefore being charged more.
This does not mean taxes were changed post-launch.
See example below: