this post was submitted on 03 Feb 2024
398 points (94.8% liked)
Technology
59219 readers
3320 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've love to see more pools, but I just don't think its as big of an issue as it's often made out to be, since they don't actually control the hashpower. The blocks they send to participants are immediately verifiable as real or not, miners don't have to take a pool's word for it and will often have full nodes monitoring the blockchain to make sure any given pool doesn't go over 51% hashpower.
Pools really can't do sus stuff. There are a few things pools could do or try to do:
Censor transactions by refusing to include them in blocks. They are financially incentivized not to do this, since not including a tx in the block means selecting the next least valuable tx in terms of fees. The immediate damage from this is basically nil, the next block will probably be made by a different pool and the tx will go through. So transactions can't get censored, only delayed. But people will notice, and that pool will lose all its hashpower and its means of making money, which is exactly what happened when this scenario happened before. Bitcoin has faced, and beaten back, this exact attack before.
Conspire to perform a 51% attack. They don't just need 51% between each other, they need enough hashpower to roll back previous blocks, which means maintaining 51% for several blocks in a row. One of the primary reasons 51% attacks are not viable is that you need to give that Bitcoin to somebody, get something of value in return, and then un-spend it. They need to transfer you that equivalent amount of value before it gets unspent. Nobody transferring hundreds of millions or billions of dollars worth of value is going to be happy with a one block confirmation. Or even a three block confirmation. Even if they were, what items can you actually transfer that quickly? It's just not viable as an attack method, there is no money to be gained. Pool operators are fallible at the rest of us, if there was a viable way to do a 51% attack, somebody would have done it by now. But it's not.
If a block moves a coin from a to b, that coin can't also the coin that stakes that block. Granted, I am showing some ignorance of Cardano here, but that's how other PoS systems work. And there is usually a "cooldown" of a couple blocks to prevent that coin from staking for a while for security reasons.
I didn't know about cardano's capped supply, you've taught me a few things in this thread. Until the system is actually decentralized and the cardano devs give away the master keys and let the network truly run on its own, I have little interest in it. And based on some cursory reading, centralization of relays and growing chain size are much more of a concern than with Bitcoin. Best of luck to you.