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.
thnx for asking about 'miner violated, I was also wondering.
I just did a pruned node to get āupā quicker and block spamā¦ ( ābetter moneyā for the People is under attack because it IS BETTER.)
can the pruned blockchain be added to gradually while staying online? I could just up the limit a few MB every now and then i suppose.
Pruning is just discarding old blocks after youāve validated them. It doesnāt get you up and running quicker. It just frees up drive space, by only storing newer blocks. The only way you can avoid the Initial Block Download, is if you already have a fully validated blockchain archive somewhere you can import. Your node canāt function until it has a fully validated blockchain, pruned or not.
OK thnx, well i didnt need to save space so that was silly of me. letās see how long it takes to go unpruned then.
edit: have to reindex, start whole download again