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 Latest Messages page #196

Open
jaybuidl opened this issue May 24, 2023 · 2 comments
Open

VeaScan Latest Messages page #196

jaybuidl opened this issue May 24, 2023 · 2 comments

Comments

@jaybuidl
Copy link
Member

jaybuidl commented May 24, 2023

`As a developer building on Vea, I want to see the list of latest messages going through the bridge, regardless of which snapshot they are included in."

Support #197 to jump to a particular message in the list.

Open question: is a dedicated page per message necessary?

Design in progress

@jaybuidl jaybuidl added the Package: VeaScan Web VeaScan Web label May 24, 2023
@jaybuidl jaybuidl added this to the 0.3 - devnet to chiado milestone May 24, 2023
@shotaronowhere
Copy link
Contributor

huh, I think the prioritize should be the other way around.

most users aren't interested in generic information (block headers, validator information, snapshots, etc)

most users are interested in specific information

the most utility will be analogous to

except we will have

-https://veascan.io/sendingChain/receivingChain/address/0x123...456 to see all messages sent from a specific address
-https://veascan.io/sendingChain/receivingChain/tx/msgId to see a specific message

I think a specific message landing page is more practically valuable to developers than a generic view. How many times do developers browse blocks on etherscan vs looking at a specific txn? How many times do developers browse 'recent transactions'?

99% of the time a dev uses a block explorer to look a specific transaction, or look for a specific transaction by navigating to an address page.

I would prioritize the address page which would just be the latest messages filtered by the sending contract address.

@jaybuidl
Copy link
Member Author

Tracking this feature here #258 @shotaronowhere

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