[bitcoin-dev] Bitcoin Core 0.21.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.21.0 Release Notes Bitcoin Core version 0.21.0 is now available from: Or through BitTorrent: magnet:?xt=urn:btih:665c5bdc6f49948e47c1098d91ace98bd216150e&dn=bitcoin-

[bitcoin-dev] Bitcoin Core 0.20.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.20.1 Release Notes Bitcoin Core version 0.20.1 is now available from: Or through BitTorrent: magnet:?xt=urn:btih:6e2c72d73d763465a725e3ae941b2b937edd0300&dn=bitcoin-

[bitcoin-dev] Bitcoin Core 0.20.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.20.0 Release Notes Bitcoin Core version 0.20.0 is now available from: Or through BitTorrent: magnet:?xt=urn:btih:1845a0c66b6a728e183b9bd8c5d8c1611dddaaa3&dn=bitcoin-

[bitcoin-dev] Bitcoin Core 0.19.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 0.19.1 Release Notes === Bitcoin Core version 0.19.1 is now available from: or through BitTorrent: magnet:?xt=urn:btih:8b6ad1da5bbb24656234efc2370abc14781a6f83&dn

[bitcoin-dev] Bitcoin Core 0.18.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.18.1 is now available from: Or through BitTorrent: magnet:?xt=urn:btih:c3ba0cfee3ef8413098ac5e81db08a2670e9da8c&dn=bitcoin-core-0.18.1&tr=udp%3A%2F%2Ftracker.openbitt

[bitcoin-dev] Bitcoin Core 0.18.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.18.0 is now available from: or through bittorrent: magnet:?xt=urn:btih:a25c86ffa7a512b6d074287f74762b77f91cef4c&dn=bitcoin-core-0.18.0&tr=udp%3A%2F%2Ftracker.openbitt

[bitcoin-dev] BIP proposal - addrv2 message

See https://gist.github.com/laanwj/4fe8470881d7b9499eedc48dc9ef1ad1 for formatted version, Look under "Considerations" for topics that might still need to be discussed. BIP: ??? Layer: Peer Services Title: addrv2 message Author: Wladimir J. van der Laan Comments-Summary: No comments

[bitcoin-dev] Bitcoin Core 0.17.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.17.1 is now available from: or through BitTorrent: magnet:?xt=urn:btih:c56c87ccfaa8e6fbccc90d549121e61efd97cb6f&dn=bitcoin-core-0.17.1&tr=udp%3A%2F%2Ftracker.openbitt

[bitcoin-dev] Bitcoin Core 0.17.0.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.17.0.1 is now available from: or through BitTorrent: magnet:?xt=urn:btih:70749cf2cf2922a21208b4ae760c9f2f9d1e7f11&dn=bitcoin-core-0.17.0.1&tr=udp%3A%2F%2Ftracker.open

[bitcoin-dev] Bitcoin Core 0.17.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.17.0 is now available from: or through BitTorrent: magnet:?xt=urn:btih:1c72f17bc1667a2ce81860b75135e491f6637d05&dn=bitcoin-core-0.17.0&tr=udp%3A%2F%2Ftracker.openbittor

[bitcoin-dev] Bitcoin Core 0.15.2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version *0.15.2* is now available from: or through bittorrent: magnet:?xt=urn:btih:c0a23591e04ce45dd6349f3abc34df948c45537c&dn=bitcoin-core-0.15.2&tr=udp%3A%2F%2Ftracker.openbitt

[bitcoin-dev] Bitcoin Core 0.14.3 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version *0.14.3* is now available from: or through bitorrent: magnet:?xt=urn:btih:171edf5f51820900f24fc72620deaa07ee497dee&dn=bitcoin-core-0.14.3&tr=udp%3A%2F%2Ftracker.openbitto

[bitcoin-dev] Bitcoin Core 0.16.3 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.16.3 is now available from: or through bittorrent magnet:?xt=urn:btih:a6015029671a445a7a07026b3e4a0fe54c2b2df3&dn=bitcoin-core-0.16.3&tr=udp%3A%2F%2Ftracker.openbitto

