Agent: set as organization's ENS name

[john-light]

I want to bring up a discussion about how we use ENS names in Aragon organizations.

Currently, users are being conditioned to think of ENS names as replacements for Ethereum addresses. Several wallets support this conditioning by enabling the sending of funds to ENS names.

However, that's not how Aragon uses ENS. If you send funds to an Aragon organizations ENS address, the funds are stuck until someone manually "recovers" them, and then they still don't show up in the organization's Finance app transaction history.

Is there a way that we can continue using ENS names as a way to address organizations, while also making the ENS name function the way people expect it to? Meaning that they can send funds to the ENS name and they will show up in the organization's transaction history and be immediately spendable without any extra work?

[sohkai]

A few potential ideas:

• Start assigning the org's ENS name to an app, and particularly only the Agent app makes sense for this (so the org could still manage the ENS name)
• The Kernel could proxy ETH into the default vault; unfortunately this would not work automatically for tokens
• We could have a "financial" dashboard in the client that knows about all value stored in the Kernel and apps, and users could spend from there directly
  • If value is stuck in an non-financial app / kernel, the user would first have to "recover" it into the default vault and then spend it from there

[john-light]

Just had an idea today: if we start to use the Agent app by default in place of the Vault app for all default templates, then we can assign the ENS name the user chooses to the Agent app. This solves two problems: the first is that people will be able to send tokens to the ENS name as expected, the second is that the ENS name will become transferable (and also changeable, both of which are not currently possible).

If we go this route, we would want to add some extra logic to the client so that the ENS name shows up in the URL when it's owned by the Agent app and in the case of older organizations where the main organization contract owns the ENS name. We'd also have to account for cases where the Agent app owns multiple names. (Do all names resolve to the org? Is only one of them designated as the "main" name?)

[sohkai]

@john-light Yes, @izqui have been thinking about this since 0.8 and it's something we may start doing with 0.9.