On Mon, May 18, 2015 at 2:42 AM, Rusty Russell ru...@rustcorp.com.au
wrote:
OK. Be nice if these were cleaned up, but I guess it's a sunk cost.
Yeah.
On the plus side, as people spend their money, old UTXOs would be used up
and then they would be included in the cost function. It is only
Thanks Stephen, I hadn't thought about BIP 34 and we need to address this
in both proposals. If we can avoid it I'd like not to have one transaction
hashed one way and other transactions in another way.
Since BIP 34 explicitly uses the scriptSig to make the coinbase transaction
unique, simply
Hello,
I've just tagged release candidate 1 for 0.9.5 (tag `v0.9.5rc1`).
The reason for this backport release is to make BIP66 available on the 0.9
branch. This has been requested by a few users, mostly miners.
Full (preliminary) release notes can be found at:
On Tue, May 19, 2015 at 9:28 AM, Christian Decker
decker.christ...@gmail.com wrote:
Thanks Stephen, I hadn't thought about BIP 34 and we need to address this
in both proposals. If we can avoid it I'd like not to have one
transaction hashed one way and other transactions in another way.
The
On Tue, May 19, 2015 at 11:16 AM Tier Nolan tier.no...@gmail.com wrote:
On Tue, May 19, 2015 at 9:28 AM, Christian Decker
decker.christ...@gmail.com wrote:
Thanks Stephen, I hadn't thought about BIP 34 and we need to address this
in both proposals. If we can avoid it I'd like not to have
Freundliche Grüsse
---
Jonas Schnelli
°°
include7 AG
Jonas Schnelli
Mattengasse 27
CH-8005 Zürich
Switzerland
Office: +41 44 500 16 70
Mail: jonas.schne...@include7.ch
Web: www.include7.ch
V-Card: www.include7.ch/js.vcf
Am 18.05.2015 um 23:57 schrieb Justus Ranvier
jus...@openbitcoinprivacyproject.org
mailto:jus...@openbitcoinprivacyproject.org:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Replying to the list because this is a common question.
We rated as many wallets as we could based on the
Hi
I briefly mentioned something about this on the bitcoin-dev IRC room. In
general, it seems experts (like sipa i.e. Pieter) are against using
sidechains as a way of scaling. As I only have a high level understanding
of the Bitcoin protocol, I cannot be sure if what I want to do is actually
An option would be that the height is included in the scriptSig for all
transactions, but for non-coinbase transctions, the height used is zero.
No need to add an extra field to the transaction just to include the
height. We can just add a rule that the height specified in the scriptSig
in
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep
Bitcoin Core version 0.10.2 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.10.2/
The distribution is also available as torrent:
https://bitcoin.org/bin/bitcoin-core-0.10.2/bitcoin-0.10.2.torrent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello all,
BitPay has just released our first whitepaper on ChainDB, a new
peer-to-peer database system backed by the Bitcoin blockchain. This
paper outlines our intended consensus mechanism, proof of fee.
Please take a look at the paper here:
Hello All,
Josh Rickmar and I discovered a subtle consensus change in Bitcoin Core
which causes forking behavior on regtest. Luckily it does not affect
mainnet or testnet, however it does mean that regtest difficulty
retargetting is broken.
I've made a post to the bitcointalk forums at
13 matches
Mail list logo
