You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
noticed you guys are using extensively hooks in the enforcers.
It is very similar generic problem in the industry, e.g. Ironblocks and other companies implementing firewalls do same.
I’ve created https://ercs.ethereum.org/ERCS/erc-7746 to address this as generic industry problem so that we can have interoperable middleware hooks standard across industry.
I think you guys should contribute your ideas to it (and use it as a standard)!
The text was updated successfully, but these errors were encountered:
Requires we pack all our gator-specific params into the bytes memory configuration, but otherwise we surely could. Given that it's still only compatible with usage that explicitly involves encoding for it, how big do we think the win of reusing this interface would be?
I tend to think using agnostic input types like that are mostly useful when someone else is composing them (like in ERC-7710 redeemDelegation(bytes authority, Action action), where the authority is flexible but the caller is not expected to compose it. Since in this case the caller will basically always be packing it, my first thought is that the usage doesn't end up being very easily intercompatible, it just looks the same on the surface.
noticed you guys are using extensively hooks in the enforcers.
It is very similar generic problem in the industry, e.g. Ironblocks and other companies implementing firewalls do same.
I’ve created https://ercs.ethereum.org/ERCS/erc-7746 to address this as generic industry problem so that we can have interoperable middleware hooks standard across industry.
I think you guys should contribute your ideas to it (and use it as a standard)!
The text was updated successfully, but these errors were encountered: