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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1Z50La-0008Qf-CT
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 23:32:50 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.178 as permitted sender)
client-ip=209.85.213.178; envelope-from=gmaxwell@gmail.com;
helo=mail-ig0-f178.google.com;
Received: from mail-ig0-f178.google.com ([209.85.213.178])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z50LZ-0005aE-9Y
for bitcoin-development@lists.sourceforge.net;
Tue, 16 Jun 2015 23:32:50 +0000
Received: by igblz2 with SMTP id lz2so25449467igb.1
for <bitcoin-development@lists.sourceforge.net>;
Tue, 16 Jun 2015 16:32:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.43.168.6 with SMTP id ng6mr5795994icc.66.1434497564013; Tue,
16 Jun 2015 16:32:44 -0700 (PDT)
Received: by 10.107.147.213 with HTTP; Tue, 16 Jun 2015 16:32:43 -0700 (PDT)
Date: Tue, 16 Jun 2015 23:32:43 +0000
Message-ID: <CAAS2fgRKFTVu-rzr9spQZtMBrV0oGYmWVbiAOOhxkW4NnuzjHg@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z50LZ-0005aE-9Y
Subject: [Bitcoin-development] Lost proposals from FellowTraveler/Monetas
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: Tue, 16 Jun 2015 23:32:50 -0000
Is there any discussion thats been had relating to the BIP-drafts at:
https://github.com/Open-Transactions/rfc/tree/master/bips
Fellow Traveler has apparently been waiting 9 months for progress on
these proposals and I'm trying to find out where the breakdown
happened. While do not doubt that I am somehow at fault, I can't
figure out how.
Searching my email and this list archive for "Base58 Serialization for
Transaction-Based Color Descriptors" or "Order-based Smart Property
Coloring" or the draft names bip-ccids, etc. turn up no hits at all.
I've asked several other people and there list archives show nothing.
Has anyone else taken part in discussions related to these proposals
(or seen them all before)? If so, please point me to the discussion.
Otherwise I'll just go ahead and create threads for each under the
assumption that there is yet another mailing list screwup. :(
|
