🎵 We Call Them Poor🎵
mIX
mix@lowtimepreference.ca
npub1sl5c...nwpw
Supporting a decentralized future of sound money and technology. Study Bitcoin. Become a #noderunner.
GM. Hope you have a good Sunday. ☀️
If anyone is looking at getting a Bitcoin node setup, I would suggest looking at refurbished Dell Optiplex Micro computers. They sell for really cheap now that windows 10 is done and most don't support windows 11. 🤮
You can get them with 8GB RAM and a 250GB SSD for around $200 (CAD) (7050). Throw in a 2 TB NVMe (M.2) drive in it and you're ready to install node software that wants two drives like @mynodebtc or @Umbrel ☂️.
You can install @Start9 as well, but I believe it only supports one drive (dont see an option for a second in my test rig) so everything would go on on the 2 TB drive.
I like the first two options because the OS goes on the smaller drive and all the data (wallet, timechain and lightning channels) goes on the 2 TB drive. If the OS drive blows up, you just reflash the OS drive and continue on (after a small catch-up sync of the timechain).
I prefer the Micro version of the Optiplex, since it barely takes up any space, but there are SFF and desktop size versions as well.
Far superior to running a Pi and about the same price.




#zapathon


hehe


So they want to change op_return so that the UTXO set won't be as effected as much by malformed data.
So the proposed idea is not a solution to fixing the ability to spam UTXOs issue, just makes spammer's job easier so that they maybe won't mess around in the UTXO data. Analogy: It seems this points spammers toward a larger easier front door, but the back door is still open?
Said another way. Trying to keep people from making a mess in UTXO by making it easier to spam in other ways, but in no way does this limit the ABILITY to spam UTXO data.
Am I understanding this correctly or am I missing something?
#bitcoincore #knots #op_return