-
Notifications
You must be signed in to change notification settings - Fork 14
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
Update to 0.9.42 #382
Update to 0.9.42 #382
Conversation
a057555
to
26d2316
Compare
26d2316
to
31fcc00
Compare
@gianfra-t can you please resolve the conflicts of this PR? We need to prepare it for merging again |
The new fee per second implementation was merged into this branch, which removes the need for a temporary workaround used before. |
@ebma @gianfra-t would this update break the ledger app? |
I don't think so, because the extrinsics are not changing by the update (the transaction version should stay the same). |
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.
Looks good to me but should probably only be merged once pendulum-chain/spacewalk#491 and #410 are merged. The rev
commits for the Spacewalk dependencies should then point to the merge commit of the PR on Spacewalk main.
Co-authored-by: Marcel Ebert <[email protected]>
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.
Looks good 👍🏼
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.
Let's go ahead with this. Thanks for all the testing work!
Oh just one more thing. I noticed that the PR includes the changes of #432 which we rolled back in order not to mess with the XCM configuration until https://github.com/pendulum-chain/tasks/issues/202 is fully ready and implemented. I propose we roll those changes back here as well. I assume this is quite simple and can be done with a simple revert of the specific commit like was done in #431. |
Oh, good that you remembered that @ebma, I completely forgot. Sadly I don't know if it will be that simple, mostly because there were some changes required for the old trader given the new version. So it will probably not look exactly like before. |
@ebma I reverted the merge with fee per second, which re-introduces this workaround for the Let me know what you think. I am testing with chopsticks right now. |
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.
Looks good to me, thanks for reverting the changes 👍
Let's finally get this merged
Note: I will leave this as draft until merged with the fix code for try-runtime.
@pendulum-chain/product: This PR adds changes to the node client code that require a redeployment of the collator nodes to take effect.
Closes tasks/#158
Closes #222.
Closes https://github.com/pendulum-chain/tasks/issues/64.
Updates to dependencies
Spacewalk -> branch upgrade-v0.9.42
Substrate-stellar-sdk -> branch polkadot-v0.9.42
Dia-Oracle (oracle-pallet) -> branch polkadot-v0.9.42
Pendulum/Bifrost -> branch upgrade-v0.9.42.
Updates of the Storage Version
Following what was defined in this issue and in this notion page, we define in this PR the manual set of the storage version for all pallets which are behind the current version.
The code is added to the
Executive
type and will be used only for the purpose of this update.For pallets
vesting
andtransaction-payment
we need to make custom migrations that make use of private definitions of theStorageVersion
type and theReleases
enum. This temporary substrate fork contains these migration types. here and here.Changes in runtime
General
New
TokenError
variants were added toChainExtensionTokenError
enum andFrom<>
functions.Pallet Balances
In all configs we must add the following new types (
FreezeIdentifier
,MaxFreezes
,MaxHolds
andHoldIdentifier
). Since we currently do not use any of these functionalities, we can pass the default configuration. We need to adjust if we require more than one freeze or hold.Also in
pallet_balances
theDustRemoval
trait bound has changed. Before it was required:type DustRemoval: OnUnbalanced<NegativeImbalance<Self, I>>;
Which pallet
Treasury
implemented.Passing type
Treasure
is not supported anymore since the bound is now:type DustRemoval: OnUnbalanced<CreditOf<Self, I>>;
which is not implemented by theTreasury
pallet, so we must define a new implementation. This is adopted from ComposableFi yet the functionality is the same which will transfer to the Treasury's account the unbalanced currency.Pallet Contracts
DeletionWeightLimit
,DeletionQueueDepth
since are not required anymore.DefaultDepositLimit
, which is the fallback value to limit the storage deposit if it's not being set by the caller. Defined this value as in substrate contracts nodePallet Collective
MaxProposalWeight
. We use 50 percent of the max block weight as it is defined in Frontier.Pallet XCM
AdminOrigin
type, which is set to root. This is only used for privileged function about xcm version management.Farming Pallet
Because we update our bifrost fork to
0.9.42
, the farming pallet now allows for a "boost reward" functionality, which can also be managed in conjunction with the palletve-minting
. This is refelected into 4 new config types forfarming
pallet:FarmingBoost
,VeMinting
,BlockNumberToBalance
,WhitelistMaximumLimit
. We do not useVeMinting
in this case, as in bifrost kusamaChanges in Node
Partly adopted changes from equilibrium's node service. Changes are minor and mostly involve modifications in methods calls.