[bitcoin-dev] Bitcoin Core 0.16.2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.16.2 is now available from: or through bittorrent: magnet:?xt=urn:btih:b64eacae7d6e5f7ba50de3da8aca4368c27f0823&dn=bitcoin-core-0.16.2&tr=udp%3A%2F%2Ftracker.openbitt

[bitcoin-dev] Bitcoin Core 0.16.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.16.1 is now available from: Or through bittorrent: magnet:?xt=urn:btih:91069028aaf9f6bb3279e71bfd9ab164922e578e&dn=bitcoin-core-0.16.1&tr=udp%3A%2F%2Ftracker.openbittor

[bitcoin-dev] Bitcoin Core 0.16.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.16.0 is now available from: or through bittorrent: magnet:?xt=urn:btih:6493ae7a15b4d32bb4eca1dfaf6dcc0c143492cb&dn=bitcoin-core-0.16.0&tr=udp%3A%2F%2Ftracker.openbittor

[bitcoin-dev] Bitcoin Core 0.15.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version *0.15.1* is now available from: or Or through bittorrent: magnet:?xt=urn:btih:e83dfdfca54def4e29f5355e8c3f9a7aa45ecbaf&

[bitcoin-dev] Bitcoin Core 0.15.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version *0.15.0* is now available from: and Or through bittorrent: magnet:?xt=urn:btih:e17a5823dd84fe5100386c69e91bc0671e4b4e

[bitcoin-dev] Bitcoin Core 0.14.2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.14.2 is now available from: Or by torrent: magnet:?xt=urn:btih:b4fc7820df95b8b39603ad246c241272ec403619&dn=bitcoin-core-0.14.2&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A8

[bitcoin-dev] Bitcoin Core 0.14.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.14.1 is now available from: Or, by torrent: magnet:?xt=urn:btih:0482be8fc8e1c0b02162871e3591efc3d1d34585&dn=bitcoin-core-0.14.1&tr=udp%3A%2F%2Fpublic.popcorn-tracker.org%3A

[bitcoin-dev] Bitcoin Core 0.14.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.14.0 is now available from: Or from the torrent, magnet:?xt=urn:btih:2dbf4181022baa0629f9313787d0a4294e6acac4&dn=bitcoin-core-0.14.0&tr=udp%3A%2F%2Ftracker.openbittorrent

[bitcoin-dev] Bitcoin Core 0.13.2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.13.2 is now available from: Or by bittorrent: magnet:?xt=urn:btih:746697d03db3ff531158b1133bab5d1e4cef4e5a&dn=bitcoin-core-0.13.2&tr=udp%3A%2F%2Ftracker.openbittorrent.com%

[bitcoin-dev] Bitcoin Core 0.13.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.13.1 is now available from: Or through bittorrent: magnet:?xt=urn:btih:dbe48c446b1113890644bbef03e361269f69c49a&dn=bitcoin-core-0.13.1&tr=udp%3A%2F%2Ftracker.openbittorrent

Re: [bitcoin-dev] Completing the retirement of the alert system

On Sat, Sep 10, 2016 at 12:42:30AM +, Gregory Maxwell via bitcoin-dev wrote: > The alert system was a centralized facility to allow trusted parties > to send messages to be displayed in wallet software (and, very early > on, actually remotely trigger the software to stop transacting). > > It h

[bitcoin-dev] Bitcoin Core 0.13.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.13.0 is now available from: Or through bittorrent: magnet:?xt=urn:btih:35367ed2db6c41f7af9c1ed2dd54ae29d99bc632&dn=bitcoin-core-0.13.0&tr=udp%3A%2F%2Ftracker.openbittorrent

[bitcoin-dev] Bitcoin Core 0.13.0 release candidate 3 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.13.0rc3 are available from: https://bitcoin.org/bin/bitcoin-core-0.13.0/test.rc3/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.13.0rc3 This is a rel

[bitcoin-dev] Bitcoin Core 0.13.0 release candidate 2 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.13.0rc2 are available from: https://bitcoin.org/bin/bitcoin-core-0.13.0/test.rc2/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.13.0rc2 This is a rel

