Skip to content
This repository has been archived by the owner on Jan 14, 2020. It is now read-only.

Figure out ENS names #510

Open
cuongdo opened this issue Sep 20, 2018 · 5 comments
Open

Figure out ENS names #510

cuongdo opened this issue Sep 20, 2018 · 5 comments

Comments

@cuongdo
Copy link
Contributor

cuongdo commented Sep 20, 2018

Are we using ENS names for anything? Maybe the marketplace and token contracts?

@micahalcorn micahalcorn added this to Backlog in Origin Project Sprints via automation Sep 20, 2018
@cuongdo
Copy link
Contributor Author

cuongdo commented Sep 20, 2018

cc @joshfraser

@joshfraser
Copy link
Member

We currently own originprotocol.eth and originid.eth and I just started the process to acquire originmarket.eth, originmarketplace.eth, originstore.eth, originarbitration.eth and originsupport.eth. DM me if you think of others I missed that we should grab. There's a 7-character minimum, so unfortunately origin.eth unfortunately isn't an option.

Here's my current thinking on how to utilize them:

  • originid.eth - Origin-issued attestations. As @crazybuster and I were discussing today, this is also what we'd use if we decide to offer Origin usernames in the form of ENS subdomains (ie. joshfraser.originid.eth)

  • originprotocol.eth - ERC20 contract

  • originmarket.eth - marketplace contract

  • originsupport.eth - arbitration contract

Thoughts? Anything I'm missing?

@matthewliu
Copy link
Member

matthewliu commented Sep 20, 2018 via email

@franckc
Copy link
Member

franckc commented Sep 24, 2018

I assume this is not blocking for Mainnet launch, correct ?

@joshfraser
Copy link
Member

FYI, we'll know by tonight whether we won the auctions. It's pretty easy for us to point them wherever we want.

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

No branches or pull requests

4 participants