Rodrigo Quelhas

@sorpaas for `EIP-2537`, we should port the changes from frontier: https://github.com/polkadot-evm/frontier/tree/7b058d322b93712daf080e997bc0e4c4b00b21fb/frame/evm/precompile/bls12381

For `EIP-7702`, it was added here https://github.com/rust-ethereum/evm/pull/323. Still needs to be ported to master

For `EIP-7623`, it is currently in progress: https://github.com/rust-ethereum/evm/pull/389

> @RomarQ should this PR strengthen the security of the github actions? if so, how? (besides the repository content being set to read-only) @noandrea and @pLabarta are the ones working...

> @noandrea > > If I understand this correctly: lazy-loading-tests and zombie_upgrade_test use secrets and allow being triggered from PRs from forked repositories. > > twiggy could be used to...

Adding more context to the issue, it is related to the fact that when the payload `(Call, Extension, Extension::Implicit)` is bigger than `256` bytes, the function `crypto_sign_secp256k1` also needs to...

The identifier is for chains using [MultiSignature](https://github.com/paritytech/polkadot-sdk/blob/3dfbdf4a454f35238500779e503e1ec32ba7fc63/substrate/primitives/runtime/src/lib.rs#L291). On Moonbeam use use [ecdsa::Signature](https://github.com/moonbeam-foundation/moonbeam/blob/4c1a75aed28ab24deb9b4b5c698a74a428f1c1ac/primitives/account/src/lib.rs#L121), which does not wrap the signature in an enum (the extra byte you mentioned) The current implementation works...

> For information there I had 2 PR to upgrade usage to authorize call: > > * [[Tx ext stage 2: 3/4] use `#[pallet::authorize(...)]` to migrate unsigned in system: tasks...

> > Agreed, these 2 PR's you mentioned complement this one. What is blocking them? > > Because I think it is unnecessary breaking change. > > In general I...

Agree, we could simply update the output of the command to print a disclaimer informing that old versions of this command used `Ether` coin_type. Something like: ```ocaml Address: 0x... Mnemonic:...