git.delta.rocks / unique-network / refs/commits / 0982b02171d4

difftreelog

doc: sponsoring for unique is implemented via different structs

Yaroslav Bolyukin2022-09-11parent: #4c8a7eb.patch.diff
in: master

1 file changed

modifieddoc/sponsoring.mddiffbeforeafterboth
before · doc/sponsoring.md
1# Sponsoring23![Sponsoring flow](./sponsoring-flow.drawio.svg)45## Implementation67If you need to add sponsoring for pallet call, you should implement `SponsorshipHandler<AccountId, Call, ()>`89If you need to add sponsoring for EVM contract call, you should implement `SponsorshipHandler<CrossAccountId, (H160, Vec<u8>), CallContext>`1011For both examples, you can take a look at `UniqueSponsorshipHandler` struct inside of common runtime1213## EVM bridging1415In case if Ethereum call is being called using substrate `evm.call` extrinsic, `BridgeSponsorshipHandler` is used to convert between two different `SponsorshipHandler` types
after · doc/sponsoring.md
1# Sponsoring23![Sponsoring flow](./sponsoring-flow.drawio.svg)45## Implementation67If you need to add sponsoring for pallet call, you should implement `SponsorshipHandler<AccountId, Call, ()>`, see `UniqueSponsorshipHandler` for example.89If you need to add sponsoring for EVM contract call, you should implement `SponsorshipHandler<CrossAccountId, (H160, Vec<u8>), CallContext>`, see `UniqueEthSponsorshipHandler` for example.1011## EVM bridging1213In case if Ethereum call is being called using substrate `evm.call` extrinsic, `BridgeSponsorshipHandler` is used to convert between two different `SponsorshipHandler` types