-
Notifications
You must be signed in to change notification settings - Fork 15
Closed
Description
We should add the source_nonce to all relevant events we may like to track
Lines 198 to 211 in d38b4b0
| PortedTokens { who: AccountIdOf<T>, amount: BalanceOf<T> }, | |
| /// Minted some tokens ported from another chain! | |
| MintedPortedTokens { | |
| who: AccountIdOf<T>, | |
| amount: BalanceOf<T>, | |
| source_nonce: PortTokensNonceOf<T>, | |
| }, | |
| /// Forwarded some minted tokens to another location. | |
| ForwardedPortedTokens { who: AccountIdOf<T>, amount: BalanceOf<T>, location: T::Location }, | |
| /// Failed to forward the tokens to the final destination. | |
| FailedToForwardTokens { who: AccountIdOf<T>, amount: BalanceOf<T>, location: T::Location }, | |
| /// Tried to forward the tokens to an illegal destination, hence the operation was | |
| /// aborted (tokens were successfully minted on this chain though). | |
| IllegalForwardingLocation { location: T::Location }, |
- The porteer UI may want to watch for the
PortedTokensevents, extract the souce_nonce and then await theMintedPortedTokensevent with the matching nonce on the destination side - If direct forwarding to asset hub is selected, we still want to know that the TEER arrived well at the other side of the broidge, before we trace them on their way to asset hub
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels