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
|
Return-Path: <loneroassociation@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id BE6E1C0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Mar 2021 23:42:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id BA51D4EC6F
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Mar 2021 23:42:53 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5
tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp4.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id pHruPZGl-wEc
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Mar 2021 23:42:52 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com
[IPv6:2607:f8b0:4864:20::b34])
by smtp4.osuosl.org (Postfix) with ESMTPS id C78724EC6E
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 4 Mar 2021 23:42:52 +0000 (UTC)
Received: by mail-yb1-xb34.google.com with SMTP id h82so16663222ybc.13
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 04 Mar 2021 15:42:52 -0800 (PST)
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=gxYqmPloc9znFMBMhO3a4lfsR0Q5eZ6frLGDa8xh3lc=;
b=sRjL33ZymcIoHVP/aZjkBwG8tKW0fSX+yavE4ItJA3NHr0boqzIUaeQDfQUnKkFZO3
3jmaRE07SxR+yszcwtEnxmSrCJkbquRdKZx6y7rmujVSHjD8esILr3OVw+e/rRMc/maW
GL9sXOj9br/iDTgKfnHU0rfwuQ+7//pP2zPASjHq2/uZuJWbAmMcEkIhxd0x6OQ8Qu5n
o9UpIzyOSHibVov9hsynlDaUuIWepK2GpPwD0KEmxNl0nDUWIG6HX0CfEJ3t1w95HSRE
avYf7KBRTsreR6Bsad9EGVz+PCrM3QlcHAPB9QNJL3W6JEjd05L/GkC/10thHgO3twl6
2RbQ==
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=gxYqmPloc9znFMBMhO3a4lfsR0Q5eZ6frLGDa8xh3lc=;
b=EeHcPaOE9JVazPNiO1aeNLiO5x3eXeMDzf7qtWsFb7kjeZrCfERpCvXmITyTMjtN30
3Z2Im0ZoqnRGqt+5x6Ou6hZAGnM/kMsJdoJqhtdAFCpY6/Pyv+A4daPzB8PdMi/cHH5e
+wTCC9TzJx2I15rMhZBMqt2lhmzu+E6be7FgfrN0yoAbWDq6aeAhEtsB/XGu8CgetcX2
Hn7fIXwf3KBc9s2O4m2FtKHVHGexoSdvHgD6F+RiwEog7e+bNb4euLFP9rspuP1oixfk
XQNxQXbhsZv/Lx3zUYTP7OzzTh2buAl0VIplfZoYhLJl/fazfpRTQO01uWvWrUSAn2Wj
JQJQ==
X-Gm-Message-State: AOAM533Vgl9Vr9GTB7nU21vY2MLMWVjFWWMqLVNaFQ2yoJzxeQ0niPRc
tLKBF1ptHQmfJZqio4OJdaSnEglNvIDdXfGCojmSCpbWArE=
X-Google-Smtp-Source: ABdhPJzvq47ser3n6HWliHgQosu2uS4Z6cfL5DBeeSD20q61Wty++xD4GW3tDwa2iQmMl7R5eFLeUfMarbzRf+jZJno=
X-Received: by 2002:a25:ae14:: with SMTP id a20mr10600277ybj.129.1614901371132;
Thu, 04 Mar 2021 15:42:51 -0800 (PST)
MIME-Version: 1.0
From: Lonero Foundation <loneroassociation@gmail.com>
Date: Thu, 4 Mar 2021 18:42:40 -0500
Message-ID: <CA+YkXXxUdZFYTa1c-F=-FzoQQVtV3GUmE2Okec-zRAD3xS1qAQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="00000000000092dd1105bcbe8666"
X-Mailman-Approved-At: Fri, 05 Mar 2021 09:39:24 +0000
Subject: [bitcoin-dev] BIP Proposal: Consensus (hard fork) PoST Datastore
for Energy Efficient Mining
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
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, 04 Mar 2021 23:42:53 -0000
--00000000000092dd1105bcbe8666
Content-Type: text/plain; charset="UTF-8"
Hello, I want to start a new BIP proposal aiming to tackle some of the
energy efficiency issues w/ Bitcoin mining. Excuse my ignorance given this
is my first time making a BIP proposal, but is there a specific format I
need to follow? Do I just make a draft on my personal GitHub or need to
attach the README?
Anyways my idea is centered around a hybrid mining integration w/ POW/PoST
for BTC's SHA-256 hash algorithm. The integration is actually a
cryptography proof. While I would prefer a soft fork integration, a vastly
different cryptography proof without affecting the current node integration
is less than feasible.
Anyways, I do want to submit my document explaining everything and how all
this would work. I am mostly a Quantum Engineer and Bioinformatics
consultant for a living, so I think what I can propose to an extent may be
of interest to some.
Best regards,
Andrew M. K. Nassief
--00000000000092dd1105bcbe8666
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Hello, I want to start a new BIP proposal aiming to t=
ackle some of=20
the energy efficiency issues w/ Bitcoin mining. Excuse my ignorance=20
given this is my first time making a BIP proposal, but is there a=20
specific format I need to follow? Do I just make a draft on my personal=20
GitHub or need to attach the README?=C2=A0 <br></div><div><br></div><div>An=
yways my idea is centered around a hybrid mining integration w/ POW/PoST fo=
r BTC's <span><span>SHA-256
hash algorithm. The integration is actually a cryptography proof. While
I would prefer a soft fork integration, a vastly different cryptography
proof without affecting the current node integration is less than=20
feasible.</span></span></div><div><span><span><br></span></span></div><div>=
<span><span>Anyways,
I do want to submit my document explaining everything and how all this=20
would work. I am mostly a Quantum Engineer and Bioinformatics consultant
for a living, so I think what I can propose to an extent may be of=20
interest to some.</span></span></div><div><span><span><br></span></span></d=
iv><div><span><span>Best regards, <br></span></span></div><div><span><span>=
Andrew M. K. Nassief</span></span></div></div>
--00000000000092dd1105bcbe8666--
|
