Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 78F1912 for ; Wed, 25 Apr 2018 06:58:58 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-wr0-f176.google.com (mail-wr0-f176.google.com [209.85.128.176]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C4A9167B for ; Wed, 25 Apr 2018 06:58:57 +0000 (UTC) Received: by mail-wr0-f176.google.com with SMTP id q3-v6so42179259wrj.6 for ; Tue, 24 Apr 2018 23:58:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=zIxlKgU8f4Jz7bNL1UoyTs3dUdA5WOqqIKRNqWMNYbQ=; b=Zd6ftWrD0pUbhjyKShHl4i9H7GXqV2zx8GA0sf9Q3NqRD8krXPkdPduPdwFj4dfGUS hqEibBn0mcnEv3/7NDcU0VTRpRwsO6IszMQNauNkVyF+vmJZ7tHe03vNoADiQp/sSjIS vdj9miGMIjMsbHzj+oAxuiqEtmySLPBVVNA1NNhBIsDtZjudBgyya1mYs7xKUaGpaEOg r9PuA0aV1Uyapka/Hsp8VEMv8apFaOGkEmfSrqe5/aox8wNGbzxxUGXnzwEDO4g5MHIX iCk+wgG5NXGXJUtqwltBCR4eIrzn4GEGUoR0J3mccC61b7Ys0c0ELxtREYTidwhNphgu SR2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=zIxlKgU8f4Jz7bNL1UoyTs3dUdA5WOqqIKRNqWMNYbQ=; b=f1YWBMvxaGNlJ0v/ATe1t/paWDfy6iNuNfIFtDtKitUaHCXR8c5Htegbk9jpnR2aBh m3aQ1qIbb4J5CbyfzklE6tLBajoMfpi35fQHThE0LW3NKQ6w22S0d5ujgEFqI7YeZKBF 5Zdyx3H7t3XbQjrMu69Rl7UmZ2JfoPXUQcPMXiKjGShi8G8IWv97bfTJQjawq6qOX6TU nOwF+kb80PC6x3h6agRQFwof/5gvOlYjL7AnpHKWmCbZKM9lHeSUnx+i6t2nT8tQUn1L TXUfoHO1geyM2r1KdRZ4whE9G6fai7gyZTNGeqcU8j04PIxMk75PhzEGs/soUW7JwQHM BDzw== X-Gm-Message-State: ALQs6tC2YGbPpixC7WB+AvWUjmHV7NGdYBPyAQiNy5yasmvdPmb9OF5M H7myI1UsIsVnAof+HyFXYvZufLb+5LHRYlqKKI+yGQ== X-Google-Smtp-Source: AIpwx4+WtHo9JCsMCeWbeLDZu8EvBV5Xxb1CviCFMPDC4OmbT6cV3ET8dS8HRF2g2VgypabAAMt5YdKamOMGVH55WqI= X-Received: by 2002:adf:b90a:: with SMTP id k10-v6mr23864034wrf.283.1524639535703; Tue, 24 Apr 2018 23:58:55 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Tyler H Date: Wed, 25 Apr 2018 06:58:45 +0000 Message-ID: To: "bitcoin-dev@lists.linuxfoundation.org" Content-Type: multipart/alternative; boundary="000000000000efa990056aa6cd90" X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Wed, 25 Apr 2018 12:36:34 +0000 Subject: Re: [bitcoin-dev] Numerifides - Proposal for Decentralized trust/authority on Bitcoin blockchain X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Apr 2018 06:58:58 -0000 --000000000000efa990056aa6cd90 Content-Type: text/plain; charset="UTF-8" Hello again, I've reworked this idea a bit as alluded to previously. The key highlights of Numerifides are now: - Transaction is a normal transaction paying to a script hash with a CHECKSEQUENCEVERIFY encumbrance. - Users "mine" their registrations to produce TXIDs with Proof of Work attached (providing for a way to secure and "commandeer" names). - Secondary network for gossiping name->data mappings, that is rooted from the numerifide transactions on the Bitcoin blockchain. The "mining" is done simply by incrementing a nonce in the registration data (off-chain). This prevents "namesquatting" like we see on Namecoin. There is an easy formula that uses the Timelock, Proof of Work and amount of Bitcoin locked that determines which transactions are authoritative for a given name mapping. https://github.com/tyzbit/numerifides#technical-proposal Feedback and criticism appreciated, Tyler On Sat, Apr 21, 2018 at 8:35 AM Tyler H wrote: > Greetings, > > I have been working on a proposal called Numerifides which would provide a > general method to register human-readable names and arbitrary data (such as > username->GPG key, domain->IP address, Lightning node Alias-> URI, etc). > Here are the key highlights: > > --New transaction type called "numerifides" transactions > --Lock up Bitcoin for a certain amount of time to make the mappings valid, > discourage "namesquatting" > --Transaction puzzle attached to transactions to allow community consensus > revocation of highly contested names or "squatted" name mappings. > --Transactions are RBF so if name is contentious or miners wish to censor, > one honest greedy miner can include the censored user's high-fee > transaction) > --Solves Zooko's triangle of Secure, Decentralized and Human Meaningful > > Full working spec is here: https://github.com/tyzbit/numerifides > > I'd love feedback and possible enhancements, as I know this early rough > draft does have a lot of room for improvement (I also think it would be > remiss to incentivize filling blocks with data like this, and a possible > change proposed on the lightning-dev list by ZmnSCPxj is a P2WSH defining > the mapping that is gossiped about outside of the Bitcoin network, but I'd > like to hear all comments). > > Thank you for your time. > Tyler Hawkins > --000000000000efa990056aa6cd90 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello again,

I've rework= ed this idea a bit as alluded to previously.=C2=A0 The key highlights of Nu= merifides are now:

- Transaction is a normal trans= action paying to a script hash with a CHECKSEQUENCEVERIFY encumbrance.
- Users "mine" their registrations to produce TXIDs with Pr= oof of Work attached (providing for a way to secure and "commandeer&qu= ot; names).
- Secondary network for gossiping name->data mappi= ngs, that is rooted from the numerifide transactions on the Bitcoin blockch= ain.

The "mining" is done simply by incr= ementing a nonce in the registration data (off-chain).=C2=A0 This prevents = "namesquatting" like we see on Namecoin.

There is an easy formula that uses the Timelock, Proof of Work and amount = of Bitcoin locked that determines which transactions are authoritative for = a given name mapping.


Feedback and c= riticism appreciated,
Tyler

On Sat, Apr 21, 2018 at 8:35 AM Tyler H <tyzbit@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Greetings,

= I have been working on a proposal called Numerifides which would provide a = general method to register human-readable names and arbitrary data (such as= username->GPG key, domain->IP address, Lightning node Alias-> URI= , etc).=C2=A0 Here are the key highlights:

--New transaction type called "numerifides" transactions<= /div>
--Lock up Bitcoin fo= r a certain amount of time to make the mappings valid, discourage "nam= esquatting"
--T= ransaction puzzle attached to transactions to allow community consensus rev= ocation of highly contested names or "squatted" name mappings.
--Transactions are RBF= so if name is contentious or miners wish to censor, one honest greedy mine= r can include the censored user's high-fee transaction)
--Solves Zooko's triangle of Se= cure, Decentralized and Human Meaningful

Full working spec is here:=C2=A0https://github.com/tyzbit/numerifides

I'd love feedback and possible = enhancements, as I know this early rough draft does have a lot of room for = improvement (I also think it would be remiss to incentivize filling blocks = with data like this, and a possible change proposed on the lightning-dev li= st by=C2=A0ZmnSCPxj is a P2WSH defining the mapping that is gossiped about = outside of the Bitcoin network, but I'd like to hear all comments).

Thank you for your time.
Tyler Hawkins
--000000000000efa990056aa6cd90--