pull down to refresh
0 sats \ 0 replies \ @Filiprogrammer 3 Jun \ parent \ on: Quantum vs Bitcoin: A Visual Breakdown bitcoin
Under the assumption that quantum computers can ever derive the private key from the public key.
On the other hand one could also argue that P2TR is more resistant to brute-force attacks than the hash-based addresses.
The hashing algorithm used in P2PKH, P2WPKH... is RIPEMD160, which produces a 160 bit long hash. In principle, that means many different 256 bit private keys map to the same 160 bit hash (and therefore the same address).
But a Taproot address consists of a 256 bit long compressed public key. That's much harder to brute-force.
Sigh, quantum fearmongering again.
Bitcoin uses elliptic curve cryptography (ECC).Private key k, public key P = k*G.
Yeah, Elliptic Curve Digital Signature Algorithm (ECDSA) to be more specific.
When you spend, your public key is revealed.
That is the case for P2PKH, P2SH, P2WPKH and P2WSH.
P2TR outputs (bc1p...) themselves are already the public key, so for those addresses it does not matter whether you spend or not.
Experts give a 50% chance we’ll see quantum computers that can break ECC by 2030–2035.
Highly doubt it. Right now there is no quantum computer in existence that can even run Shor's algorithm.
More people in Bitcoin results in more places to spend and earn Bitcoin directly.
Bitcoin also promotes saving and disincentivizes wasteful consumerism which is destroying the nature around us.
There is just one thing that slightly triggers me about this Bitaxe board:
The placement of the antenna of the ESP32 ‒ The antenna should be sticking out of the board (preferably at the top) for a better WiFi signal.
The shrinking-pie effect of the shares per block rewards early miners but leaves later miners with barely any reward. I find it hard to believe that miners would rather mine on a "sharechain" with these incentives than mine with a regular pool.
Did this ever have an intended or practical purpose ?
In the early days of Lightning (2018-ish) the network was still small enough for it to be easily visualized on a map. Each node would show up in its respective color on that map.
Here is a snapshot of such a visualizer from January 2018:
http://web.archive.org/web/20180118075741/https://lnmainnet.gaben.win/
We see that taproot (p2tr) is the most common UTXO type (at 34.2%), followed shortly by p2pkh (28.8%) & p2wsh (26.5%).
Should be "...p2pkh (28.8%) & p2wpkh (26.5%)"
Please read my message again
Finding the prime factors of 21 is far from enough for cracking a Bitcoin private key. I can figure out in my head that 3*7 = 21. That's the level quantum computers are on right now. So I am not worried about quantum computers cracking Bitcoin private keys any time soon.
Shor's algorithm in practice can just about find the prime factors of 21. I can do that in my head. Don't need a quantum computer for that.
Here you can see the size of the UTXO set over the past 5 years:
https://statoshi.info/d/000000009/unspent-transaction-output-set?orgId=1&refresh=5s&from=now-5y&to=now
It completely exploded in 2023. No wonder your 8 GB RAM Pi performs poorly on a 11 GB UTXO set.
You could still try increasing the value of
dbcache= in your bitcoin.conf to a number of Megabytes that still fits in your memory. Might improve performance a little.I watched the first season of Classroom of the Elite in 2019. It certainly peaked my interest but back then there was no 2nd season. When the 2nd season was announced in 2022, I got excited but I still did not get around to watching it until this day.
Be careful with Revolut! They froze and eventually banned my account after I used it for P2P trades on Robosats.
I can understand the argument that this change might reduce the pollution of the UTXO set in favor of OP_RETURN, but completely removing the option for the user to easily configure these mempool policies seems a bit extreme.
btw, the "bloat" is currently 11gb. so not a big deal in my opinion as people start to switch from 1tb harddrive to 2tb for storage.
Storage is not the problem. The problem is that the UTXO set no longer fits into memory on low-end systems. Thus slowing down the node since it has to access the disk more often now.