04.11.2014 Views

Great+Chain+of+Numbers+A+Guide+to+Smart+Contracts,+Smart+Property+and+Trustless+Asset+Management+-+Tim+Swanson

Great+Chain+of+Numbers+A+Guide+to+Smart+Contracts,+Smart+Property+and+Trustless+Asset+Management+-+Tim+Swanson

Great+Chain+of+Numbers+A+Guide+to+Smart+Contracts,+Smart+Property+and+Trustless+Asset+Management+-+Tim+Swanson

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

While his proposal will likely receive a mixed reaction, he sees this evolution in terms of the existing role<br />

of a 3 rd party. In his view, “taking the asset-backed loan as an example again, let us suppose there are<br />

multiple lenders. Usually those lenders will enter into a contractual arrangement with an agent or<br />

trusted 3 rd party, another bank or a professional trustee company, to hold and exercise their rights, at<br />

their direction and on their collective behalf. This arrangement works because (1) the common law<br />

allows the lenders to contract with that TTP on certain terms and (2) the parties know where to find the<br />

TTP if it screws up.”<br />

In Byrne’s view, once a trusted 3 rd party is removed from simple transaction of the kind in the style<br />

proposed by Nick Szabo, such an agreement differs from a contract concluded in the normal way in<br />

that:<br />

1) “the TTP and its associated costs are disintermediated and users become independent of<br />

existing institutions; however,<br />

2) “the price of decentralisation is full cash collateralisation, making even the most basic lending<br />

contract unviable for ordinary commerce;<br />

3) “the element of discretion to hold our rights in abeyance and adapt to changed circumstances<br />

is limited by the algorithm; and<br />

4) “in all likelihood, the possibility of enforcement for losses which arise beyond the provisions<br />

made in the smart contract itself will be compromised, because<br />

(a) by design, the technology doesn’t permit this course of action (as a party who would<br />

be liable for, e.g., consequential loss would almost certainly not hand over his private<br />

key in circumstances where his liability would increase); and<br />

(b) even if one could present the contract to a court and trace all of the relevant assets,<br />

reintroducing a contract to the legal system when it was intentionally structured to exist<br />

outside of it does not tend to work out well for the party seeking to rely on its<br />

provisions.”<br />

This is an issue that numerous reviewers of this manuscript asked: for digital contracts, how is the<br />

problem of real life enforcement solved? After all, even if things are enforceable on the blockchain, a<br />

human still has to input the conditions for which contracts will be executed, and if anything happens in<br />

real life, it still has to be enforced by lawyers and the state. However, there is no clear cut answer to<br />

this and each jurisdiction will likely react in different ways: from acceptance to outright banning.<br />

Yet Byrne sees only one solution: invite 3 rd parties back into the equation.<br />

As Szabo said, “by extracting from our current laws, procedures, and theories those principles which<br />

remain applicable in cyberspace, we can retain much of this deep tradition, and greatly shorten the time<br />

needed to develop useful digital institutions.”99 To Byrne, this means that while “a technical<br />

understanding of jurisdiction specific legal principles is absolutely essential to smart contract design,<br />

trying to encode the sophistication of common law into an algorithm is impossible – see, for example,<br />

the Eurosail-UK 2007-3BL case, where ambiguity relating to the statutory consequences of a purely<br />

mechanical provision, which in all likelihood nobody expected would ever be invoked at the time the<br />

29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!