this post was submitted on 03 Feb 2024
397 points (94.8% liked)
Technology
59317 readers
5275 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
Bitcoin has literally 2 pools who have more then half of the block production. Also not all PoS systems have locking and slashing btw.
Pools that people could leave if something suspicious was happening.
Very different than an individual entity.
Well... Cardano has like 30 different pools that add up to 50+% of the block production.
If something sus was happening with one or more of those - people can just leave them.
Same thing but 30 is better than 2.
Definitely agree, 2 isn't ideal, and there's some level of trust happening there because of it.
There's been pushes over the years to get people to split apart more, and I'm pretty sure there was a significant split due to this at least once in the past.
It's gotta be either something like reliability, ui/ux, ease of setup, otherwise all I can come up with is a larger pool pays out smaller amounts more consistently and people prefer that?
We in Cardano have a "saturation" limit per pool. So if you have more than like 70M ADA, you don't get rewards for anything above that. This encourages people with a lot of ADA (either theirs or delegated to them) to run multiple pools. We call them multi pool operators. Cardano community has a really strong sentiment against delegating to multi pools. And if you are wondering if that figure I mentioned earlier (30 pools to reach 50+%) is just a few entities with many pools. No - this is actually 30 individual MPOs (multi pool operators).
That's a pretty cool way to address the problem. I originally wrote solution, but that's not really a solution since it could theoretically just be multi pools, but by putting a barrier in place like that to discourage it, it should lessen the problem.