summaryrefslogtreecommitdiff
path: root/f1/343bb7ce70fafaa02b16eb7f80145c43ee0a59
blob: 1d4fd2894d602d05b4d623ec95d4de645ad74cfc (plain)
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
Return-Path: <earonesty@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id C5B2071
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 26 Jun 2016 12:12:14 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-yw0-f172.google.com (mail-yw0-f172.google.com
	[209.85.161.172])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 51C51155
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 26 Jun 2016 12:12:14 +0000 (UTC)
Received: by mail-yw0-f172.google.com with SMTP id i12so132239192ywa.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sun, 26 Jun 2016 05:12:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:from:date:message-id:subject:to;
	bh=cX3PDbubv6Z+lQA5rZCjo7PieuFiqMURv1xh3ztB2qc=;
	b=TlCAazA2zPfe+JOsr4HtiYcTTWd15CcUGRtHm2nQMmgzWO7YrXlFBaILianoDW7ATz
	bnSh0HMVcUEoKjKmN3AhxIESS+nwcl8jIgaxTj92AfKkl35zuzp2HpPpkrMrDxOIut42
	tb/NykDAkWe9qZzXqM2Q1eXMwV2jrU5T/lomxvayaYrufzXymUMo8i7jO6HtD6iMSu79
	cKlWMjnj0ovY7IKgnQDEnB/LxNOP/YqgzdV44CJOr0aTX/X+Elsc0HwBa14snAzlEarP
	YiBht7pLFCIRqy0dW2glKOYqN1OL2JlU67qNq4WaGQJEAm7P6DmmdXthaV5lmk+xPVyf
	Kxqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:sender:from:date:message-id:subject
	:to; bh=cX3PDbubv6Z+lQA5rZCjo7PieuFiqMURv1xh3ztB2qc=;
	b=ZPzCLhgfmayCnm3ymFI7lFNYFVDLDSZ/u66U4KnfUpDAi60wrGSXOaecJOve+7auK3
	GedLpNnTIC5Iq7GfBkKH7bFzxU96PABmF+0fFq+8zlVaMSzLC0R1RP6E+lM8jiZECQaR
	u299jqidGdlnDZut9ftuUrphoG6YeTGbpUnT70C5Q+QKDVz6N7w6f/Rkzx2tArmnfEOZ
	7E/1VZ1P37oJkgFuYb4umEAkqHbIihb3gfOdRFRv9yQE3txXMJpjzEl0J4JL6c1606EA
	fZ9xfbkSROryWBbY+1ZPfFUIqbVqDFMdgdG5HjiWrcr5y7gwjO0eOmSNSJe5jB9RUJ24
	sndw==
X-Gm-Message-State: ALyK8tKgskbu2Gy2kK1kDMB5JPvshvbtajyVXgG8VoTzChDlYw2qA3FEkSl4AkFw2dy26NY7Gyi3rJsYC+TVvQ==
X-Received: by 10.37.65.144 with SMTP id o138mr7965004yba.87.1466943132047;
	Sun, 26 Jun 2016 05:12:12 -0700 (PDT)
MIME-Version: 1.0
Sender: earonesty@gmail.com
Received: by 10.37.72.68 with HTTP; Sun, 26 Jun 2016 05:12:11 -0700 (PDT)
From: Erik Aronesty <erik@q32.com>
Date: Sun, 26 Jun 2016 08:12:11 -0400
X-Google-Sender-Auth: 5ALsIpMnOsQu93dM10w9VIoEEEo
Message-ID: <CAJowKgJKQ+4MU1pUE6s7kJL2+r2rLfJC0V1X96CK=Z5FvV8p9A@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c05a544aa03f05362d500b
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, 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
Subject: [bitcoin-dev] parallel token idea & question
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: Sun, 26 Jun 2016 12:12:14 -0000

--001a11c05a544aa03f05362d500b
Content-Type: text/plain; charset=UTF-8

token miners who will work to the a new token signal readiness to secure
that token by posting a public key to the bitcoin blockchain along with a
collateral and possibly a block mined from a side chain, or some other
signal proving sufficient participation (allows for non-blockchain tokens).

coin moved to the new token set is sent to a multisig wallet consisting of
miners who have signaled readiness, with nlocktime set to some time in the
future

coin sits in that wallet - the new token doesn't even have to be a chain,
it could be a DAG, or some other mechanism - following whatever rules it
pleases

any time, miner of the new system can move coin back to the main chain...
trivially and following whatever rules are need.  also, any time a miner
fails to follow the rules of the new system, they lose their collateral

any sufficient consortium of miners/participants in the side chain can, of
course, steal that coin...but that is true for all sidechains - and to some
extent bitcoin - anyway

does this seem too simplistic or weak in some way?

--001a11c05a544aa03f05362d500b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">token miners who will work to the a new token signal readi=
ness to secure that token by posting a public key to the bitcoin blockchain=
 along with a collateral and possibly a block mined from a side chain, or s=
ome other signal proving sufficient participation (allows for non-blockchai=
n tokens).<div><br></div><div>coin moved to the new token set is sent to a =
multisig wallet consisting of miners who have signaled readiness, with nloc=
ktime set to some time in the future</div><div><br></div><div>coin sits in =
that wallet - the new token doesn&#39;t even have to be a chain, it could b=
e a DAG, or some other mechanism - following whatever rules it pleases</div=
><div><br></div><div>any time, miner of the new system can move coin back t=
o the main chain... trivially and following whatever rules are need. =C2=A0=
also, any time a miner fails to follow the rules of the new system, they lo=
se their collateral</div><div><br></div><div><div>any sufficient consortium=
 of miners/participants in the side chain can, of course, steal that coin..=
.but that is true for all sidechains - and to some extent bitcoin - anyway<=
/div></div><div><br></div><div>does this seem too simplistic or weak in som=
e way?=C2=A0<br></div></div>

--001a11c05a544aa03f05362d500b--