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
|
Return-Path: <opensourcepj@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 67EBBD06
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 12 Jul 2018 08:05:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com
[209.85.208.177])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CF20576E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 12 Jul 2018 08:05:56 +0000 (UTC)
Received: by mail-lj1-f177.google.com with SMTP id a6-v6so21324350ljj.7
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 12 Jul 2018 01:05:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=9vCVBMzuPZZ41sZcpxtf6al6uJHCu+4UlOHYbf8MJf0=;
b=ZPHR0iiJOMNhin0s739PPlGwCdroXCIlnfRpmihWKTwjGp9Y3x4cU+BnfWCuaCuvPJ
hpoXsfYhy0yAaozBBmYy7Tr7T8eVxEd0Hd9W+eFWV8KY/1y2uJJmId/abHrbCzIOQVOj
XoZ8cdM0AHe63NhX1f2CZmPnZYkOCBE5Ozcld/SdT/QNLiUb9/Hba6yU6weXMFJMAntE
4WK3X3SlN9p06A2jU/0P+KdL2Km0a8OLed1wivhh5UOmumO1my/bvpiUp87AAhsnmuZM
oo6GJZuqi6J2UKxuFd7M/n3HdEfQr3vrxP2BapIAqZ6JYUDAuETqgdgxcEc5FLXT4k8N
isNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=9vCVBMzuPZZ41sZcpxtf6al6uJHCu+4UlOHYbf8MJf0=;
b=MKxiOwmsCi6dq4SK4xQGHcSkEKg32GN52kAUdZJlm3NSjTs0saDuP0WU6lfcKwBKJK
E53f/3mwPedqglLszdYx5ZIs6uKDcOZ5lfIjquKek4gPaepqf7M3RGBe2OxhjBCUQ9Tn
psyRymp5nRj66tnEecy0WGI969fd2r9s4y/zCcjfPe0XFtmrRqcSYu1adc//A4lb3l7t
ar3Zkcf5HuP8CfMYxQjtCscWpEJjRN+C9disqTpnVu9ie2TpnLgNfFRRh6jtMkHOaqXA
RS/kZ884CMmG/MHLDU6nVaCzskMMh8Jlz6j14o3WhdGe5bJqyJFdG3yrStpQ7uFrnU7u
CaYA==
X-Gm-Message-State: APt69E2cnsJyk5sET73xMEErBSMruwhbCvSP6rutM39EXrbh2AU3ni93
11Xd22JR9t/s9bss45GeDf+IBGHLTI8sfBLxrv8BuP84
X-Google-Smtp-Source: AAOMgpfEZGYvsph15S8xYVyFS49EG/Lp6v0E6cqsD3sjJm1epsFHThrP1H2c/bKSK03ZgXGi4f5daxySgZXeDDDM9eE=
X-Received: by 2002:a2e:80d3:: with SMTP id
r19-v6mr17102898ljg.85.1531382754814;
Thu, 12 Jul 2018 01:05:54 -0700 (PDT)
MIME-Version: 1.0
From: PJ Fitzpatrick <opensourcepj@gmail.com>
Date: Thu, 12 Jul 2018 09:05:42 +0100
Message-ID: <CAEpNEN4wP3CMtrs1ivj_o+VN95fqaDswXeEq858zyJ03TjxuUA@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="0000000000001db0920570c8d572"
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: Thu, 12 Jul 2018 22:46:36 +0000
Subject: [bitcoin-dev] Transaction Coins
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: Thu, 12 Jul 2018 08:05:57 -0000
--0000000000001db0920570c8d572
Content-Type: text/plain; charset="UTF-8"
I am considering a method to derive digital scarcity from bitcoin
transactions. Coins are created from transactions if their hash is among
the closest n to the non zero portion of the block hash. Only a single coin
can be created per transaction irrespective of the size of the transaction.
Therefore n coins are created per block.
The initial coin supply and addresses can be fully determined by the
existing blockchain. Additionally coins are scarce as coins can only be
produced by transactions.
There are a number of variants such as creating computation puzzles from
the previous block.
Has anyone seen anything similar.
PJ Fitzpatrick
--0000000000001db0920570c8d572
Content-Type: text/html; charset="UTF-8"
<div dir="ltr">
<p style="margin-bottom:0cm;line-height:100%">I am considering a
method to derive digital scarcity from bitcoin transactions. Coins
are created from transactions if their hash is among the closest n to
the non zero portion of the block hash. Only a single coin can be
created per transaction irrespective of the size of the transaction.
Therefore n coins are created per block.</p>
<p style="margin-bottom:0cm;line-height:100%">The initial coin
supply and addresses can be fully determined by the existing
blockchain. Additionally coins are scarce as coins can only be
produced by transactions.</p>
<p style="margin-bottom:0cm;line-height:100%">There are a number
of variants such as creating computation puzzles from the previous
block.</p>
<p style="margin-bottom:0cm;line-height:100%">Has anyone seen
anything similar.</p><p style="margin-bottom:0cm;line-height:100%"><br></p><p style="margin-bottom:0cm;line-height:100%">PJ Fitzpatrick</p><p style="margin-bottom:0cm;line-height:100%"><br></p></div>
--0000000000001db0920570c8d572--
|
