TL;DR: If a mechanic charges you to fix your car and doesn't, they’re responsible. But in Hive, if a service says it'll swap your token and then can’t, who cops the blame? After the recent Denial of Service (DoS) attack, who should be liable when things go belly up?
Mate, in the real world, if you pay someone to do a job and they botch it, they’ve gotta make it right. Whether it’s a tradie fixing your leaky tap, a mechanic replacing your brakes, or an online store sending your order, there’s an unspoken (and sometimes legal) rule: do what you said you’d do, or make up for it.
But in Hive, and crypto in general, the rules are fuzzier. What happens when a Hive service promises something—like swapping a token—but fails to deliver? Are they responsible? Should they cough up a refund? And when things go pear-shaped due to attacks like the recent DoS incident, who’s to blame?
Let's unpack this.
If you pay a mechanic to fix your car, but it’s still clunking down the road, you’d expect them to either fix it properly or give you your money back. That’s just how things work in a fair deal.
But crypto doesn’t have consumer protection laws like traditional businesses. No Fair Trading, no ACCC breathing down dodgy operators’ necks. Instead, it relies on:
But here’s the kicker: most Hive services aren’t purely on-chain. They operate outside the blockchain layer, which means their obligations become a bit more like real-world businesses.
Take token swap services. If a bridge says, “Send us HBD, and we’ll give you BTC,” but they fail to deliver, that’s not just bad luck—that’s dodgy business.
The big question is: should they be held to the same standard as a regular business?
Not all failures are the same. Let’s break it down:
This is when a Hive service:
That’s like a mechanic charging for new brakes but never installing them. Morally, they’re on the hook.
What if the reason they failed was out of their hands? For example, the Denial of Service (DoS) attack that recently smacked Hive hard.
If a token bridge couldn’t process transactions because the blockchain itself was struggling, is that their fault? Well, not entirely.
But here’s what should happen:
If they don’t? That’s negligence, even if they weren’t the cause of the problem.
The recent DoS attack left plenty of people wondering who should cop the blame when services go down. Let’s look at the key players:
Hive itself isn’t a company—it’s a decentralised blockchain. But its core devs and witnesses do have a moral duty to:
They’re not personally liable, but if they ignored security threats, that’d be on them.
A Hive service (e.g., a token bridge or exchange) might not be able to prevent a DoS attack, but they are responsible for:
If a service just disappears or refuses to help, then yeah, they’re on the hook.
In the crypto world, there’s no safety net. That means:
That doesn’t mean we should just “accept” losses—it means we need to hold services accountable.
The moral standard in Hive should be no different from the real world. If a business takes money (or tokens) and fails to deliver, it is on the hook—whether legally enforceable
