Currently, when an ipOrg updates its hooks, i.e. adding a new hook. The applications that integrate with the ipOrg will fail and require code changes because it doesn't know what data to pass into the new hook.
We need a way to allow application developers to migrate smoothly when this happens. Maybe a time lock mechanism to allow the application developers to know the attempt of updating hooks ahead of time. Or any other better approaches.
I think it worths researching some other projects like Uniswap v4 to see how they handle this.
We could add some hook metadata to identify them. There are some cases where it only makes sense to have a payment hooks for a module/action, the module needs to know what the hook does.
Currently, when an ipOrg updates its hooks, i.e. adding a new hook. The applications that integrate with the ipOrg will fail and require code changes because it doesn't know what data to pass into the new hook. We need a way to allow application developers to migrate smoothly when this happens. Maybe a time lock mechanism to allow the application developers to know the attempt of updating hooks ahead of time. Or any other better approaches. I think it worths researching some other projects like Uniswap v4 to see how they handle this.