-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: ethereum transaction pallet must forward to pallet-ethereum::transact #1536
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am missing expertise to evaluate the changes for the router and gateway but given that this is the result of a long debugging session, I am optimistically approving. Rest LGTM!
TransactionSignature::new( | ||
TRANSACTION_RECOVERY_ID, | ||
H256::from_low_u64_be(1u64), | ||
H256::from_low_u64_be(1u64), | ||
H256::from_low_u64_be(2u64), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to make sure this bump is intended? If you have the time, would be interested what this number reflects as the type is quite opaque:
pub struct TransactionSignature {
v: TransactionRecoveryId,
r: H256,
s: H256,
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just wanted the signature to not match the one from pallet-xcm-transactor
. I have to be honest, no clue whether this makes snese. The signature is not checked, so I guess it is not really relevant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All right, thanks nevertheless!
pallets/liquidity-pools/src/lib.rs
Outdated
/// An incoming LP message was | ||
/// detected and is further processed | ||
IncomingMessage { | ||
sender: DomainAddress, | ||
msg: MessageOf<T>, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On a note: I would like to introduce the opposite OutgoingMessage
enum event in #1473
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I also add it here do you mean? In this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, not at all. I should have been more explicit. I wanted to express I am happy the opposite of my planned Event
impl for Liquidity Pools will be implemented by this PR as this is a good signal for my plans.
Description
Axelar depends on the
pallet_ethereum::Event<T>::Transact{..}
and we were previsoulsy shortcircuting the logic, which lead to the event missing. This change fixes that behaviour and just generates the same origin as the runtime and forwards directly topallet-ethereum
.Changes and Descriptions
pallet-ethereum::Pallet::<T>::transact(..)
Checklist: