With the PATCH endpoint the frequency of the chip could be throttled. Maybe that's the way forward. I have to try it out.

Yes, I thought about that as well. However some electronics may be sensitive to frequent power cuts. I do not know how sensitive a Bitaxe is in this concern.

Yeah, but unfortunately there is no stop or start endpoint in here: https://osmu.wiki/bitaxe/api/

Yes, I guess you have to compile the software yourself following these instructions https://github.com/OCEAN-xyz/datum_gateway?tab=readme-ov-file#installation

It's not that complicated.

Gerald Celente defines fascism as “the merger of corporate power with government power”.

So, if cooperation takes over the state or the state takes over cooperations may result in a similar end state.

Given it survives till it is widely deployed and used on daily basis. In the meantime the other debate stays relevant.

As Jeff Booth repeatably said: "If Bitcoin stays decentralized..."

Unfortunately people have a tendency to get lazy, complacent, submissive to authority etc. which can lead them away from the right path. Just like it's told in the Bible over and over again.

Therefore stay vigilant and put in the work.

Yes, the default configuration of Knots is using more resources. The virtual memory grabbed is about factor 4x more than Core.

If you have enough available memory, you may consider to increase dbcache property in bitcoin.conf. That may help

Definitely a catch-22 as Bitcoin is not a democracy. Participating in polls is cheap and running a node is work. So abstain.

What is really the probability that CSAM gets included by any of the large KYC pools?

It seems somehow unlikely that such a block would be constructed by a large pool due to legal risks.

And if it is constructed by some other miner I could imagine that such a block would be orphaned by the other miners.

Yes it happened on the BSV chain, but who care's about that?

Data storage on the chain is undesirable, but this fear about CSAM seems exaggerated.

With datacarriersize=0 you also block out use cases like Bisq etc.

Yes, the resource of Knots seem to be quite higher.

Any suggestion how configuration can be optimized or feedback about minimal hardware requirements would be highly appreciated.

If you only consider the latest versions of both implementation then the share is almost 50% each.

Most node runner (28.1 and earlier) did not yet upgrade or changed implementation.

This hype about treasury companies may pump the price somewhat but actually it is part of the fiat mentality as well.

A lot of energy goes into this type of financial engineering that will also be obsolete when the fiat system finally vanishes.

Is that not a classical example of high time preference and fiat mentality?

Fees may be low now but what is in ten years?

You have to be prepared and not optimized for the short term.

Bitcoin has failed if it is "only Gold 2.0", because then the exchanges like Relai will be the choke points.

If humanity loses the general purpose computing devices on which you can run software without permission, they will try next to force the chip implant on you.

Yes, according to some news article¹ (in German) they will move part of the operation to Germany and Norway.

For the sake of completeness: You can not restore a backup written with an older Coldcard/firmware on a newer device.

But where would they go? Iceland?

I do not understand why smart developers try to figure out how to make transaction even more efficient and on the other hand also enable more spamming?

Are they corrupt aka. having another hidden motive, are they cognitive delusional or are they some kind of neo luddites that want to protect further work as optimizing a dysfunctional UTXO set will be a challenging task that will occupy them for decades.