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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <dennison@dennisonbertram.com>) id 1UneUr-0007Yy-Kb
for bitcoin-development@lists.sourceforge.net;
Sat, 15 Jun 2013 00:37:37 +0000
X-ACL-Warn:
Received: from mail-ee0-f49.google.com ([74.125.83.49])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UneUq-0001wU-Jg
for bitcoin-development@lists.sourceforge.net;
Sat, 15 Jun 2013 00:37:37 +0000
Received: by mail-ee0-f49.google.com with SMTP id b57so657924eek.8
for <bitcoin-development@lists.sourceforge.net>;
Fri, 14 Jun 2013 17:37:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=references:mime-version:in-reply-to:content-type
:content-transfer-encoding:message-id:cc:x-mailer:from:subject:date
:to:x-gm-message-state;
bh=uqXsmtj3AGVSGzLyiYXheetRBFeh570zwRk9PPHYrew=;
b=SJqoVdLqnXkeIUfa8BgBRmZTOBvpZ4++zNy5v8EcYZiXvKT7dQFvSP8OKT+hboydbB
Lmx6qqsyDtzMNtkvgHbJmT89HlnVmfVClHFhuF1GVoOiuJN67Vy2O6ZCuVXgoEsuXaXQ
7Z1dp0D0g8fguBt9imrVXbJaZv6dlucccYEDoHOvo6oVKn1MgqaXIYj/Oqzwj9ElMbzU
TfOP8B8rPw2NKvyBBNBh8zhP7usm/qMqxUBZU+iahvHO5S0iNfyTIYcS7jLH/GOB4Sqs
4BDe2PIT0BUe0yxx6/+7DlsCoDVG9Q8MXcydSqa4tbpjYSWgD2pNwZj2FrI+LGYeus4Q
2zmg==
X-Received: by 10.15.75.70 with SMTP id k46mr5564532eey.80.1371254951039;
Fri, 14 Jun 2013 17:09:11 -0700 (PDT)
Received: from [192.168.1.180]
(host152-91-dynamic.54-79-r.retail.telecomitalia.it. [79.54.91.152])
by mx.google.com with ESMTPSA id bk1sm6856534eeb.5.2013.06.14.17.09.09
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 14 Jun 2013 17:09:10 -0700 (PDT)
References: <20130519132359.GA12366@netbook.cypherspace.org>
<20130614192058.GA11509@petertodd.org>
<20130614205031.GB10215@netbook.cypherspace.org>
<201306142110.09687.luke@dashjr.org>
<51BB8A58.7000308@petersson.at>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51BB8A58.7000308@petersson.at>
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <27BA300C-71B8-4AB1-9459-09975ABED8EB@dennisonbertram.com>
X-Mailer: iPhone Mail (10A523)
From: Dennison Bertram <dennison@dennisonbertram.com>
Date: Sat, 15 Jun 2013 02:09:09 +0200
To: Andreas Petersson <andreas@petersson.at>
X-Gm-Message-State: ALoCoQnf9zSB3qKDj9ML0qBqj73lW6L3TOifODiVvyifZqnxaogVyWf7zCOFSyjSNO49jo7i4/xv
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1UneUq-0001wU-Jg
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] is there a way to do bitcoin-staging?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 15 Jun 2013 00:37:37 -0000
It seems so much easier to just allow bitcoin testnet to be used more widely=
for larger scale bitcoin staging. People can assign value as they wish to t=
estnet bitcoins but at their own risk/peril. This incremental amount of valu=
e though would allow for testing of larger ideas, ideas that perhaps might n=
ot be appropriate in their nascent stages to apply for bitcoin.=20
Have your seen 'proof of existence'? It's basically a bitcoin notary service=
that proves a document existed before it gets inserted into the blockchain.=
While a good idea- you could argue that it's blockchain spam as well- espec=
ially if one were to adapt it to high volumes in the future for notarizing p=
ermanently things like tweets (for example) or combining it with something l=
ike colored coins. These are great ideas, but maybe better suited to a proto=
bitcoin without needing to fashion a brand new coin.=20
Sent from my iPhone
On Jun 14, 2013, at 11:25 PM, Andreas Petersson <andreas@petersson.at> wrote=
:
> my initial idea (not sure if it is good) was to have an asymetric market.
> lets say you want to create altcoin ALC. ALC are merge-mined with btc,
> though without block reward.
> to create 1 ALC you have two choices: destroy 1 BTC, or buy 1 ALC for a
> floating amount from an exchange.
>=20
> in my book, this would automatically lead to a slightly lower price for
> 1 ALC, and an automatic ceiling of 1 BTC, since you could always
> sacrifice BTC to gain ALC.
> but it would not diverge drastically lower, since apparently somebody
> was willing to destroy 1 BTC to create it. maybe it could even trade
> slightly higher because traded ALC could be spendable instantly while
> sacrificed ALC would need a 120 blocks maturing period.
> the "beauty" of that system is also it does not inflate the
> cryptocurrency realm.
>=20
> Andreas
>=20
> Am 14.06.2013 23:10, schrieb Luke-Jr:
>> Note that the "earn a mixture of BTC and TBC, but not both in full volume=
"=20
>> only works for TBC because the price is by definition fixed with BTC.
>> I'm not sure how you could implement something like this for an altcoin w=
here=20
>> the price is floating independently of Bitcoin.. that is, how you would k=
now=20
>> the right amount of Bitcoin to require sacrificed.
>=20
>=20
> --------------------------------------------------------------------------=
----
> This SF.net email is sponsored by Windows:
>=20
> Build for Windows Store.
>=20
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
