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

Walnut Lite: Visualisation of supported chains #56

Open
mazurroman opened this issue Aug 27, 2024 · 1 comment
Open

Walnut Lite: Visualisation of supported chains #56

mazurroman opened this issue Aug 27, 2024 · 1 comment
Assignees

Comments

@mazurroman
Copy link
Contributor

This issue is about this section:
CleanShot 2024-08-27 at 14 36 46@2x

The visual is looking great already! I really like how the cards "float" making a "live" appeal. But we would like to introduce a notion of support for "maaaaaany" chains, not just four.

Some of the cards are currently less visible than others. That creates an idea: can we have cards "appear" and "disappear", in time? To create a visual impression that the user is debugging many transactions across many different chains?

Displaying 20 cards at the same time would be too much. So what about we keep showing four (two full visibility, two less visibility) and then, over few seconds, some of the cards become more visible, while others fade away and get replaced by new cards.

We can have a loop of 20 cards or so that keep appearing and disappearing. At any given time, the page would show 3-4 cards.

Regarding the cards design:

  • The "circle" will actually be a logo of each chain. I.e. Optimism Mainnet, Base, Zora, ...
  • It would be good to have the "circle" a bit larger
  • The tx hash: it's unclear this is a tx hash. We should probably make it a bit longer. @barabanovro would love to hear your thoughts
  • The chain name is OK with the exception of "Custom RPC: https". @barabanovro any suggestion what to use in this case?

@melnikga please wait with implementation until we flash out the specs

@barabanovro
Copy link
Contributor

  • I would suggest adding more symbols to the transaction hashes and placing the ellipsis at the end (similar to how it's done on Etherscan). Additionally, use different hashes for each transaction. For example: 0x24d525cba511fr7...
  • Use http://localhost:3000 instead of Custom RPC: https

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

No branches or pull requests

3 participants