From: odinn <odinn.cyberguerrilla@riseup.net>
To: Jeff Garzik <jgarzik@gmail.com>,
Bitcoin development mailing list
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP 100 repo
Date: Thu, 03 Sep 2015 06:41:20 +0000 [thread overview]
Message-ID: <55E7EB90.3010509@riseup.net> (raw)
In-Reply-To: <CADm_WcZEbAe_+VXxS1eMKQ1SM3KiJwVDS50-GtfUPw-Mdd5O2w@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Excellent - thank you.
Jeff Garzik via bitcoin-dev:
> Oops, link paste fail.
>
> The repo: https://github.com/jgarzik/bip100
>
>
> On Wed, Sep 2, 2015 at 7:51 PM, Jeff Garzik <jgarzik@gmail.com>
> wrote:
>
>> Opened a repo containing the full text of BIP 100 discussion
>> document, in markdown format.
>>
>> The BIP 100 formal spec will be checked in here as well, before
>> submitting to upstream bips.git repo.
>>
>>
>>
>
>
>
> _______________________________________________ bitcoin-dev mailing
> list bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
- --
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
iQEbBAEBCgAGBQJV5+uQAAoJEGxwq/inSG8CVBUH9A5GtIj3pLxZRlX0oDxSbIWJ
2830HURoeb40ShBlhbzO1nHiJtPhRPWqByZETQcuElBagMPreSKI5VZxJ1xaNOI3
o6yo9ujeLNlge1j53TOq8uQCXKnwrVsjS3yQkXlo+IX+Vihin5c/D4Xn9y97OqwQ
CixVswCJrrRrGHj6YaFsfAx+epaJ/aT4djoB0XjH9PKJI5b0cPGSBDipHbuVn3nd
FZidPAS/hHI0Sw3k0EHtYudjBXBbMi2hCad37asrg2cIF/sFbCA/BSkpuIi5agzY
50Wp8xm3gd4WWjEn/svhw2AIgH7R/1Yk2/qFImob5iXMm7sU1OUMHD325kN2dg==
=7a0Z
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-09-03 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 23:51 [bitcoin-dev] BIP 100 repo Jeff Garzik
2015-09-02 23:58 ` Jeff Garzik
2015-09-03 0:17 ` Luke Dashjr
2015-09-03 3:38 ` Jeff Garzik
2015-09-03 4:09 ` Jeff Garzik
2015-09-03 4:55 ` Benjamin
2015-09-03 6:41 ` odinn [this message]
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=55E7EB90.3010509@riseup.net \
--to=odinn.cyberguerrilla@riseup.net \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jgarzik@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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