[bitcoin-dev] Bitcoin Core 0.13.0 release candidate 1 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.13.0rc1 are available from: https://bitcoin.org/bin/bitcoin-core-0.13.0/test.rc1/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.13.0rc1 This is a rel

[bitcoin-dev] Bitcoin Core 0.12.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.12.1 is now available from: Or through bittorrent: magnet:?xt=urn:btih:25c4df2a822e840e972a50a31095632d87efadab&dn=bitcoin-core-0.12.1&tr=udp%3A%2F%2Ftracker.openbittorrent

Re: [bitcoin-dev] Bitcoin Core 0.12.1 release candidate 1 available

That's rc2, not rc1 (thanks btcdrak for noticing). rc1 was DOA - see meeting minutes from Thursday. Link for the tag: https://github.com/bitcoin/bitcoin/tree/v0.12.1rc2 The other links and downloads are correct. Wladimir On Mon, Apr 11, 2016 at 09:37:06AM +0200, Wladimir J. van der Laan wrote:

[bitcoin-dev] Bitcoin Core 0.12.1 release candidate 1 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.12.1rc1 are available from: https://bitcoin.org/bin/bitcoin-core-0.12.1/test.rc2/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.12.1rc1 This is a rel

Re: [bitcoin-dev] Proposed release schedule 0.13.0

On Mon, Mar 14, 2016 at 12:18:33PM +0100, Wladimir J. van der Laan wrote: > Proposed release schedule for 0.13.0: > > 2015-05-01 > 2015-05-15 Obviously these are 2016, not 2015. More active tracking here: https://github.com/bitcoin/bitcoin/issues/7679 https://github.com/bitcoin/bitcoin/milestone

[bitcoin-dev] Proposed release schedule 0.13.0

Proposed release schedule for 0.13.0: 2015-05-01 --- - Open Transifex translations for 0.13 - Soft translation string freeze (no large or unnecessary string changes until release) - Finalize and close translations for 0.11 2015-05-15 --- - Feature freeze (bug fixes only until rel

[bitcoin-dev] IRC meetings moved to #bitcoin-core-dev

It seems that MeetingBot was deactivated in #bitcoin-dev, so the last two weeks the weekly developer meeting (Thursday 19:00-20:00 UTC) was held in #bitcoin-core-dev. Let's keep it at that. Wladimir ___ bitcoin-dev mailing list bitcoin-dev@lists.linux

[bitcoin-dev] Bitcoin Core 0.12.0 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.12.0 is now available from: Or through bittorrent: magnet:?xt=urn:btih:e6c0cd47cce75e53b04c1c575a39d2022612d1d6&dn=bitcoin-core-0.12.0&tr=udp%3A%2F%2Ftracker.openbittorren

[bitcoin-dev] Bitcoin Core 0.12.0 release candidate 5 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.12.0rc5 are available from: https://bitcoin.org/bin/bitcoin-core-0.12.0/test/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.12.0rc5 This is a release

[bitcoin-dev] Bitcoin Core 0.12.0 release candidate 3 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.12.0rc3 are available from: https://bitcoin.org/bin/bitcoin-core-0.12.0/test/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.12.0rc3 This is a release

Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available

> > To enable block pruning set prune= on the command line or in > > bitcoin.conf, where N is the number of MiB to allot for raw block & undo > > data. > > From having read the Bitcoin whitepaper quite a few months ago ago, I have > the > very very basic understanding that pruning is meant to:

[bitcoin-dev] Bitcoin Core 0.12.0 release candidate 2 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.12.0rc2 are available from: https://bitcoin.org/bin/bitcoin-core-0.12.0/test/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.12.0rc2 This is a release

Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available

> > So I'm interested whether this limitation has been lifted, and the whole > feature is considered as finished. Yes, it's exactly that limitation that has been lifted! > If yes, I would highly recommend advertising it in the new release notes - as > said, the disk space reduction is a big de

Re: [bitcoin-dev] What is OpenSSL still used for?

> > In the release notes for 0.12, it says that we have moved from > > using OpenSSL to libsecp256k1 for signature validation. So what > > else is it being used for that we need to keep it as a dependency? > > Openssl was dropped from the consensus layer (ECC) in 0.12, though, it > still used for.

Re: [bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available

On Sun, Jan 17, 2016 at 11:57:28PM +0100, xor--- via bitcoin-dev wrote: > On Sunday, January 17, 2016 11:08:08 AM Wladimir J. van der Laan via bitcoin- > dev wrote: > > Preliminary release notes for the release can be found here: > > > > https://github.com/bitco

[bitcoin-dev] Bitcoin Core 0.12.0 release candidate 1 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.12.0rc1 are available from: https://bitcoin.org/bin/bitcoin-core-0.12.0/test/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.12.0rc1 This is a release

[bitcoin-dev] Weekly developer meetings over holidays

Next two weekly developer meetings would fall on: - Thursday December 24th - Thursday December 31th In my timezone they're xmas eve and new year's eve respectively, so at least I won't be there, and I'm sure they're inconvenient for most people. So: let's have a two week hiatus, and continue Ja

Re: [bitcoin-dev] Capacity increases for the Bitcoin system.

On Mon, Dec 07, 2015 at 10:02:17PM +, Gregory Maxwell via bitcoin-dev wrote: > The Scaling Bitcoin Workshop in HK is just wrapping up. Many fascinating > proposals were presented. I think this would be a good time to share my > view of the near term arc for capacity increases in the Bitcoin sys

Re: [bitcoin-dev] Bitcoin Core 0.11.2 released

the new message was genuine. Maybe Wladimir made an > edit after the signature was attached. Or maybe it got changed when it > went through the email system. It would be nice to know. Anyway, I fell > back on Windows security and ran the install because it said it verified > that the

[bitcoin-dev] Bitcoin Core 0.11.2 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.11.2 is now available from: Alternatively, through bittorrent: magnet:?xt=urn:btih:d6d3387160f7e14f6f27dc40ae84cf566ebf631b&dn=bitcoin-core-0.11.2&tr=udp%3A%2F%2Ftracker.

[bitcoin-dev] Announcing Jonas Schnelli as GUI maintainer

Hello, I'd like to announce Jonas Schnelli as the new GUI maintainer of Bitcoin Core. He's been very active in this area for the last year, as one example he redesigned all the icons for 0.11.0, has visualized various network statistics, and has been continuously improving the user experience. So

[bitcoin-dev] Bitcoin Core 0.10.4 release candidate 1 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.10.4rc1 are now available from: https://bitcoin.org/bin/bitcoin-core-0.10.4/test/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.10.4rc1 This is a new

[bitcoin-dev] Bitcoin Core 0.11.2 release candidate 1 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Binaries for bitcoin Core version 0.11.2rc1 are now available from: https://bitcoin.org/bin/bitcoin-core-0.11.2/test/ Source code can be found on github under the signed tag https://github.com/bitcoin/bitcoin/tree/v0.11.2rc1 This is a new

[bitcoin-dev] Bitcoin Core 0.10.3 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.10.3 is now available from: This is a new minor version release, bringing security fixes and translation updates. Please report bugs using the issue tracker at github:

[bitcoin-dev] Bitcoin Core 0.11.1 released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.11.1 is now available from: This is a new minor version release, bringing security fixes. It is recommended to upgrade to this version as soon as possible. Torrent magnet link

Re: [bitcoin-dev] Memory leaks?

On Tue, Oct 13, 2015 at 02:56:08PM -0700, Jonathan Toomim (Toomim Bros) via bitcoin-dev wrote: > I just noticed that several of my running bitcoind processes were using > around 3+ GB of RAM, even though the mempool itself seemed to be under > control. > > @prime:~/bin$ ./bitcoin-cli getmem

Re: [bitcoin-dev] Bitcoin Core 0.11.1 release candidate 2 available

Bitcoin Core 0.11.1 and 0.10.3 final have been tagged, please start your gitian builds, Wladimir ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

[bitcoin-dev] ALERT: Vulnerability in UPnP library used by Bitcoin Core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 TL;DR disable UPnP in Bitcoin Core as soon as possible, if you still have it enabled. Upgrading to 0.11.1rc2 or 0.10.3rc2 will also solve the issue, as they bundle a newer libupnpc (as well as disable upnp usage by default.) However these versio

[bitcoin-dev] Bitcoin Core 0.10.3 release candidate 2 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.10.3 release candidate 2 is now available from: (release candidate 1 never had binaries available) This is a release candidate for a new minor version release, bringing s

[bitcoin-dev] Bitcoin Core 0.11.1 release candidate 2 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Bitcoin Core version 0.11.1 release candidate 2 is now available from: This is a release candidate for a new minor version release, bringing security fixes. (release candidate 1 was never release

Re: [bitcoin-dev] Fwd: Bitcoin Core 0.12.0 release schedule

On Thu, Oct 01, 2015 at 12:10:45PM +0200, Marcel Jamin wrote: > I think the question has already been answered for you by the companies > that build on top of it, the investments being made and the $3.5 billion > market cap. The 1.0.0 tag is probably long overdue. May I remind you that by far, mos

Re: [bitcoin-dev] Fwd: Bitcoin Core 0.12.0 release schedule

On Thu, Oct 01, 2015 at 11:41:25AM +0200, Marcel Jamin wrote: > I guess the question then becomes why bitcoin still is <1.0.0 I'll interpret the question as "why is the Bitcoin Core software still <1.0.0". Bitcoin the currency doesn't have a version, the block/transaction versions are at v3/v1 r

Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule

On Wed, Sep 30, 2015 at 05:57:42PM +, Luke Dashjr wrote: > On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via > bitcoin-dev wrote: > > 2015-12-01 > > --- > > - Feature freeze > > Where is "Consensus freeze"? Shou

Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY!

On Sun, Sep 27, 2015 at 02:50:31PM -0400, Peter Todd via bitcoin-dev wrote: > It's time to deploy BIP65 CHECKLOCKTIMEVERIFY. There appears to be common agreement on that. The only source of some controversy is how to deploy: versionbits versus IsSuperMajority. I think the versionbits proposal sh

Re: [bitcoin-dev] 2015-09-24 #bitcoin-dev Weekly Development Meeting Minutes

Hello Daniel, On Thu, Sep 24, 2015 at 05:29:02PM -0700, Daniel Stadulis via bitcoin-dev wrote: > If you weren't able to attend the first, weekly development meeting, the > following are the minutes: Thanks for writing up the meeting minutes and posting them to the list! We should probably put th

[bitcoin-dev] Bitcoin Core 0.12.0 release schedule

Hello all, The next major release of Bitcoin Core, 0.12.0 is planned for the end of the year. Let's propose a more detailed schedule: 2015-11-01 --- - Open Transifex translations for 0.12 - Soft translation string freeze (no large or unnecessary changes) - Finalize and close translation

[bitcoin-dev] Weekly development meetings on IRC: schedule

Hello, There was overwhelming response that weekly IRC meetings are a good thing. Thanks to the doodle site we were able to select a time slot that everyone (that voted) is available: Thursday 19:00-20:00 UTC, every week, starting September 24 (next Thursday) I created a shared Google Cale

Re: [bitcoin-dev] Weekly development meetings on IRC

On Mon, Sep 21, 2015 at 03:51:29PM +0200, gb wrote: > > Although the planning for this a bit far along now, one consideration I > might add from experience on working with other transglobal IT projects Nah, we can always change the scheduling later... But let's first try it out with one time. W

Re: [bitcoin-dev] Weekly development meetings on IRC

On Fri, Sep 18, 2015 at 03:07:10AM +0200, Wladimir J. van der Laan wrote: > Hello, > > At Monday's code sprint we had a good idea to schedule a regular developer > meeting in #bitcoin-dev. > > Attendance is of course voluntary, but it may be good to have a time that > many people are expected t

[bitcoin-dev] Weekly development meetings on IRC

Hello, At Monday's code sprint we had a good idea to schedule a regular developer meeting in #bitcoin-dev. Attendance is of course voluntary, but it may be good to have a time that many people are expected to be present and current issues can be discussed. Any preference for days/times? What

Re: [bitcoin-dev] libconsensus and bitcoin development process

On Wed, Sep 16, 2015 at 06:29:28PM -0400, Peter Todd via bitcoin-dev wrote: > I've run into a number of cases where companies were maintaining forks > of Bitcoin Core unnecessarily, where a different, loosely coupled, > architecture could do what they needed to do without including the new > logic

Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft

On Tue, Sep 01, 2015 at 02:30:17PM +0100, Ahmed Zsales via bitcoin-dev wrote: > Hello, > > We believe the network requires a block chain licence to supplement the > existing MIT Licence which we believe only covers the core reference client > software. As long as it's an open system, one can't re

Re: [bitcoin-dev] Your Gmaxwell exchange

On Mon, Aug 31, 2015 at 01:55:43PM -0500, Justus Ranvier via bitcoin-dev wrote: > * They should own their bitcoins, meaning that they retain exclusive > control over their balances. Even more precisely, the network must > always honour the conditions of the scripts associated with unspent outputs.

Re: [bitcoin-dev] push tx fuzzing

On Tue, Sep 01, 2015 at 04:59:15PM +, Monarch via bitcoin-dev wrote: > which uses Bitcoin Core for validation. If they aren't validating > transactions before broadcast they won't make it more than a single > hop through the P2P the network so they are of minimum concern. blockchain.info had

Re: [bitcoin-dev] Censorship

On Fri, Aug 21, 2015 at 01:03:33PM -0500, sisadm101--- via bitcoin-dev wrote: > is from a one sided point of view? There doesn't seem to be a solution at > this time, but I find it dissapointing that many (in this very email list) Please, this has drifted so far from the goal of this list: bitcoi

Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP

On Mon, Aug 24, 2015 at 06:15:39PM +, Eric Lombrozo via bitcoin-dev wrote: > It would be very useful to not only be able to switch filtering on and off > globally...but to be able to switch on a per-connection basis. But then You don't necessarily need to send everyone the same nServices bits.

Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP

On Mon, Aug 24, 2015 at 05:37:51PM +, Matt Corallo wrote: > Its more of a statement of "in the future, we expect things to happen > which would make this an interesting thing to do, so we state here that > it is not against spec to do so". Could reword it as "NODE_BLOOM is > distinct from NODE_

Re: [bitcoin-dev] Revisiting NODE_BLOOM: Proposed BIP

> NODE_BLOOM is distinct from NODE_NETWORK, and it is legal to advertise > NODE_BLOOM but not NODE_NETWORK (eg for nodes running in pruned mode > which, nonetheless, provide filtered access to the data which they do have). But is this useful without having decided on a way to signal which blocks

Re: [bitcoin-dev] Libconsensus separated repository (was Bitcoin Core and hard forks)

On Mon, Jul 27, 2015 at 11:40:42PM -0700, Eric Voskuil via bitcoin-dev wrote: > It's a performance sacrifice, and then there's the OpenSSL dependency, > but these are both optional within our stack - so the application > developer has the option. So the only downside is that we are > maintaining t

Re: [bitcoin-dev] Libconsensus separated repository (was Bitcoin Core and hard forks)

On Thu, Jul 23, 2015 at 04:30:06PM +0200, Jorge Timón via bitcoin-dev wrote: > I think there were some misunderstandings in our previous conversation > about this topic. > I completely agree with having a separated repository for libconsensus > (that's the whole point, alternative implementations

Re: [bitcoin-dev] Bitcoin Core and hard forks

Eric Voskuil, Alice Larson, others: Personal attacks or bullying of any kind are not tolerated on this mailing list. This list is meant to be a low-volume community for technical proposals and discussion regarding Bitcoin. See the archive for say, 2012, for example. What Peter Todd or anyone el