-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should Ics20Context implement Module? #182
Comments
Hi @kevinji, the reason |
@kevinji can we close this, or do you still see an issue with the current design? |
Hey sorry for the late response. I agree that implementing The use case I was thinking of is that I could separate out the ICS-20 logic into a separate module (possibly separate smart contract). Would this essentially require some way to generate an Or, phrased a different way, is there some way to get |
@hu55a1n1 This looks good, I'll try it out once I get some time to revisit this. |
Summary
Should Ics20Context implement Module so ChannelKeeper and ChannelReader don't need to be implemented?
Problem Definition
The current ICS20 logic looks a bit like a standalone IBC module, which means it doesn't interop nicely with the Module system proposed by ICS26. It also leads to a lot of extra boilerplate code due to having to implement ChannelKeeper and ChannelReader that could be delegated to a routing module that implements ICS26.
Proposal
Have Ics20Context implement Module, and update the interface of Ics20Context so only the BankKeeper and Ics20Reader functions need to be implemented.
Acceptance Criteria
The changes proposed are made to Ics20Context and the other related traits.
For Admin Use
The text was updated successfully, but these errors were encountered: