shotaronowhere
commented
1 year ago 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
`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