public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Eric Lombrozo <elombrozo@gmail.com>
To: Peter Todd <pete@petertodd.org>
Cc: Jean-Paul Kogelman via bitcoin-dev
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis
Date: Fri, 24 Jul 2015 13:23:27 -0700	[thread overview]
Message-ID: <D7531018-087E-4588-B113-7DD838E4ED22@gmail.com> (raw)
In-Reply-To: <20150724174320.GB25947@savin.petertodd.org>


[-- Attachment #1.1: Type: text/plain, Size: 1906 bytes --]

Thanks for bringing up the CCSS, Adam and Peter.

I was actually working on a post inviting everyone in this mailing list to come and participate…but you guys beat me to it. :)

The CCSS is an open standard, born out of the belief that sharing the industry's best practices amongst each other and with the community at large benefits everyone.

To read more about it and how you can contribute, please visit http://blog.cryptoconsortium.org/contributing-to-the-ccss/ <http://blog.cryptoconsortium.org/contributing-to-the-ccss/>

The standard:  https://cryptoconsortium.github.io/CCSS/ <https://cryptoconsortium.github.io/CCSS/>

The github repository: https://github.com/CryptoConsortium/CCSS <https://github.com/CryptoConsortium/CCSS>


- Eric

> On Jul 24, 2015, at 10:43 AM, Peter Todd via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> 
> On Fri, Jul 24, 2015 at 03:39:08PM +0200, Thomas Zander via bitcoin-dev wrote:
>> On Friday 24. July 2015 05.37.30 Slurms MacKenzie via bitcoin-dev wrote:
>>> It's worth noting that even massive companies with $30M USD of funding don't
>>> run a single Bitcoin Core node,
>> 
>> I assume you mean that they don't have a Bitcoin Core node that is open to
>> incoming connections. Since that is the only thing you can actually test, no?
> 
> We can test the fact that blockchain.info's wallet and block explorer
> has behaved in a way consistent with not running a full node - they have
> shown invalid data that any full node would reject on multiple
> occasions, most recently invalid confirmations during the BIP66 fork.
> 
> --
> 'peter'[:-1]@petertodd.org
> 000000000000000006baf20e289b563e3ec69320275086169a47e9c58d4abfba
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #1.2: Type: text/html, Size: 3153 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]

  reply	other threads:[~2015-07-24 20:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  2:57 [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing" Analysis Dave Scotese
2015-07-24  3:37 ` Slurms MacKenzie
2015-07-24 11:38   ` Mike Hearn
2015-07-24 14:09     ` Adam Back
2015-07-24 15:22       ` Simon Liu
2015-07-24 17:40       ` Peter Todd
2015-07-24 20:28         ` Eric Lombrozo
2015-07-24 20:31           ` Eric Lombrozo
2015-07-24 15:08     ` Dave Scotese
2015-07-24 13:39   ` Thomas Zander
2015-07-24 17:43     ` Peter Todd
2015-07-24 20:23       ` Eric Lombrozo [this message]
2015-07-24 21:12       ` Slurms MacKenzie
2015-07-24 15:40 ` Milly Bitcoin
2015-07-25  2:23 Dave Scotese
2015-07-25 11:19 ` Slurms MacKenzie

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=D7531018-087E-4588-B113-7DD838E4ED22@gmail.com \
    --to=elombrozo@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=pete@petertodd.org \
    /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