chore: upgrade to polkadot v1.11.0 #889
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 124e289.
|
Crate versions that have been updated:
Runtime version has been increased. |
Co-authored-by: green-jay <75261756+green-jay@users.noreply.github.com>
feat: make ah as dot reserve
mrq1911
reviewed
Oct 2, 2024
integration-tests/src/evm_permit.rs
Outdated
| @@ -1141,7 +1141,7 @@ fn dispatch_permit_should_increase_account_nonce_correctly() { | |||
|
|
|||
| let hdx_balance = user_acc.balance(HDX); | |||
| let tx_fee = initial_user_hdx_balance - hdx_balance; | |||
| assert_eq!(tx_fee, 1_916_889_814_194); | |||
| assert_eq!(tx_fee, 1_930_010_523_303); | |||
| @@ -47,7 +47,7 @@ fn non_native_fee_payment_works_with_oracle_price_based_on_onchain_route() { | |||
| ) | |||
| ); | |||
| let bob_balance = hydradx_runtime::Tokens::free_balance(BTC, &AccountId::from(BOB)); | |||
| assert_eq!(bob_balance, 999969); | |||
| assert_eq!(bob_balance, 999964); | |||
| @@ -76,7 +76,7 @@ fn non_native_fee_payment_works_with_oracle_price_based_on_onchain_route() { | |||
| ); | |||
|
|
|||
| let dave_new_balance = hydradx_runtime::Tokens::free_balance(DAI, &AccountId::from(DAVE)); | |||
| assert_eq!(dave_new_balance, 999993637058691367900); | |||
| assert_eq!(dave_new_balance, 999_992_750_748_267_749_500); | |||
| @@ -109,7 +109,7 @@ fn set_currency_should_work_in_batch_transaction_when_first_tx() { | |||
| ) | |||
| ); | |||
| let bob_balance = hydradx_runtime::Tokens::free_balance(BTC, &AccountId::from(BOB)); | |||
| assert_eq!(bob_balance, 999969); | |||
| assert_eq!(bob_balance, 999964); | |||
| @@ -139,7 +139,7 @@ fn set_currency_should_work_in_batch_transaction_when_first_tx() { | |||
| ) | |||
| ); | |||
| let bob_balance = hydradx_runtime::Tokens::free_balance(BTC, &AccountId::from(BOB)); | |||
| assert_eq!(bob_balance, 999969); | |||
| assert_eq!(bob_balance, 999964); | |||
| @@ -260,4 +260,56 @@ where | |||
| config, | |||
| ) | |||
| } | |||
|
|
|||
| fn create_force_address( | |||
There was a problem hiding this comment.
Not sure who uses this, but EVM Runner requires this function.
There was a problem hiding this comment.
ok, i didnt found case yet, but creations of the contracts is restricted so we should make sure that we filter it accordingly if this would become avaliable for users somehow
i would currently just error out instead as "not supported" or something to be safe
mrq1911
approved these changes
Oct 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTES:
Merged feature
All changes can be found here:
Breaking changes:
Notable changes
System Callbacks: The system pallet gets five new config items - all of which can be safely set to () as default.
Add the ability for MessageQueue to process enqueued messages on idle
Rate limiting for RPC server which can be utilized by the CLI --rpc-rate-limit
Adds pallet-parameters that allows to have parameters for pallet configs that dynamically change at runtime
pallet-migrations is introduced that can be configured in the System of a runtime to act as multi-block migrator.
Add claim_assets extrinsic to pallet-xcm
The construct_runtime macro now generates a test to assert that all GenesisConfigs of all pallets can be build within the runtime.
XCM fee payment API: A runtime API was added for estimating the fees required for XCM execution and delivery.
pallet-xcm's extrinsics teleport_assets and reserve_transfer_assets have been marked as deprecated. Please change their usage to the limited_teleport_assets and limited_reserve_transfer_assets, respectively; or use the generic/flexible transfer_assets extrinsic.
pallet-xcm's extrinsics execute and send have been marked as deprecated. Please change their usage to the new execute_blob and send_blob. There's a new utility in PolkadotJS Apps for encoding XCMs you can use: https://polkadot.js.org/apps/#/utilities/xcm
Migrations: prevent accidentally using inner unversioned migration instead of VersionedMigration
Adds optional HRMP notification handlers to the xcm-executor. These handlers are 3 new config types on the xcm-executor Config trait:
The runtime now can provide a number of predefined presets of RuntimeGenesisConfig struct. This presets are intended to be used in different deployments, e.g.: local, staging, etc, and should be included into the corresponding chain-specs. Having GenesisConfig presets in runtime allows to fully decouple node from runtime types (the problem is described in #1984).
New call hrmp.establish_channel_with_system to allow parachains to establish a channel with a system parachain
(Breaking change) For all authority nodes, the node binary now enforces the presence of a network key, instead of auto-generating when it is absent.
pallet-xcm has a new extrinsic transfer_assets_using_type_and_then for transferring assets from local chain to destination chain using an explicit XCM transfer types for transferring the assets and the fees:
E.g. For transferring a bridged Foreign Assets between local parachains, Asset Hub or the parachain that bridged the asset over must be used as the reserve location. Same when transferring bridged assets back across the bridge, the local bridging parachain must be used as the explicit reserve location.
The new method takes a custom_xcm_on_dest parameter allowing the caller to specify what should happen to the transferred assets once they reach the dest chain. The custom_xcm_on_dest parameter should contains the instructions to execute on dest as a final step. Usually as simple as: Xcm(vec![DepositAsset { assets: Wild(AllCounted(assets.len())), beneficiary }]), but could be something more exotic like sending the assets even further.
Remove XCM SafeCallFilter for chains using Weights::v3