Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
AddressBadge component #3
A new proposed design for an address badge component, to be used whenever an entity name/ethereum address is need to display on the Aragon UI.
The rationale is that it should be very easy for users to visually distinguish in the UI when an entity is being referred to, and effortless to find out more information about that entity.
We allow shortening of long entity names/addresses where space doesn't allow for the full address, and by making the badge clickable we display the complete Ethereum address, make it very easy to copy the address, and make it easy to open the Etherscan url in another tab for more information.
Looking forward to this component!
Relating to this, we may want to also set a specific permission for who in the DAO can grant this "verified" badge to other people too?
Perhaps the DAO founders can be the initial set of "identity validators" / people who vouch for other identities within the DAO (I know this adds some element of centralization, but we all know very well how much of a problem identity is on Twitter).
I'm trying to find out more details because i'm wondering the complexity of integrating another app to read data from, to populate the autocomplete (e.g. one of the apps part of our planning suite - Address Book, which is useful for managing frequently used addresses of non-DAO members - which can be individuals, projects, multisigs, etc)