difftreelog
doc: sponsoring for unique is implemented via different structs
in: master
1 file changed
doc/sponsoring.mddiffbeforeafterboth445## Implementation5## Implementation667If you need to add sponsoring for pallet call, you should implement `SponsorshipHandler<AccountId, Call, ()>`7If you need to add sponsoring for pallet call, you should implement `SponsorshipHandler<AccountId, Call, ()>`, see `UniqueSponsorshipHandler` for example.889If you need to add sponsoring for EVM contract call, you should implement `SponsorshipHandler<CrossAccountId, (H160, Vec<u8>), CallContext>`9If you need to add sponsoring for EVM contract call, you should implement `SponsorshipHandler<CrossAccountId, (H160, Vec<u8>), CallContext>`, see `UniqueEthSponsorshipHandler` for example.101011For both examples, you can take a look at `UniqueSponsorshipHandler` struct inside of common runtime1213## EVM bridging11## EVM bridging141215In case if Ethereum call is being called using substrate `evm.call` extrinsic, `BridgeSponsorshipHandler` is used to convert between two different `SponsorshipHandler` types13In case if Ethereum call is being called using substrate `evm.call` extrinsic, `BridgeSponsorshipHandler` is used to convert between two different `SponsorshipHandler` types