phf: jurov: the goal is to get bitcoind working with pogo's limited memory. the problem is that a running bitcoind grows in memory use as a result of normal operations. we know that some processes claim a lot of memory by design, like mempool, so first step is to get a reliable way of cleaning out mempool. ascii wrote that patch, but discovered that in practice zapmempool doesn't reduce memory use.

phf: in that case you'd better truncate it doing run too, because if that pogo doesn't go down, there's no cap on the log

phf: should there even be logs on pogo?

phf: ascii_field: you're too sane, to comprehend this madness. the way stupid thinks in this case, "want to sell bitcoin device, can't really make pogo, because no "value add", so must add some hardware to make it seem like useful hardware." of course they don't have enough sense to say add a ecc sig verifier asic, so add probably stolen miner asic code, which is not going to mine anything for anybody, hence the dodgy justification code.