Guillaume Thiolliere

By the way I think it is actually fine to deny any non signed origin in extensions like `CheckWeight`, `CheckNonce` etc... I have the feeling that the final design of...

~`ValidateUnsigned::validate_unsigned` function takes `source: TransactionSource` as a parameter, this will be needed to be passed in some way to the transaction extension.~ ~EDIT: or do I miss something like unsigned...

Working on stage 2. The pre dispatch weight of a transaction extension would be more accurate if it had access to call information, explicit payload (and maybe even implicit payload,...

> > IMO the not allowed origin should not be able to appear in the pallet code at all. Otherwise pallet functions that ignore the origin could run into problems...

About supporting multiple set of transaction extension and having in the metadata: `Vec.` I think then we must put the extension version (`version_u8`) in the inherited implication. So that it...

> > About supporting multiple set of transaction extension and having in the metadata: `Vec.` I think then we must put the extension version (`version_u8`) in the inherited implication. So...

> @gui1117 I see now what corner case you're talking about. I personally think this would be extremely improbable, but if we want to address it, we should just provide...

Hopefully the last commit fix the CI for benchmarks I don't know yet what is failing in CI migration tests. But I don't have time today, I will look into...

CI should be fixed with https://github.com/paritytech/polkadot-sdk/pull/4904

> Looks good except for this one question and we need an XCM program to properly burn things on Asset Hub (see https://github.com/paritytech/polkadot-sdk/pull/3940/files#diff-37cc15e938c38da98634db29e597af5b5233e3eda662e79491ded2f58c943b52R50-R81) I added burn at relay, but I...