🚬 Ethereum compatibility

[JuaniRios]

What?

• Add support for Ethereum based projects by letting users define the ethereum account that receives the tokens at the moment of participation.

How?

• Participation info structs now have a receiving_account field which is an xcm Junction. This has to be either AccountKey20 or AccountId32
• Issuers now define at project creation if they expect one or the other account Junction.
• Existing participation extrinsics now call the inner participation functions with AccountId32=caller
• New participation extrinsics now accept a junction, and a signature. The signature will be checked against the account defined in the signature to prove ownership.

Testing?

In the next PR

Anything Else?

For now we only support SR25519 signatures for Polkadot, and secp256k1 for Ethereum.
The Ethereum signatures also need some prefix defined in https://eips.ethereum.org/EIPS/eip-191

[JuaniRios]

• WETH from assethub support #427
• 🔧 Set round end block to None on evaluation fail #426
• ✅ ETH Compatibility Tests #425
• 🚬 Ethereum compatibility #420 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JuaniRios and the rest of your teammates on Graphite

[vstam1]

Lgtm. Cannot verify signature verification, but logic looks solid