tmsr - Search: 168000

a111: Logged on 2018-10-24 18:37 asciilifeform: current flagship trb cannot be replayed 'from genesis', but can be from 168000, per http://btcbase.org/patches/genesis#L3542 .

asciilifeform: current flagship trb cannot be replayed 'from genesis', but can be from 168000, per http://btcbase.org/patches/genesis#L3542 . ☟︎

a111: Logged on 2017-08-06 03:01 asciilifeform: wedge at 168000 apparently.

mircea_popescu: anyway, let's see some details. main chain block 168000 is 000000000000099e61ea72015e79632f216fe6cb33d7899acb35b75c8303b763 mined 2012-2-22 at 21:31 ; size 7.1kb

a111: 30 results for "168000", http://btcbase.org/log-search?q=168000

mircea_popescu: i don't specifically recall 168000-168002 being a heavy load in that sense

a111: Logged on 2017-08-06 03:43 phf: you replay to 167998, you then let it run till 168000 on the network. if it doesn't wedge with that setup, than you have two possibilities. it is either a heisenbug, or you need to replay to an earlier block, say 167000 and let that run on the wild network, etc.

mod6: SetBestChain: new best=000000000000099e61ea height=168000 work=243835201642261706754

a111: Logged on 2015-07-08 16:36 mod6: <+gernika> mod6 I've attempted syncing on OpenBSD again and am now past block 168000 and have reached 185126. It's going very very slowly though. << good to hear though

mod6: <+asciilifeform> mod6, phf didja see 168kisms on openbsd? << not me, but others did, see: <+BingoBoingo> http://btcbase.org/log-search?q=168000

phf: you replay to 167998, you then let it run till 168000 on the network. if it doesn't wedge with that setup, than you have two possibilities. it is either a heisenbug, or you need to replay to an earlier block, say 167000 and let that run on the wild network, etc. ☟︎

phf: if it consistently wedges at 168000 across various machines and settings then it's not a question of wild sewage

assbot: [MPEX] [S.MPOE] 168000 @ 0.0005599 = 94.0632 BTC [-] {4}

mod6: <+guruvan> mod6: that image I made last night isn't working - there's a fork at block 168000 that it's not liking << yeah this is the original v0.5.3 right?

guruvan: asciilifeform: working on a trb docker image - looks like was 168000 p2sh ?

guruvan: mod6: that image I made last night isn't working - there's a fork at block 168000 that it's not liking

assbot: [MPEX] [S.MPOE] 168000 @ 0.00049381 = 82.9601 BTC [+] {6}

mod6: <+gernika> mod6 I've attempted syncing on OpenBSD again and am now past block 168000 and have reached 185126. It's going very very slowly though. << good to hear though ☟︎

gernika: mod6 I've attempted syncing on OpenBSD again and am now past block 168000 and have reached 185126. It's going very very slowly though.

gernika: mod6 I can dumpblock 168000, but not 168001. 168000 is available here: http://exusiae.kicks-ass.net/bsdwedge.bin. I'll share it differently if you'd rather I sign it and post it to the mailing list or anywhere else.

mod6: <+gernika> mod6 stator with mods for OpenBSD. Blockheight=168000 << if it's a problem in block 168`001, i'm sure we hit this problem in february. but it should be resolved with openssl 1.0.1g.

gernika: mod6 stator with mods for OpenBSD. Blockheight=168000

BingoBoingo: thestringpuller: Original block 168000 fork no one knew about

punkman: (I'll mention again that if you let VerifySignature run on all tx's, it blows up much sooner than block 168000)

punkman: debug.log snippet for my node stuck on 168000: http://dpaste.com/3SS8V6X.txt

punkman: I setup a 0.5.3.1 node yesterday, stuck on 168000 today

mod6: <+asciilifeform> mod6: not once have i seen the wedge at 168000 << us either, until 72 hours ago

mircea_popescu: mod6 i didn't see a 168000 exactly freeze either, ever

asciilifeform: mod6: not once have i seen the wedge at 168000