As it was discussed in the Uniswap HackerHouse event, it will be great if all multicall & permit scripts become MIT licensed. It will also encourage new directions for hook creations.
A. Multicall: One benefit is that the community will be enabled to build hooks that incorporate multicall in them with any license. This is particularly useful for hooks that interact directly with v4 core, as opposed to the periphery, as they may need to trigger a sequence of calls to the core. For example, an aggregator contract which is also a hook.
B. Permit2: Similar to the previous argument, Permit2Forwarder can be readily used by any contract that interacts directly with v4 core. Making Permit2Forwarder MIT encourages permit2 adoption.
linear[bot]
commented
4 days ago
As it was discussed in the Uniswap HackerHouse event, it will be great if all multicall & permit scripts become MIT licensed. It will also encourage new directions for hook creations.
A. Multicall: One benefit is that the community will be enabled to build hooks that incorporate multicall in them with any license. This is particularly useful for hooks that interact directly with v4 core, as opposed to the periphery, as they may need to trigger a sequence of calls to the core. For example, an aggregator contract which is also a hook.
B. Permit2: Similar to the previous argument, Permit2Forwarder can be readily used by any contract that interacts directly with v4 core. Making Permit2Forwarder MIT encourages permit2 adoption.
C. ERC721Permit: Similar to the previous argument, it encourages new directions for hook creations, when hooks issue NFTs.
@hensha256 @snreynolds @saucepoint