1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
Return-Path: <tyzbit@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 78F1912
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 25 Apr 2018 06:58:57 +0000 (UTC)
Received: by mail-wr0-f176.google.com with SMTP id q3-v6so42179259wrj.6
for <bitcoin-dev@lists.linuxfoundation.org>;
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: <CAEegQfVLWSySWfCbSmGG4V0i6GMpgyUr=86Qzb4YE9s+M5K1gg@mail.gmail.com>
In-Reply-To: <CAEegQfVLWSySWfCbSmGG4V0i6GMpgyUr=86Qzb4YE9s+M5K1gg@mail.gmail.com>
From: Tyler H <tyzbit@gmail.com>
Date: Wed, 25 Apr 2018 06:58:45 +0000
Message-ID: <CAEegQfW48ZUfxnHG4FFs0Z+BxYzhdLJkS_oiJcWhvp3iw6o3Ow@mail.gmail.com>
To: "bitcoin-dev@lists.linuxfoundation.org"
<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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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 <tyzbit@gmail.com> 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
<div dir=3D"ltr"><div>Hello again,</div><div><br></div><div>I've rework=
ed this idea a bit as alluded to previously.=C2=A0 The key highlights of Nu=
merifides are now:</div><div><br></div><div>- Transaction is a normal trans=
action paying to a script hash with a CHECKSEQUENCEVERIFY encumbrance.</div=
><div>- Users "mine" their registrations to produce TXIDs with Pr=
oof of Work attached (providing for a way to secure and "commandeer&qu=
ot; names).</div><div>- Secondary network for gossiping name->data mappi=
ngs, that is rooted from the numerifide transactions on the Bitcoin blockch=
ain.</div><div><br></div><div>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.</div><div><br></div><div=
>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.<br></div><div><div><br></div><div><a href=3D"https://=
github.com/tyzbit/numerifides#technical-proposal">https://github.com/tyzbit=
/numerifides#technical-proposal</a></div><div><br></div><div>Feedback and c=
riticism appreciated,</div><div>Tyler</div></div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr">On Sat, Apr 21, 2018 at 8:35 AM Tyler H <<a =
href=3D"mailto:tyzbit@gmail.com">tyzbit@gmail.com</a>> wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
#ccc solid;padding-left:1ex"><div dir=3D"ltr"><span style=3D"color:rgb(33,=
33,33);font-size:13px">Greetings,</span><div style=3D"color:rgb(33,33,33);f=
ont-size:13px"><br></div><div style=3D"color:rgb(33,33,33);font-size:13px">=
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:</div><div style=3D"color:rgb(33,=
33,33);font-size:13px"><br></div><div style=3D"color:rgb(33,33,33);font-siz=
e:13px">--New transaction type called "numerifides" transactions<=
/div><div style=3D"color:rgb(33,33,33);font-size:13px">--Lock up Bitcoin fo=
r a certain amount of time to make the mappings valid, discourage "nam=
esquatting"</div><div style=3D"color:rgb(33,33,33);font-size:13px">--T=
ransaction puzzle attached to transactions to allow community consensus rev=
ocation of highly contested names or "squatted" name mappings.</d=
iv><div style=3D"color:rgb(33,33,33);font-size:13px">--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)</div><div style=
=3D"color:rgb(33,33,33);font-size:13px">--Solves Zooko's triangle of Se=
cure, Decentralized and Human Meaningful</div><div style=3D"color:rgb(33,33=
,33);font-size:13px"><br></div><div style=3D"color:rgb(33,33,33);font-size:=
13px">Full working spec is here:=C2=A0<a href=3D"https://github.com/tyzbit/=
numerifides" target=3D"_blank">https://github.com/tyzbit/numerifides</a></d=
iv><div style=3D"color:rgb(33,33,33);font-size:13px"><br></div><div style=
=3D"color:rgb(33,33,33);font-size:13px">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).</di=
v><div style=3D"color:rgb(33,33,33);font-size:13px"><br></div><div style=3D=
"color:rgb(33,33,33);font-size:13px">Thank you for your time.</div><div sty=
le=3D"color:rgb(33,33,33);font-size:13px">Tyler Hawkins</div></div></blockq=
uote></div>
--000000000000efa990056aa6cd90--
|
