Skip to content
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

Add inbound queue #4

Merged
merged 8 commits into from
Nov 15, 2024
Merged

Conversation

ParthDesai
Copy link

No description provided.

use snowbridge_router_primitives::inbound::{MessageProcessor, VersionedXcmMessage};
use sp_runtime::DispatchError;

pub struct XcmMessageProcessor<T>(PhantomData<T>);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would probably call it some other thing but it is likely that snowbridge will tell you how to name it. So for me this is good enough

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reason why I named it XcmMessageProcessor as it expects incoming message to be converted to xcm. :) But, let's see what snowbridge thinks.

use alloy_primitives::B256;
use alloy_sol_types::{sol, SolEvent};

sol! {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is this macro?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sol! macro takes an event declaration in solidity and provides helper functions and also struct to work with that event data. Like encoding/decoding etc.

Copy link

@girazoki girazoki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for me it looks good, but please can you investigate what sol! does?

@ParthDesai ParthDesai merged commit 4e6395c into tanssi-polkadot-stable2407 Nov 15, 2024
18 of 39 checks passed
@ParthDesai ParthDesai deleted the add-inbound-queue branch November 15, 2024 10:21
chexware pushed a commit that referenced this pull request Nov 15, 2024
* modify inbound queue to support custom message processing

* passively test tuple trait implementation

* rename XCM to Xcm everywhere

* add comment explaining MessageProcessor
chexware pushed a commit that referenced this pull request Nov 23, 2024
* modify inbound queue to support custom message processing

* passively test tuple trait implementation

* rename XCM to Xcm everywhere

* add comment explaining MessageProcessor
tmpolaczyk pushed a commit that referenced this pull request Dec 31, 2024
* modify inbound queue to support custom message processing

* passively test tuple trait implementation

* rename XCM to Xcm everywhere

* add comment explaining MessageProcessor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants