News for hackers. Stuff that matters.
Re:The collapse of the IRON stable coin by ceejayoz on Thursday June 17, 2021 @11:42AM (#27540847)
I think the point is more that if you owe $200M to someone, a court is unlikely to accept "it's irreversibly stuck in a smart contract" as an out.
Re:The collapse of the IRON stable coin by tluyben2 on Thursday June 17, 2021 @12:04PM (#27541138)
I am against smart contracts because we do not know how to write software in that way. I like how they sparked a formal verification Renaissance of sorts but that did not help much either unfortunately (if the premise is wrong, no amount of proof will save you anyway).

However, if you let all parties review the smart contract (the source is on the chain, you can check it) and agree with it's workings and sign a 'human' contract saying you do agree and then it goes wrong, I think it should be an out. We do not have proper ways to sue for misbehaving software (it happens all the time but MSFT is climbing higher and higher): this is easier to verify but we are adults here: if you agree to put money in smart contracts, you should have verified the code. And if you think the code is flawed, do not put money: otherwise do not complain afterwards. It is not that hard.

Re:The collapse of the IRON stable coin by Daishiman on Thursday June 17, 2021 @06:47PM (#27545302)
> but we are adults here: if you agree to put money in smart contracts, you should have verified the code. And if you think the code is flawed, do not put money: otherwise do not complain afterwards. It is not that hard.

That's not how it works. Courts generally operate by ambiguous standard of what reasonable people and reasonable experts can actually do given the state of technology.

No reasonable software engineer can tell you that a piece of code is flawless. I don't think courts will agree on a system that has been shown through evidence to be highly flawed.

Re:The collapse of the IRON stable coin by tluyben2 on Friday June 18, 2021 @03:12AM (#27548090)
Sure, that will depend on the courts and specific case, as it seems it works exactly like this mostly. But if you inspected the code yourself and you put your money in anyway and it is gone, you might find that the court will not do anything at all. And who can you shout at then, the moon? I am saying that smart contracts are a special case: they are small pieces of code, if they have a bug, it usually causes major damage and, if they run on the eth chain etc and no one took public responsibility for deploying it, there is no one to sue. We have no way to write this type of bombs without flaws as you rightly say and because of the irrevocable damage and the lack of defendant in most cases, these contracts should not be used at all.

There are already (many) cases like this, but if I write some software and put it in github, someone else deploys it and people die; that is simply not my fault: it is the deploying person. In normal situations, this is easy to find the defendant here: but on the chain, you won't be able to: anyone can deploy anything and you won't know who it was. So unless you to end open source software, you have no case against anyone.

Re:The collapse of the IRON stable coin by mimixco on Friday June 18, 2021 @08:42AM (#27549693)
This reminds me of the Toyota Prius (and other models') un-commanded acceleration problem. Should car buyers examine Toyota's code, or should they assume that the gas and brake pedals work as expected?

It's not reasonable to expect software users (even other developer users) to understand or audit code in order to be able to use software -- for anything.

Re:The collapse of the IRON stable coin by tluyben2 on Friday June 18, 2021 @12:20PM (#27551953)
Yes, but not in case of smart contracts is the point. Prius it's source is not open and cannot be audited and is, definitely installed by Toyota. So Toyota is responsible. Smart contracts have none of this.

They are open source by definition and no one knows, by definition, who deployed them. It is a very different case.

Re:The collapse of the IRON stable coin by mimixco on Friday June 18, 2021 @12:23PM (#27551981)
The author of the code and/or its publisher are always responsible for software quality, not the users.

The fact that other people could audit the software does not absolve the original authors of the fact that they didn't.

Re:The collapse of the IRON stable coin by tluyben2 on Friday June 18, 2021 @12:28PM (#27552051)
Sigh. If this were the case, all open source is doomed. You are responsible if you deploy/offer it, not if you only wrote it. And the point is, in smart contracts, you will not normally know who deployed it.

If you put on github

Return x>0;

And I deploy this in a production environment that kills people with heart rate over 0, do you have any responsibility? No of course not. I do. You have none.

In short: if you put money into something as smart contracts, the only thing you have, and that is literally the intention of the pundits, is that you check the contracts and trust or not trust them. I do not know how this crosses over to other software that has different properties in this thread. That is not relevant. There is no one to sue or say they did a bad job here: you will not know. That is baked in.

Re:The collapse of the IRON stable coin by mimixco on Friday June 18, 2021 @12:40PM (#27552203)
As a career developer of more than 30 years, I still take the viewpoint that the person who wrote the code and/or approved it (both = developers) are 100% responsible for all bugs.

As I mentioned earlier in this thread, there is no such thing as bug-free software (even for devices that kill people, as you point out), because bug-free software is categorically impossible within comp sci.

Knowing this comes with great responsibility, even more so when dealing with life... or finances. The developers of this software, as is the case with Solidity and smart contracts in general, have foregone this responsibility.

Another egregious failing of all crypto schemes which I'm compelled to point out is that they fail to use any of their enormous profits to actually fix bugs.

When I was mainframe developer at IBM, the company spent millions of dollars (taken from clients, of course) to find and fix bugs. They paid people good money, including yours truly, for that work.

Today's crypto companies have no such ethics. They (Mr. Buterin, I'm looking at you) have no compunctions after profiting windfalls from their software inventions to actually invest in debugging or fix distribution (or even real error reporting) for the customers. Likewise, they ignore all the UI aspects (and problems) that their inventions have birthed.

This is not responsible software development. It leads to problems like IRON and others in the crypto space. As I said, it is the exact opposite of how, historically, important enterprise software development is done.

It's only for selfish reasons (= money hoarding) that crypto projects don't hire the best auditors and coders in the world to fix their code. They can certainly afford them.

Re:The collapse of the IRON stable coin by tluyben2 on Friday June 18, 2021 @12:58PM (#27552399)
Seems we are similar ages: I am 30+ years into commercial dev as well. I started with the Dijkstra school of development (under pupils of Dijkstra which my father is one) and found that this is not helping. I like it but more intellectually than anything else. I went more the Arthur Whitney way of practical computing without waste.

I vehemently disagree that just writing code makes your responsible for it's use. We are so bad at writing good code that all programmers would be living on the streets or in jail. And that is not malice, just how little we understand or underestimate complexity. Which becomes apparent if you indeed try to create some formal proof and give up after 30 pages.

I also believe your last statement does not recognize the vast issue there is with the smart contract world: I am more of the school of Erlang/OTP: just let it crash these days. If you cannot correct a state, we cannot write software for it. No matter the proofs and auditing. If we cannot correct an erroneous state, we are not capable of writing software in that system. And that is smart contracts. Not space craft where we often can upload a patch and steer the other way, not cars where we detect a deviation and correct it. Smart contracts are: if it's done it is irreversible and there are no programmers, provers or auditors who can predict or prevent that. Rollback must exist or this all will go to shit. Which is what will happen.

Edit: I actually do not believe cryptocurrencies have a chance unless there is rollback (something like refunds without merchant consent). I just cannot see what rollback means in this context: I read papers with scifi type of stories how this would work but it does not mesh with cryptocurrency obviously otherwise.

Re:The collapse of the IRON stable coin by mimixco on Friday June 18, 2021 @01:29PM (#27552729)
While we disagree on who is responsible for code, I do think we are saying the same thing about cryptos. If you can't fix software later, you're doomed because it all has problems.

Likewise, humans make mistakes in transactions and if they can't be undone... problems.

EDIT: I should clarify that I don't believe software authors are responsible for use, but rather for bugs.

Re:The collapse of the IRON stable coin by tluyben2 on Friday June 18, 2021 @03:13PM (#27553803)
> Likewise, humans make mistakes in transactions and if they can't be undone... problems

But that is saying everything is shit. I do not disagree but I do live in this world.

> EDIT: I should clarify that I don't believe software authors are responsible for use, but rather for bugs

I got that but what would it look like? In practice? As that seems impossible to me.

Re:The collapse of the IRON stable coin by mimixco on Friday June 18, 2021 @04:36PM (#27554737)
I'm not saying most transactions are wrong, but some are. So transactions may need to be corrected, just like code. And, in practice, they often are.

In practice, software companies take responsibility for bugs in three ways today, based on their business model.

Old line companies like IBM paid millions of dollars for people and tools to find and fix bugs and to distribute the fixes to customers. IBM did not wait for you to tell them you had a bug. Their system could tell you if you had a bug that someone else reported. And IBM would ship you a custom tape which fixed that bug and didn't break the rest of your software. Let's call that The Gold Standard. With money, it's certainly possible.

Option 2 is a company like Red Hat. Unironically, IBM bought Red Hat. The reason that, while open source gives you the option to look at the code, most companies don't really want to do that. In other words, Ford could make a lot more money focusing on making cars than they can by hiring people to find and fix bugs in (free) Linux software. Voila! Red Hat offers bug fixing and finding (and a plethora of other things enterprise customers don't want to setup) for a hefty subscription fee. Red Hat has many service offerings in the $10,000/month+ range. Once again, if you pay people, you can find and fix bugs.

Finally, option 3 is a company like Google. They don't really care if anyone else can get open source software to work. But... and this is a big but... they need it to work for themselves. Having built a very lucrative empire on open source (Android, for example), Google cannot afford to wait for "the community" to find and fix bugs. They must pay people and they must pay them well. And, this they do. So while the free open source isn't directly monetized by Google, it's worth their while to pay to keep it up to date and correct. Other companies like Netflix do the same thing.

So there are three ways you can do it today.

What irks me about projects like Ethereum is that, having all these real world models out there, its founder doesn't seem interested in finding or fixing bugs at all. He is relying on "the community" (we know that doesn't work, see #3) and not spending any of his own money on debugging or fixes. In all the real cases where you want fixes to happen (and you want CI/CD to get them to customers), "you", being the publisher or heavy user of such software, must pay.

That's what I mean about responsibility. It's where the buck stops.

Re:The collapse of the IRON stable coin by tluyben2 on Saturday June 19, 2021 @04:31AM (#27558866)
I think we are in agreement and the implementations that can fullfil so what remains is: how can you find the person or group responsible for fixing or getting sued in blockchain land? I can put some malicious code on the eth chain: how will you find it was me. And that is with intent.

But we agree and I will reiterate: without rollback, current human coders cannot write reliable software. So in it's current state, smart contracts are a utopia and no one should trust them, with or without code audit. But if you still want to play a lottery of humanity vs complexity, read the code, think hard and put or not put your money. If you put your money, do not whine after you lost it. You might as well shout at your toilet for the same endresult.

Re:The collapse of the IRON stable coin by kevincox on Thursday June 17, 2021 @12:33PM (#27541493)
Sure, but if you both sign a legal contract to obey the outcome of the smart contract then no one owes anything, because the smart contract says that the $200M is gone.

Obviously this doesn't allow you get around laws such as warranties but I don't see why it can't be used if everyone agrees to it.

Re:The collapse of the IRON stable coin by only_as_i_fall on Thursday June 17, 2021 @02:17PM (#27542663)
A valid contract requires a meeting of minds such that inserting something designed to trick the other party inside a contract is pretty much always invalid.

If you sign a contract to abide by a smart contract that was designed in bad faith or misrepresented I fail to see how that's any different.

Even valid contracts are bound by the law. E.G. you can't sell yourself into slavery. Similarly, a smart contract can be a tool to execute the terms of a legal contract, but if it behaves in a way that would be illegal under a traditional contract I doubt any court in the US or Europe is going to recognize that as legal.

I admit enforcement is another issue entirely though.

Re:The collapse of the IRON stable coin by nradov on Thursday June 17, 2021 @01:25PM (#27542080)
That's not how US civil courts work. If a contract is flawed then a judgment can be rendered based on intent, equity, and other factors. There are centuries of common law precedent for this. The existence of blockchains and "smart" contracts changes nothing.
Re:The collapse of the IRON stable coin by ceejayoz on Thursday June 17, 2021 @12:40PM (#27541569)
In some cases, perhaps, but not all.

Fraud, for example, isn't legal even if you have a cleverly crafted contract that uses wording tricks to technically be true.

I would expect a court to take a dim view of a smart contract that has an obfuscated, non-obvious mechanism for someone to siphon off all the money in an undisclosed fashion. "Code is law", but so's "you can't defraud people".

Re:The collapse of the IRON stable coin by SiliconAlley on Thursday June 17, 2021 @03:25PM (#27543513)
Where’s the part where anybody defrauded anybody? This was clearly incompetence that benefited nobody (certainly the developers would rather not have TITAN implode and all of this USDC locked in a contract...). Embarrassing yes. Fraud? Pretty clearly no
Re:The collapse of the IRON stable coin by ceejayoz on Thursday June 17, 2021 @03:40PM (#27543707)
It's an example of a scenario where you can't sign certain rights away. Not specific to TITAN.
Re:The collapse of the IRON stable coin by lupire on Thursday June 17, 2021 @06:51PM (#27545339)
How can it be "locked"? Can't they deploy a protocol update to the members of the compute pool?
Re:The collapse of the IRON stable coin by acjohnson55 on Friday June 18, 2021 @01:04AM (#27547529)
Depends on how you write the contract. If you make a smart contract unilaterally updatable, then it's no longer decentralized and trustless, because people with admin rights can plunder it, or can be extorted, or compelled by authorities to turn over the capital.
Re:The collapse of the IRON stable coin by shkkmo on Thursday June 17, 2021 @01:32PM (#27542156)
> Sure, but if you both sign a legal contract to obey the outcome of the smart contract then no one owes anything,

You are begging the question by presupposing that for every smart contract there could be a possible legal contract that can bind the people who sign it to the results of the smart contract.

If a smart contract is illegal, then any written contract that binds people to the results of that contract would be similarly illegal.

Re:The collapse of the IRON stable coin by jcrawfordor on Thursday June 17, 2021 @01:55PM (#27542404)
Contracts can be unenforceable for reasons that might not be obvious to people who don't do contract law, as well. For example, the concept of consideration is not especially obvious, that contracts are often not enforceable if both parties do not receive consideration, which leads to things like peppercorn payments. I know about that as a layman but a contract attorney would know of many more non-obvious things that must be checked out to avoid having problems actually enforcing the contract. It seems like it would be very, very easy to produce a smart contract which a court would later determine was not enforceable in the first place, and perhaps order reversal of payments or other things.

For one, as a general concept the parties to the contract need to actually understand the terms and courts will somewhat regularly throw a contract out if they think there were implications that were not apparent to one of the parties. Smart contracts seem like absolute minefields for this kind of problem.

Re:The collapse of the IRON stable coin by shkkmo on Thursday June 17, 2021 @03:03PM (#27543237)
Yeah, consulting a lawyer before drawing up an important contract is usually a very good idea for precisely these reasons. You can probably make small adjustments to a boilerplate without doing so, but that always adds atleast a little risk.
Re:The collapse of the IRON stable coin by crooked-v on Thursday June 17, 2021 @02:28PM (#27542791)
A very obvious example: in most jurisdictions, a contract signed by a minor can be rendered null and void by that minor (or their legal guardian) at any time.
Re:The collapse of the IRON stable coin by unyttigfjelltol on Thursday June 17, 2021 @04:32PM (#27544244)
... and a small band of programmers quietly sneak out of the room ...

If your mechanic installs the tires in the passenger cabin, no one cares about the mechanics' lien. Depending on the judge they might not even care about the fine print on the back of the invoice, because installing tires in the passenger compartment is that dumb.

Re:The collapse of the IRON stable coin by thebean11 on Thursday June 17, 2021 @11:50AM (#27540956)
Sure, I don't disagree with that. For example, defrauding someone with a smart contract obviously doesn't offer the scammer legal protections.
Re:The collapse of the IRON stable coin by toomuchtodo on Thursday June 17, 2021 @11:51AM (#27540970)
Who defines fraud if the contract is contested?
Re:The collapse of the IRON stable coin by thebean11 on Thursday June 17, 2021 @11:57AM (#27541042)
Depends on which jurisdiction alleged fraud happens in. If the parties are anonymous or in "difficult" jurisdictions, it will be pretty difficult.

Fraudulent or not, though, you have a pretty heavy layer of protection as the money has already been transferred, and that money is not easy (close to impossible) to freeze.

Any reversal that happens will be necessarily by a threat outside the blockchain, as the governing body can't actually reverse the transaction. It's a second transaction.

Re:The collapse of the IRON stable coin by vkou on Thursday June 17, 2021 @12:33PM (#27541485)
The courts.