On Sun, May 11, 2014 at 4:08 AM, Saïvann Carignan wrote:
> A new "Developer Documentation" section should be soon merged on
> bitcoin.org .
>
> Live Preview:
> http://bitcoindev.us.to/en/developer-documentation
>
> GitHub Pull Request:
> https://github.com/bitcoin/bitcoin.org/pull/393
>
> Bitcoint
Christophe Biocca wrote:
> The problem is that since the rule
> isn't enforceable, no miner will wait before mining on the longest
> chain (which is the rational move), and you're back to where we are
> now.
Back up to the miner who decided to include a "seasoned" double-spend in
his block. Let
Would it be a terrible idea to amend BIP 70 to suggest implementors include
a "Access-Control-Allow-Origin: *" response header for their payment
request responses? I don't think this opens up any useful attack vectors.
I ask because this would make it practical for pure HTML5 web wallets to
use th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since it seems unlikely that we'll be able to ship an integrated stats /
monitoring feature in the short term, I went ahead and set up a public Statoshi
instance and threw a nicer interface on top of it.
http://statoshi.info
You can also view the r
4 matches
Mail list logo