-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add new privilege raw_events
#139
Comments
I like the wasmd one. |
This would be a nice addition to a future staking contract. And really make privileged contracts first class citizens. |
I don't see this as urgent. We don't do proper faking of all the staking contracts anyway (use different proto types for messages, etc). We can look at this in the future, for now block explorers seem to work without this |
This was a very old idea to be able to fully migrate go modules to contracts. Do you think this is still relevant @daniellarita ? |
@ethanfrey what do you think, is this ticket still relevant? |
I think the idea is good and it would give better compatibility, but event compatibility didn't seem to be a major issue with tooling. I would leave this in the "nice ideas" pile, where we could do if there is time for refactoring and polish, but not urgent at all |
Background:
With bonding/unboding we have events emitted by the contract and the PoE module's msg_server. There is an amount of duplicate data with this approach. The contract's events are prefixed with
wasm-
so that they can not replace the ones defined in staking module.Requires: CosmWasm/wasmd#614
Follow up tasks would be:
The text was updated successfully, but these errors were encountered: