Tracking issue to bump substrate related deps to polkadot-v0.9.42

[dmitrylavrenov]

Diff

paritytech/substrate

paritytech/substrate@polkadot-v0.9.40...paritytech:substrate:polkadot-v0.9.42

paritytech/frontier

polkadot-evm/frontier@3b87145...polkadot-evm:frontier:e89f33688e0e438d0d26ca4f5eaba16a17201a22

Tasks

humanode-network/substrate fork

• Prepare locked branch
  https://github.com/humanode-network/substrate/tree/locked/polkadot-v0.9.42
• Fix casting usize to u8 at pallet::error macro (#91) (#95) substrate#99
• [Hotfix] Fix default http max connections value for RPC servers (#92) (#96) substrate#100

humanode-network/frontier fork

• Prepare locked branch
  https://github.com/humanode-network/frontier/tree/locked/polkadot-v0.9.42
• Use substrate locked/polkadot-v0.9.42 frontier#96
• Support external account provider (#83) (#92) frontier#97
• Include ED into account_basic balance data extraction frontier#98
• Sovereign accounts and EVM system layer (#94) frontier#99
• Sovereign EVM balances layer frontier#100
• Support Mutate, Unbalanced, Balanced fungible related traits for pallet-evm-balances frontier#102

[MOZGIII]

Substrate:

Part 1:

• paritytech/substrate@bd52212
• paritytech/substrate@be9e305
• paritytech/substrate@a2d4f7d
• paritytech/substrate@f8a1dd4
• paritytech/substrate@9d2d020
• paritytech/substrate@2b42fbd

Part 2:

• paritytech/substrate@d6899f8
• paritytech/substrate@988f6ad
• paritytech/substrate@bf395c8
• paritytech/substrate@656b139
• paritytech/substrate@ad66dd2
• paritytech/substrate@770d237
• paritytech/substrate@d0449fd
• paritytech/substrate@ea72382 - need to check the token claiming system
• paritytech/substrate@78c99da - yep, substrate has something broken due to prev stuff immediately, looks like this is a good suspicion
• paritytech/substrate@f40ba0d
• paritytech/substrate@49ba186 - we need to switch too
• paritytech/substrate@9c92e49
• paritytech/substrate@14f1a39
• paritytech/substrate@4499829
• paritytech/substrate@d6f278b - I've seen at least one more bs part there that I don't know how passed review - same issue as usual with that codebase...
• paritytech/substrate@bbcc63a - this is interesting
• paritytech/substrate@842e651 - not just batch verification
• paritytech/substrate@2961138 - to account for
• paritytech/substrate@057f2af - but why hardcoded fields only
• paritytech/substrate@8548a97 - investigate, see also Companion for paritytech/substrate#13811 paritytech/polkadot#6998

Part 3:

• paritytech/substrate@5601965
• paritytech/substrate@a1d3d50
• paritytech/substrate@9a07e9d - Interesting stuff for our bridges
• paritytech/substrate@2e94e25 - to apply - wasm constructor stuff
• paritytech/substrate@416b0f5 - metadata v15
• paritytech/substrate@32221d4 - check our balances implementation
• paritytech/substrate@da9f88d
• paritytech/substrate@a1f71b8 - check our impl
• paritytech/substrate@ea9ce4c - check our codebase
• paritytech/substrate@f0d3bbb - bump our stuff too
• paritytech/substrate@3f8dc9e
• paritytech/substrate@4e93782 - we should use this technique more
• paritytech/substrate@785115b - balances
• paritytech/substrate@cb95482
• paritytech/substrate@917f7e3 - cool stuff
• paritytech/substrate@37f3d58
• paritytech/substrate@2059dca - we probably need to account for this (sizes) at the infra level
• paritytech/substrate@471b49b - balances
• paritytech/substrate@b5846cc - oh well, they touched this stuff (cli)
• paritytech/substrate@db6ebf5 - offences
• paritytech/substrate@943c520
• paritytech/substrate@f2b6680 - this is nice - new syntax for weights
• paritytech/substrate@3bb3882 - something with fungibles
• paritytech/substrate@ff24c60 - check if this helps with anything we need, I recall it might

Done!