Re: [bitcoin-dev] [Bitcoin-development] Reusable payment codes

On 22/10/15 20:22, Peter Todd wrote: > FWIW multi-push OP_RETURN outputs will be standard in v0.12.0: > > https://github.com/bitcoin/bitcoin/pull/6424 > As I said before, once the prerequisites for a better notification method are usable in the network, I'd love to define a version 2 payment

Re: [bitcoin-dev] [patch] Switching Bitcoin Core to sqlite db

On Thursday 22 Oct 2015 17:26:42 Jeff Garzik via bitcoin-dev wrote: > It was noted that leveldb is unmaintained, and this is part of researching > alternatives that are maintained and reliable. Apart from it being unmaintained, any links to what are problems with levelDB?

Re: [bitcoin-dev] Mailing List Moderation Now Active.

> > - Posts must concern the near-term development of the bitcoin core > code or bitcoin protocol. > Are block size discussions considered acceptable, then? ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org

Re: [bitcoin-dev] Memory leaks?

Btc Drak via bitcoin-dev writes: > I think this thread has gotten to the stage where it should be moved > to an issue on Github and not continue to CC the bitcoin-dev list (or > any other list tbh). Agreed. I couldn't see an issue, so I've opened one.

Re: [bitcoin-dev] [patch] Switching Bitcoin Core to sqlite db

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Here is the beginnings of an implementation to replace leveldb > with sqlite: https://github.com/jgarzik/bitcoin/tree/2015_sqlite > > It builds, but still needs work before passing tests. Nice work! Although not sure if we should focus directly