this post was submitted on 12 Jun 2024
19 points (100.0% liked)

Buttcoin

9 readers
2 users here now

Buttcoin is the future of online butts. Buttcoin is a peer-to-peer butt. Peer-to-peer means that no central authority issues new butts or tracks butts.

A community for hurling ordure at cryptocurrency/blockchain dweebs of all sorts. We are only here for debate as long as it amuses us. Meme stocks are also on topic.

founded 11 months ago
MODERATORS
top 5 comments
sorted by: hot top controversial new old
[–] grimsolem@lemmy.dbzer0.com 10 points 5 months ago (1 children)

Impressive they could spend a quarter billion to fail building a new database.

[–] dgerard@awful.systems 8 points 5 months ago

it was really pretty impressive

[–] yellowcake@awful.systems 10 points 5 months ago

In capital markets infrastructure low latency and high throughput are the 2 core design principles of any system. Blockchain manages to violate both; how anyone could have thought this is “the future” is beyond me. I still hear all too often “ya blockchain (or cryptocurrency) doesn’t work now but I’m sure it’ll be great and useful eventually!”

Why oh why are people so attached to this proven failed tech idea? I’ll throw it the smallest of bones and say maybe a distributed ledger with cryptographic proofs has some very specific minor use case, but even if that maybe is true for one thing why is it shoved everywhere it doesn’t belong?

[–] corbin@awful.systems 7 points 5 months ago (1 children)

In enterprise computing, “smart contracts” are called “database triggers” or “stored procedures.” They’re a nightmare, because they’re very hard to reason about or maintain, and they’re prone to unexpected and spooky effects.

It occurs to me that the situation's even more dire than this single-node description. If everything's in one database, then yes, a smart contract is effectively a stored procedure. But it can be worse! Imagine e.g. an MMORPG where city centers or dungeons are disconnected from the regional map to prevent overload. A smart contract might need to synchronize data between two databases, e.g. a dungeon and a surrounding region, to maintain correctness.

[–] dgerard@awful.systems 7 points 5 months ago

yeah, i'm talking about the general case of not separating the code from the data