Your web3 username | Join the chat in /ens

Learn more: ens.domains | Register: app.ens.domains

we're exploring the space of "multi-address @ensdomains" with basenames — e.g. linking multiple addresses to your name, so you can be your whole self onchain. 

if you've explored this, would love to learn from you: share a link in the thread or reply!

Doing it on @payflow, but more on the application level, I assume you’re referring to a protocol solution?

The basic thought could be attestations to link wallets together, similarly the way it’s done on farcaster, but for everyone usage, however you still need an identity to rule them all :)

Or it could be many-to-many mapping, any identity can be a global identity with a list of bi-directional proofs of other linked wallets

@jessepollak, would be awesome if it was part of ENS protocol and not only basenames, I was exploring if we could use attestations for that with many-to-many bi-directional proofs similar the way it's implemented on farcaster

Some input I left on similar discussion:

@base builder #001; onchain cities w/ OAK & city3

@jessepollak, would be awesome if it was part of ENS protocol and not only basenames, I was exploring if we could use attestations for that with many-to-many bi-directional proofs similar the way it's implemented on farcaster

Some input I left on similar discussion:
https://warpcast.com/sinaver.eth/0xc8314215

Crimean building @payflow

/payflow /ideas /crimea 🛡🌎🇺🇦 

awesome happy to integrate it into @payflow, similar the way I pull farcaster verified addresses into list of payment flows, if identity which holds basename has linked multiple addresses, that would be pulled as well

yes agree - whatever we do will be done as an ENSIP + support in the basename registrar/resolver as a first example