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
It came up during discussions that there’s demand for pools that have whitelisted addresses that can interact with them. While there are hacky ways we can add this directly in chain code, @p0mvn suggested that we could instead trigger a hook at the beginning of each message that calls a CW contract such that if a target contract is set for the pool, we execute sudo message like with CW pools.
This would in theory allow for arbitrary logic to be run prior to pool message execution, so the use cases would be far more expansive than the simple validation check above.
Suggested Design
See above description
Acceptance Criteria
Feature is implemented and well tested
The text was updated successfully, but these errors were encountered:
Background
It came up during discussions that there’s demand for pools that have whitelisted addresses that can interact with them. While there are hacky ways we can add this directly in chain code, @p0mvn suggested that we could instead trigger a hook at the beginning of each message that calls a CW contract such that if a target contract is set for the pool, we execute sudo message like with CW pools.
This would in theory allow for arbitrary logic to be run prior to pool message execution, so the use cases would be far more expansive than the simple validation check above.
Suggested Design
Acceptance Criteria
The text was updated successfully, but these errors were encountered: