[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

adii Stepanov - - João Barbosa - - Luke Dashjr - - MarcoFalke - - MIZUTA Takeshi - - Pieter Wuille - - Russell Yanofsky - - sachinkm77 - - Samuel Dobson - - Wladimir J. van der Laan As well as to everyone that helped with translations on [Transifex](https://www.transifex.com/bitcoin/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

hanks to everyone who directly contributed to this release: - - Aaron Clauson - - Adam Jonas - - Andrew Chow - - Fabian Jahr - - fanquake - - Gregory Sanders - - Harris - - Hennadii Stepanov - - Jan Beich - - Jim Posen - - João Barbosa - - Karl-Johan Alm - - Luke Dashjr - - MarcoFalke - - Michael Chr

[bitcoin-dev] Bitcoin Core 0.18.1 released

- Luke Dashjr - - MarcoFalke - - MeshCollider - - Pieter Wuille - - shannon1916 - - tecnovert - - Wladimir J. van der Laan As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/). -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHk

[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: N

[bitcoin-dev] Bitcoin Core 0.17.1 released

ivner - - fanquake - - fridokus - - Glenn Willen - - Gregory Sanders - - gustavonalle - - John Newbery - - Jon Layton - - Jonas Schnelli - - João Barbosa - - Kaz Wesley - - Kvaciral - - Luke Dashjr - - MarcoFalke - - MeshCollider - - Pieter Wuille - - practicalswift - - Russell Yanofsky - - Sjors

[bitcoin-dev] Bitcoin Core 0.17.0.1 released

Pieter Wuille - - Sjors Provoost - - Wladimir J. van der Laan -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAlvYRjgACgkQHkrtYphs 0l1Gigf/dRF0wlT/Ht3hkRs4vo4FqBy6fNeTbn0G20uiK/L0XYdj9fDoVrbzuDHX 1cszwwUyj3E/wLredII3sEIaMN3ttc

[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

=== Thanks to everyone who directly contributed to this release: - - fanquake - - Jonas Schnelli - - Luke Dashjr - - Matt Corallo - - MeshCollider - - Russell Yanofsky - - Suhas Daftuar - - Wladimir J. van der Laan And to those that reported security issues: - - awemany (for CVE-2018-17144, previ

[bitcoin-dev] Bitcoin Core 0.14.3 released

lli - - Gregory Maxwell - - Karl-Johan Alm - - Luke Dashjr - - MarcoFalke - - Matt Corallo - - Mikerah - - Pieter Wuille - - practicalswift - - Suhas Daftuar - - Thomas Snider - - Tjps - - Wladimir J. van der Laan And to those that reported security issues: - - awemany (for CVE-2018-17144, previousl

[bitcoin-dev] Bitcoin Core 0.16.3 released

tcoinconsensus_err` (afk11) ### Documentation - - #13844 `11b9dbb` correct the help output for -prune (hebasto) Credits === Thanks to everyone who directly contributed to this release: - - Anthony Towns - - Hennadii Stepanov - - Matt Corallo - - Suhas Daftuar - - Thomas Kerin - - Wladimir J. van

[bitcoin-dev] Bitcoin Core 0.16.2 released

oemphilips - - John Newbery - - Kristaps Kaupe - - lmanners - - Luke Dashjr - - MarcoFalke - - Matt Corallo - - Pieter Wuille - - practicalswift - - Sjors Provoost - - Suhas Daftuar - - Wladimir J. van der Laan And to those that reported security issues: - - Braydon Fuller - - Himanshu Mehta

[bitcoin-dev] Bitcoin Core 0.16.1 released

nd - - Jesse Cohen - - John Newbery - - Johnson Lau - - Karl-Johan Alm - - Luke Dashjr - - MarcoFalke - - Matt Corallo - - Pieter Wuille - - Suhas Daftuar - - Tamas Blummer - - Wladimir J. van der Laan As well as everyone that helped translating on [Transifex](https://www.transifex.com/pro

[bitcoin-dev] Bitcoin Core 0.16.0 released

- Paul Berg - - Pedro Branco - - Pierre Rochard - - Pieter Wuille - - practicalswift - - Randolf Richardson - - Russell Yanofsky - - Samuel Dobson - - Sean Erle Johnson - - Shooter - - Sjors Provoost - - Suhas Daftuar - - Thomas Snider - - Thoragh - - Tim Shimmin - - Tomas van der Wansem -

[bitcoin-dev] Bitcoin Core 0.15.1 released

Berg - - Pedro Branco - - Pieter Wuille - - practicalswift - - Russell Yanofsky - - Samuel Dobson - - Suhas Daftuar - - Tomas van der Wansem - - Wladimir J. van der Laan As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/). -BEGIN PGP S

[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

ry Sanders - - Jonas Schnelli - - Matt Corallo - - Russell Yanofsky - - Shigeya Suzuki - - Wladimir J. van der Laan As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/). -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCgAGBQJZRR

[bitcoin-dev] Bitcoin Core 0.14.1 released

t Corallo - - Pieter Wuille - - practicalswift - - rawodb - - Suhas Daftuar - - Wladimir J. van der Laan As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/). -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCgAGBQJY+1YNAAoJEHSBCwEj

[bitcoin-dev] Bitcoin Core 0.14.0 released

wbs - - Jorge Timón - - Justin Camarena - - Karl-Johan Alm - - Kaz Wesley - - kirit93 - - Koki Takahashi - - Lauda - - leijurv - - lizhi - - Luke Dashjr - - maiiz - - MarcoFalke - - Marijn Stollenga - - Marty Jones - - Masahiko Hyuga - - Matt Corallo - - Matthew King - - matthias - - Micha - - Michael Ford

[bitcoin-dev] Bitcoin Core 0.13.2 released

- - instagibbs - - Ivo van der Sangen - - jnewbery - - Johnson Lau - - Jonas Schnelli - - Luke Dashjr - - maiiz - - MarcoFalke - - Masahiko Hyuga - - Matt Corallo - - matthias - - mrbandrews - - Pavel Janík - - Pieter Wuille - - randy-waterhouse - - Russell Yanofsky - - S. Matthew English - - S

[bitcoin-dev] Bitcoin Core 0.13.1 released

on - - David A. Harding - - Eric Lombrozo - - Ethan Heilman - - fanquake - - Gaurav Rana - - Gregory Maxwell - - instagibbs - - isle2983 - - Jameson Lopp - - Jeremy Rubin - - jnewbery - - Johnson Lau - - Jonas Schnelli - - jonnynewbs - - Justin Camarena - - Kaz Wesley - - leijurv - - Luke Dashjr

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

orallo - - Matthew English - - Matthew Zipkin - - mb300sd - - Mitchell Cash - - mrbandrews - - mruddy - - Murch - - Mustafa - - Nathaniel Mahieu - - Nicolas Dorier - - Patrick Strateman - - Paul Rabahy - - paveljanik - - Pavel Janík - - Pavel Vasin - - Pedro Branco - - Peter Todd - - Ph

[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

as deprecated (btcdrak) - - #7780 `c5f94f6` Disable bad-chain alert (btcdrak) Credits === Thanks to everyone who directly contributed to this release: - - accraze - - Alex Morcos - - BtcDrak - - Jonas Schnelli - - Luke Dashjr - - MarcoFalke - - Mark Friedenbach - - NicolasDorier - - Piete

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

[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/bit

[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

121 `466f0ea` Convert entire source tree from json_spirit to UniValue (Jonas Schnelli) - - #6234 `d38cd47` fix rpcmining/getblocktemplate univalue transition logic error (Jonas Schnelli) - - #6239 `643114f` Don't go through double in AmountFromValue and ValueFromAmount (Wladimir J. van der

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

no critical problems are found, this release candidate will be tagged as 0.12.0. Diff since rc3 (rc4 was DOA): - - #7472 `b2f2b85` rpc: Add WWW-Authenticate header to 401 response (Wladimir J. van der Laan) - - #7469 `9cb31e6` net.h fix spelling: misbeha{b,v}ing (Matt) - - #7482 `e16f5b4` Ensure

[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

27;t make easy (or even possible). So I'd do this: The binary release signing key is signed by my normal key: $ gpg --list-sigs 36C2E964 pub 4096R/36C2E964 2015-06-24 [expires: 2017-02-13] uid Wladimir J. van der Laan (Bitcoin Core binary release sig

[bitcoin-dev] Bitcoin Core 0.11.2 released

- - Alex Morcos - - ฿tcDrak - - Chris Kleeschulte - - Daniel Cousens - - Diego Viola - - Eric Lombrozo - - Esteban Ordano - - Gregory Maxwell - - Luke Dashjr - - Marco Falke - - Mark Friedenbach - - Matt Corallo - - Micha - - Mitchell Cash - - Peter Todd - - Pieter Wuille - - Wladimir J. van der L

[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

who directly contributed to this release: - - Adam Weiss - - Alex Morcos - - Casey Rodarmor - - Cory Fields - - fanquake - - Gregory Maxwell - - Jonas Schnelli - - J Ross Nicoll - - Luke Dashjr - - Pavel Vasin - - Pieter Wuille - - randy-waterhouse - - ฿tcDrak - - Tom Harding - - Veres Lajos - - W

[bitcoin-dev] Bitcoin Core 0.11.1 released

s release: - - Adam Weiss - - Alex Morcos - - Casey Rodarmor - - Cory Fields - - fanquake - - Gregory Maxwell - - Jonas Schnelli - - J Ross Nicoll - - Luke Dashjr - - Pavel Janík - - Pavel Vasin - - Peter Todd - - Pieter Wuille - - randy-waterhouse - - Ross Nicoll - - Suhas Daftuar - - tailsjoin -

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

- J Ross Nicoll - - Luke Dashjr - - Pavel Vasin - - Pieter Wuille - - randy-waterhouse - - ฿tcDrak - - Tom Harding - - Veres Lajos - - Wladimir J. van der Laan And all those who contributed additional code review and/or security research: - - timothy on IRC for reporting the issue - - Vulnera

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

Morcos - - Casey Rodarmor - - Cory Fields - - fanquake - - Gregory Maxwell - - Jonas Schnelli - - J Ross Nicoll - - Pavel Janík - - Pavel Vasin - - Peter Todd - - Pieter Wuille - - randy-waterhouse - - Ross Nicoll - - Suhas Daftuar - - tailsjoin - - ฿tcDrak - - Tom Harding - - Veres Lajos - - Wladimir

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

s a decision to not to. > Yeah, probably not a very important topic right now. Exactly. Wladimir > > > > 2015-10-01 11:56 GMT+02:00 Wladimir J. van der Laan : > > > On Thu, Oct 01, 2015 at 11:41:25AM +0200, Marcel Jamin wrote: > > > I guess the questio

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 >

[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

Re: [bitcoin-dev] Bitcoin Core 0.11.0 released

janik - - Pavel Janík - - Pavel Vasin - - Peter Todd - - Philip Kaufmann - - Pieter Wuille - - pstratem - - randy-waterhouse - - rion - - Rob Van Mieghem - - Ross Nicoll - - Ruben de Vries - - sandakersmann - - Shaul Kfir - - Shawn Wilkinson - - sinetek - - Suhas Daftuar - - svost - - Thomas Zander - -

Re: [bitcoin-dev] Bitcoin Core 0.11.0 released

- - Philip Kaufmann - - Pieter Wuille - - pstratem - - randy-waterhouse - - rion - - Rob Van Mieghem - - Ross Nicoll - - Ruben de Vries - - sandakersmann - - Shaul Kfir - - Shawn Wilkinson - - sinetek - - Suhas Daftuar - - svost - - Thomas Zander - - Tom Harding - - UdjinM6 - - Vitalii Demianets -

[bitcoin-dev] Bitcoin Core 0.11.0 released

ndy-waterhouse - - rion - - Rob Van Mieghem - - Ross Nicoll - - Ruben de Vries - - sandakersmann - - Shaul Kfir - - Shawn Wilkinson - - sinetek - - Suhas Daftuar - - svost - - Thomas Zander - - Tom Harding - - UdjinM6 - - Vitalii Demianets - - Wladimir J. van der Laan And all those who

[bitcoin-dev] Bitcoin core 0.11.0 release candidate 3 available

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I've just uploaded Bitcoin Core 0.11.0rc3 executables to: https://bitcoin.org/bin/bitcoin-core-0.11.0/test/ The source code can be found in the source tarball or in git under the tag 'v0.11.0rc3' Preliminary release notes can be found her

Re: [bitcoin-dev] The need for larger blocks

On Sat, Jun 27, 2015 at 03:50:09PM +0300, NxtChg wrote: > >The *entire network* needs to agree to switch to your new software. > > Why the "entire network"? So if, say, 75% of everybody involved want some > change and 25% don't, the majority can't have it? You can change your client, individuall

Re: [bitcoin-dev] The need for larger blocks

> It was pointed several times before that with enough loud minority you can > make any change seem controversial. Yes, absolutely. Pushing something through despite a loud miniority (certainly a well-informed one with valid reasons) is controversial. This is not about miniorities and majoriti

Re: [bitcoin-dev] The need for larger blocks

Jorge, > Provided they're also uncontroversial, they don't need to be that > different (in terms of deployment) from softforks. Since they risks > are bigger you just need to give more time for users and alternative > software to upgrade. Sure, most extreme: if secp256k1 or SHA256 starts to show

Re: [bitcoin-dev] The need for larger blocks

On Sat, Jun 27, 2015 at 12:55:01PM +0300, NxtChg wrote: > > > They cannot be changed willy-nilly according to needs of some groups, much > > less than lower gravity can be legislated to help the airline industry. > > Except the block size is not gravity. It's more like an arbitrary decision to

Re: [bitcoin-dev] Upcoming DOS vulnerability announcements for Bitcoin Core

On Sat, Jun 27, 2015 at 06:21:03AM +, Gregory Maxwell wrote: > http://sourceforge.net/p/bitcoin/mailman/message/34199290/ New archive link: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/008578.html Wladimir ___ bitcoin-dev maili

Re: [bitcoin-dev] The need for larger blocks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, Jun 26, 2015 at 04:09:18PM +0200, Pieter Wuille wrote: > People say that larger blocks are necessary. In the long term, I agree - in > the sense that systems that do not evolve tend to be replaced by other > systems. This evolution can come

[bitcoin-dev] New GPG signing key for Bitcoin Core binary releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, Starting with 0.11.0rc3, SHA256SUMS.asc will be signed with the following key: pub 4096R/36C2E964 2015-06-24 Wladimir J. van der Laan (Bitcoin Core binary release signing key) Primary key fingerprint: 01EA 5486 DE18 A882 D4C2

Re: [bitcoin-dev] Welcome to the new Bitcoin Dev List

On Mon, Jun 22, 2015 at 08:40:15AM +0200, Jonas Schnelli wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev The > > move is now complete. The previous archive has been fully > > imported and new posts here will now be save

Re: [Bitcoin-dev] Thanks for signing up for Cat Facts!

On Fri, Jun 19, 2015 at 10:25:06AM +0200, Riccardo Spagni wrote: > I think you'll find it's a Schrödinger... Any paper wallets still inside will be in a superposition of recoverable and non-recoverable. > > > > > On Fri, Jun 19, 2015 at 09:55:48AM +0200, Marcel Jamin wrote: > > > You now will r

Re: [Bitcoin-dev] Thanks for signing up for Cat Facts!

On Fri, Jun 19, 2015 at 09:55:48AM +0200, Marcel Jamin wrote: > You now will receive fun daily facts about CATS! >o< Ooh! What's in this box... , ,-. _,---._ __ / \ / ).-' `./ / \ ( ( ,'

Re: [Bitcoin-dev] Test

On Fri, Jun 19, 2015 at 09:29:19AM +0200, Martin Schwarz wrote: > Am 19.06.2015 um 09:21 schrieb Btc Drak: > > On Fri, Jun 19, 2015 at 8:17 AM, Luke Dashjr wrote: > > On Friday, June 19, 2015 6:44:23 AM Cameron Garnham wrote: > > Looking to buy stress pills!? Read no further!

Re: [Bitcoin-dev] Test

On Fri, Jun 19, 2015 at 08:21:34AM +0100, Btc Drak wrote: > On Fri, Jun 19, 2015 at 8:17 AM, Luke Dashjr wrote: > > > On Friday, June 19, 2015 6:44:23 AM Cameron Garnham wrote: > > > Looking to buy stress pills!? Read no further! You have come to the right > > > list! > > > > I have natural solut

Re: [Bitcoin-dev] Test

On Fri, Jun 19, 2015 at 05:52:20AM +, Gregory Maxwell wrote: > UNSUBSCRIBE Look Dave, I can see you're really upset about this. I honestly think you ought to sit down calmly, take a stress pill, and think things over.