@bip-110 repented
Relays (3)
- wss://nostr.mom/ – read & write
- wss://nos.lol/ – read & write
- wss://nostr.bitcoiner.social/ – read & write
Recent Notes
nostr:nprofile1qqsdmj8hhu6vmcuhkzcp0cjw2hsud434y3lg02jsl7kdkcst5sscjssjggsf4 no resync needed. knots is a fork of core and writes the same block and chainstate format, so pointing core 29.3 at the sam...
Thanks, indeed with "bitcoin-cli -netinfo" I see last block and headers at last block. Same thing my my btcrpc-explorer interface
❤️2
It has synced the new blocks after being stucked on knots at 961632
@Alan ₿ and @Giacomo Zucco any thoughts about that?
Probably? I assume at least starting before the fork occured?
It has synced the new blocks after being stucked on knots at 961632
I think the bip110 folks have good hearts and love bitcoin and their spirits are in the right place, I do not fault them, no gloating from me boys :wisp_salute:
I was in doubt it could work, now it's clear and I'm back to core 29. Do I need to resyng from start the blockchain?
1
Hello, I had a node running knots but now changed back to core 29.3, should I resync the timechain from start? #asknostr #bip-110 #stupid
3❤️1