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

VeaScan route to a specific message id #197

Open
Tracked by #175
jaybuidl opened this issue May 24, 2023 · 1 comment
Open
Tracked by #175

VeaScan route to a specific message id #197

jaybuidl opened this issue May 24, 2023 · 1 comment

Comments

@jaybuidl
Copy link
Member

jaybuidl commented May 24, 2023

Route Example
/<chainIdFrom>/<chainIdTo>/msg/<msgid> /42161/1/msg/42
from Arbitrum to Ethereum, message id 42

❓Is a dedicated page per message necessary?

⚠️ Assumes a single Vea deployment between these 2 chains where the msgId is unique.

@shotaronowhere
Copy link
Contributor

imo, it would be the most useful feature of veascan.

after my cross-chain dapps sends a message to vea, i want to provide the user with information about that message, and track it's status, estimated time until successful bridging, a manual relay button if it's ready, etc.

imo this is why veascan is useful, everything else is a nice to have.

almost noone is interested in generic views, or even knowing about 'snapshots'

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

No branches or pull requests

2 participants