Maybe for Bitcoin and all other Proof of Work coins: Would it be possible to somehow limit the hashrate the network accepts from a node? Like what if you limit the hashrate per node down to what a normal desktop CPU can do. This would cause all ASICs become irrelevant and/or increase the effort to set up huge mining farms as these, that generate thousand and million times the hashrate of a CPU, would need to run as many nodes as their hashrate is above the abilities of a standard desktop CPU. It would also stop the need to create new algorithms that are ASIC-resistant just to be cracked a few years later.

Ich habe hier eine Wallet die ist 4 Jahre alt. ca 600 Euro wert an Altcoins.

Habe es fertig gebracht, die Coins zu rund 0.04 BTC zu machen.

Kurze Frage: Wenn ich einen Altcoin verkaufen will, für den es kein Euro Pair gibt, muss ich über Bitcoin, Litecoin, ETH gehen. Aber in diesem Moment habe ich die Bitcoins ja gerade erst ein paar Minuten, wenn ich meine Altcoins auscashen will.

Gilt diese Haltefrist von 1 Jahr also für die Altcoins und überträgt sich auf die BTC, die ich dafür erhalten habe oder verlischt das, wenn ich das über Bitcoins auszahle, so dass ich die BTC noch einmal für 1 Jahr liegen lassen müsste?

Honestly, why is compiling Bitcoin still such a pain in the ass?

It still uses the old freaking BerkeleyDB.4.8 and the internet is full of people having issues to compile this thing because of these freaking damn libraries. Literally every freaking bitcoin client and altcoin has this problem

It's 2017 guys why on earth can't we just use a DB library thats included in ACTUAL MODERN SYSTEM repositories?

Yes I downloaded that old version from Oracle.-
Yes I compiled it
Yes I installed it
YES I FREAKING TRIED TO CONFIGURE IT WITH THE LIB PATH
 ./configure CPPFLAGS="-I/usr/local/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib"

NO IT STILL DOESNT RUN

FFS

Berkeley DB is at version 6.2.32