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
Should we just have a proxy variant Pallet(PalletIndex) and Call(PalletIndex, CallIndex) and automatically be 80% future proof with new pallets?
And Kian
I have always been a fan of more flexible proxies that allow for specific call indices instead of matching on specific pallets in the runtime, but there has been push-back that for Polkadot we want to be conservative.
* generate large messages
* consider headers sync lag when computing number of rewards in confirmation
* more fixes
* fix logs
* fix warnings
* do not wait until tx that has delivered nonces will be finalized before submitting other tx
* tests for maximal weight/size
* cleanup
* cleanup
* clippy
* compilation
* args for dispatch weight and remark size
* ExplicitOrMaximal
* clippy
Quoting xlc from the issue paritytech/polkadot#6211
And Kian
The text was updated successfully, but these errors were encountered: