-
Notifications
You must be signed in to change notification settings - Fork 33
Figure out ENS names #510
Comments
cc @joshfraser |
We currently own Here's my current thinking on how to utilize them:
Thoughts? Anything I'm missing? |
Perhaps:
origintoken.eth
originprotocoltoken.eth
…On Wed, Sep 19, 2018 at 8:09 PM, Josh Fraser ***@***.***> wrote:
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
<https://github.com/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?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#510 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEuxN_91QLWaQ0imERi-yxSPE7n7jKA_ks5ucwbfgaJpZM4WxQ8F>
.
--
Cofounder of Origin <http://www.originprotocol.com>
Join our Telegram <http://t.me/originprotocol>
|
I assume this is not blocking for Mainnet launch, correct ? |
FYI, we'll know by tonight whether we won the auctions. It's pretty easy for us to point them wherever we want. |
Are we using ENS names for anything? Maybe the marketplace and token contracts?
The text was updated successfully, but these errors were encountered: