Wait just so I understand the “lesser branches are maintained in an inmemory tree relative to the candidate index and are purged ..”
So: LibBitcoin has one “current chain” called “confirmed chain”, which can grow, and then at a time it’s exploring only one alternative chain at most - that is like, in case of a reorg - and that one is called the “candidate chain”.
So the in-ram tree you are talking about now is for tracking third, fourth etc. chain options - and you’re saying those chain structures are only in RAM, also as they shouldn’t really be of any significant size anyhow?
