pull down to refresh
100 sats \ 0 replies \ @Filiprogrammer 20 May \ parent \ on: What Color is Bitcoin (BTC) ? bitcoin
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.
What makes a UTXO unprunable?
Any non-zero unspent transaction output that is not provably unspendable.
An output script starting with
OP_RETURN is provably unspendable, so it can be pruned.But an output with a fake public key or fake script hash (such as produced by STAMPS) is unspendable, but that's not always obvious. Thus these outputs must be retained in the UTXO set. These are the most harmful ones.
The default mempool policies in Bitcoin Core are effective at preventing OP_RETURN outputs with more than 80 bytes of data.
They are NOT effective at preventing
OP_FALSE OP_IF ... OP_ENDIF (inscriptions) and fake public keys.El Salvador stacking a bitcoin every single day is so cool.
But are they really since the IMF agreement? Or are they just moving Bitcoin around to make it look like they are still stacking?
Oh right, I overlooked that you need BOLT12 support. LND does not have support for that yet. With Core Lightning however you could still use a pruned Bitcoin node or (although not recommended) you could use trustedcoin to immediately grant your Lightning node onchain access through public blockchain explorers.