From: Justus Ranvier <justus.ranvier@monetas•net>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Lost proposals from FellowTraveler/Monetas
Date: Tue, 16 Jun 2015 23:44:45 +0000 [thread overview]
Message-ID: <CAHabJ+Pqh_QDycWF4qjwy2duWntU7t2Z5FTw9sOTmx_BvhG7_A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2015-06-16 23:32, Gregory Maxwell wrote:
> 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.
The only two proposals we sent to the mailing list were attached to this
post:
http://sourceforge.net/p/bitcoin/mailman/message/32736455/
The rest of the proposals in that respository, as well as those the fork
here:
https://github.com/Monetas/rfc/tree/master/bips
were never submitted because we decided to use alternative identifiers in
leiu of BIP numbers to serve as the purpose code in the HD path.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJVgLRaAAoJECpf2nDq2eYjw7YQAJYrciEZZeasEJRR7XwZ5AWQ
9e/pz1SV2hoRs7TqHgHoXGINLbG9LwlXFmnoG14z+vwKvheJxlC6gOQCRIRwPfrR
zwuQWyoONHn82XL44ABqjnu0fmeh7egx3FIzsgDUxUgiP5dA0BuQvrT1+DptfJ+p
5sM7ZvRqfZJbek4AHk9Y4kERQYsP4HKgC1W3Acr1In9WPSj5TRtYz7tUK+SFcO+m
A3Ny5dUiAmmf5mfLZiWrEmCG34n+cCJZEU2hlQqH5ZuAHPmeTLuar91MLj/1Xltf
OFlMGhmUPy1alTx8o39nwRjfXIVQLk7/D5YB3gB2CUuXd+sWbY+6LUyniOKtQK3C
EmEDOUFSNm4JV1AmM+ea1HUufCJfkg1VHko4hsIyc1e7ztdECIzPQKAy7DAcu1YS
BhbkxNyaUqoF+J/ggrXhT/r5oVpWsifdj4IEzaMvmOxu+p+hTkzzwitLuyknEBZE
b2KWRMWNOheVpDp7RmrcTPqa4S1N8XcfJazDyigIhl0E/Bjk+pC1SHo7IIEMZMQ+
Fz7JaALd8XK0l7HBvvJnZmYwVLnQyB01B6n7z8eTTAneHhSXxa7Z1aFTkYU8Wp9o
L5nb1K7gJtjBFqhLi3PMLRhARao1Q/CK5bDt9Mb3VMy9jAIr9X9/NcL473cbHtQH
/h91bhkL9bvvkeCl5yQk
=NgfK
-----END PGP SIGNATURE-----
[-- Attachment #2: Type: text/html, Size: 4720 bytes --]
next reply other threads:[~2015-06-17 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 23:44 Justus Ranvier [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-16 23:32 Gregory Maxwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHabJ+Pqh_QDycWF4qjwy2duWntU7t2Z5FTw9sOTmx_BvhG7_A@mail.gmail.com \
--to=justus.ranvier@monetas$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox