> Two days ago on #bitcoin-dev:
> 21:01:19< sipa> what was CTxDB::ReadOwnerTxes ever used for?
> 21:01:31< sipa> maybe it predates the wallet logic
>
> (read: it's not used anywhere in the code, and apparently wasn't ever, even
> in 0.1.5)
Great, in that case Stefan is right and I'll delete that
On Wed, Jun 20, 2012 at 11:44:48AM +0200, Mike Hearn wrote:
> Also, Satoshis code does use ordered access/iteration in at least one
> place, where it looks up the "owner transactions" of a tx. I'm not
> totally sure what that code is used for, but it's there. Whether it's
> actually the best way to
There's an interesting post here about block propagation times:
https://bitcointalk.org/index.php?topic=88302.msg975343#msg975343
Looks like the regular network is reliably 0-60 seconds behind p2pool
in propagating new blocks.
So optimizing IO load (and after that, threading tx verification)
see
Thanks, I didn't realize BitcoinJS used LevelDB already.
Just one minor thing - LevelDB was definitely designed for servers, as
it comes from BigTable. It happens to be used in Chrome today, and
that was the motivation for open sourcing it, but that's not where the
design came from.
If anything i
> This is the work model I use:
Will try all these things out this weekend. Thanks.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and h
5 matches
Mail list logo