asciilifeform: this -- works. but the hose has TWO ends
asciilifeform: let's say gavin writes a forked client that incorporates the entirety of traditional bitcoin, and keeps both blockchains around, simply to refuse to spend any output that's been already spent somewhere in actual bitcoinland.
asciilifeform: i'm still waiting for something like a coherent explanation of how that's to work.
asciilifeform: 'We will implement replay protection'
asciilifeform: 'Hello asciilifeform I see on coin.dance/nodes , The Real Bitcoin is listed with the 'Emergent Consensus' feature tag. Could you tell me if that's accurate - will you follow a HF to > 1MB , and could you tell me anything about how it's implemented in TRB ? Thx!'☟︎
asciilifeform: the very first block would have to outweigh the cumulative work.
asciilifeform: the other open seekrit re classical trb : and afaik applies equally to various prbs : there is no means whereby to introduce a martian reorg consisting of >1 block, such that it will actually get processed.
asciilifeform: realistically a reorg affects, what, few dozen blocks. and that's if martians land.
asciilifeform: idea being (and currently in 'nqb' asciilifeform is experimenting with the proportions) it is quite stupid to do reorg ops of open-endedly large size.
asciilifeform: ( didn't find deathray hidden under the floor, no. but also ruled out bad drams, so the mystery -- remained )☟︎
asciilifeform: oh it'd seem that i neglected to say why i had the geiger around -- was hunting for a reason why a certain box of mine was ringing ecc alarms
asciilifeform: and military equip. ( compasses, aircraft gauges )
asciilifeform: at one time was ubiquitous, esp for nice watches.
asciilifeform: likewise, phf's ( the linked logtron ) has back-reference links ( when a line is mentioned, you can go from it, to the mentions ) and other conveniences (search, for instance.)
asciilifeform: between phf's logtron, Framedragger's, and ben_vulpes's -- ~100% coverage. unlike, say, your own connection plus the particular fleanode box it may happen to be on.
asciilifeform: folks coming from heathendom, who 'oh i'll lurk', despite being shown the logs, remind me of fresh-off-the-boat emigres from east asia who will come to somebody's house and then insist on trying to balance with their legs on the toilet, 'just like back home'
asciilifeform: my current understanding is that reorg can only fail if there is a catastrophic problem with db☟︎
asciilifeform: !~later tell TomServo you were right, it wasn't the clock, the original log is monotonic ( probably oughta post it publicly ) -- the boojum is a failed reorg, and it is impossible to say why it failed, could be disk rot.