Pallet-Connectors-Gateway #1358
Replies: 5 comments 1 reply
-
Notes for the following state of the code: 44227eb Yes, we need that int the router, as we need a way to know what to call. Not sure if we need something different TBH. I think we should use the same derivation that we are using normally for native to I think we must look into the frontier implementation of Not sure. Need to look at frontier again. |
Beta Was this translation helpful? Give feedback.
-
Nevermind, I saw you need that for the encoding of the Axelar message. I would add a doc comment for the struct then that this is needed for Axelar routing or so. But really nice work already!!! |
Beta Was this translation helpful? Give feedback.
-
@cdamian In the production networks, calling pallet-evm will be only allowed for root. So we should change: pallet_evm::Pallet::<T>::call(
// The `call` method uses `EnsureAddressTruncated` to check this `origin`, this ensures
// that `origin` is the same as `source`.
RawOrigin::Signed(sender.clone()).into(), to pallet_ethereum::Pallet::<T>::transact(
// The `call` method uses `EnsureAddressTruncated` to check this `origin`, this ensures
// that `origin` is the same as `source`.
pallet_ethereum::RawOrigin::EthereumTransaction(sender).into(), The sender should be converted with our standard converter. See |
Beta Was this translation helpful? Give feedback.
-
Opened a draft PR, let's move any other discussions here - https://github.com/centrifuge/centrifuge-chain/pull/1376/files |
Beta Was this translation helpful? Give feedback.
-
Discussion ground for the gateway until we have a PR.
Beta Was this translation helpful? Give feedback.
All reactions