wishlist: support BURN_6909 uni v4 action #675
Description
V4 does not support BURN_6909, BURN_6909 actions, as they as not supported neither by the v4Router (hence universal router), nor by the position manager (as per this comment in the univ4 periphery repo).
This means the protocol, at the moment, does not support ERC6909 balances.
However, a hook with access to deltas could mint an ERC6909 balance to the smart pool, and the pool would not be able to burn it. Also, the position would not be included in nav calculations. Therefore, it would be desirable for the pool to be allowed to at least burn those balances. At the current stage it is appropriate to allow this scenario, until hook management becomes more mature, as a rogue hook could mint ERC6909 with the goal of performing a phishing attack on the pool operator's tokens.
Technically, anyone can mint an ERC6909 to the pool (even a hook), therefore we should allow burning, but should be careful about including them in nav calculations, as number of pool-owned ERC6909 positions can be inflated arbitrarily by anyone.