-
Notifications
You must be signed in to change notification settings - Fork 710
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
Added fallback_max_weight to Transact for sending messages to V4 chains #6643
base: master
Are you sure you want to change the base?
Conversation
/cmd fmt |
Command "fmt" has started 🚀 See logs here |
Command "fmt" has finished ✅ See logs here |
/cmd prdoc --audience runtime_dev --bump major |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comments. Please also add an explicit Transact test from V5 chain -> V4 chain.
/cmd fmt |
Command "fmt" has started 🚀 See logs here |
Command "fmt" has finished ✅ See logs here |
Co-authored-by: Adrian Catangiu <[email protected]>
Co-authored-by: Adrian Catangiu <[email protected]>
Co-authored-by: Adrian Catangiu <[email protected]>
/cmd fmt |
Command "fmt" has started 🚀 See logs here |
Command "fmt" has finished ✅ See logs here |
All GitHub workflows were cancelled due to failure one of the required jobs. |
Closes: #6585
Removing the
require_weight_at_most
parameter in V5 Transact had only one problem. Converting a message from V5 to V4 to send to chains that didn't upgrade yet. The conversion would not know what weight to give to the Transact, since V4 and below require it.To fix this, I added back the weight in the form of an
Option<Weight>
calledfallback_max_weight
. This can be set toNone
if you don't intend to deal with a chain that hasn't upgraded yet. If you set it toSome(_)
, the behaviour is the same. The plan is to totally remove this in V6 since there will be a good conversion path from V6 to V5.