Anyone here running bitcoin knots noticed this message in the logs during verification?
date='2024-01-26T19:18:29Z' progress=0.821011 cache=214.0MiB(1747940txo) warning='Miner violated version bit protocol'
Anything to be concerned of? Can be ignored?
Knots has a stricter opinion of what are good blocks, transactions and other “bits” and pieces of protocol. This is it flagging stuff it didn’t like but can’t do anything about because consensus doesn’t agree/care. Nothing you can do about it either, and isn’t an immediate concern.
Thanks for the reply.
So in this case it doesn’t matter if one is using bitcoin core, since nothing can be done because consensus doesn’t agree/care?
I am just trying to decided one of the two. My other node is running core.
Well with Knots it’s going to download the blocks for sure, it if didn’t you’d be using a different chain that isn’t bitcoin.
What Knots does do is remove any “spam” in transactions in those blocks by flagging it as invalid.
In a sense, its mostly a political statement to run Knots for most people though, mostly.
I’m doing a first sync of my new Start9 node. I did select the option under mempool to reject tokens (runes) and what I’ve noticed now is that it is taking a VERY long time to sync and it really slowed WAY down around the 75% complete mark - much longer to sync than when I’ve done this in the past without rejecting tokens on other implementations of Bitcoin Knots (Umbrel). I assume that’s because it’s having to go through all the txns now with ordinals and runes and remove all that spam and flag it was invalid as you say.
I’m not actually sure if there’d be a performance hit or not. The block validation process is always going through all the transactions, so I honestly doubt it.
It’s been a 19hrs since you posted this, so it’s probably at 100% now… but it would have been interesting to uncheck the option and see what happened.
I don’t remember where it was exactly when I posted that message 21h ago, but it was somewhere around the 78% mark. 21h later its now at something like 81.37%. It also keeps timing out on the sync - but the log file keeps cranking along with new blocks, albeit slowly. I don’t have a particularly fast system - its an AMD Ryzen 5 5500U with 8GB RAM and a 1Tb SSD (Crucial up to 7100Mb/s).
Right now it’s on syncing on block 832247 and saying it’s at 81.37%. I’ll just let it keep running since i’m not in a rush, and will check back tomorrow on progress. But this is definitely REALLY slow to sync and I think it might be because I turned on Reject Tokens… I guess worth it to not have to support runes tho.
The 8GB probably explains it. You’ll be thrashing the SSD pretty hard. When was the last time you synced quickly with this device and 8GB?
I haven’t before… i’ve only run it as a regular laptop before and i’m now repurposing it for the first time in its life as a Bitcoin node. the RAM expansion is pretty cheap, I might just throw some extra in there for good measure…
The Bitcoin UTXO set expanded beyond 8GB some time ago, the last 25% will go slowly. If it can’t hold the entirety in RAM at once. When you get to 100%, it’ll probably be fine.
I ordered another 8GB of DDR4 ram to upgrade this system. Will see how quickly it syncs after I get that installed. But for now, I just compared current progress against yesterday and its syncing on average about 9blocks/m. At this current rate it will take about another 4 days to completely sync.
Newer blocks are much more complex, and will take longer to validate than the older ones. The last time I did an IDB, most of the total time was spent on the last 10%.
got the RAM installed and it made all the difference. syncing sped up at least 4x and node is fully sync’d now!
Thanks for the update. I’ll link here when people refuse to believe me.