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.

This comment has been minimized.

edited

Looking forward to this component!

Some thoughts to help with "DAO founder doppelgängers" is to also have some kind of special "verified" (Twitter-like) badge, so then for example, let's say I am an ANT holder, we end up knowing who the real "Luis Iván Cuende" really is, and someone else can't assume his entity when creating votes and tricking people into thinking it was Luis who created the vote.

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).

Can also use Keybase as a form of validator as well - the DAO founders use Keybase/social proofs as an "oracle" to validate people's identities (for people they don't personally know).

Or maybe instead of using Keybase, there is a Twitter/Github integration to post your DAO address as an issue in an "Aragon Identity Validator" repo or as a Tweet, to map your identity as a social proof independent of Keybase.

But the DAO founder way may be a good enough near-term solution, perhaps with a Veto option for members of the DAO to contest a verified badge, if members of the DAO have some proof of manipulation.

There can also be a vote for other members of the DAO who want to help with this identity validation / Sybil Detection for doppelgängers.The term for these people may be "Sybil Detection Good Samaritans aka Sybil Detectives", and the founders begin with this role, then later transfer it over to the Sybil Detectives.

Can you explain the design reasoning for why the address in the popup has a blue background color? Is it only blue once the copy to clipboard icon is clicked, or is it always meant to be blue like this?

This comment has been minimized.

Does the current architecture support autocomplete throughout all Aragon Apps for the "Recipient" address fields, tying it to the Identity app, or do enhancements need to be made to support this paradigm?

edited

This comment has been minimized.

edited

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)