You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NTT transfers might get enqueued when delivered to the destination chain. When the NTT uses Standard Relaying and the message gets delivered we mark it as complete, but the funds might not get unlocked until later, which is a source of confusion for the user. We might benefit from adding a special status "Enqueued" for these transfers.
We'd need logic to query the pertinent contracts on EVMs/Solana to check whether a particular NTT message is enqueued or not. I took some notes on how to do so here, but haven't tried the ideas on code yet.
Also, I think we can narrow it down for VAAs with app ids GENERIC_RELAYER and NATIVE_TOKEN_TRANSFER, since the issue seems to be particular to the relayer scheme
The text was updated successfully, but these errors were encountered:
NTT transfers might get enqueued when delivered to the destination chain. When the NTT uses Standard Relaying and the message gets delivered we mark it as complete, but the funds might not get unlocked until later, which is a source of confusion for the user. We might benefit from adding a special status "Enqueued" for these transfers.
We'd need logic to query the pertinent contracts on EVMs/Solana to check whether a particular NTT message is enqueued or not. I took some notes on how to do so here, but haven't tried the ideas on code yet.
Also, I think we can narrow it down for VAAs with app ids
GENERIC_RELAYER
andNATIVE_TOKEN_TRANSFER
, since the issue seems to be particular to the relayer schemeThe text was updated successfully, but these errors were encountered: