Abstract

If one is to believe the popular press and many “technical writings,” blockchains create not only a perfect transactional environment but also obviate the need for banks, lawyers and courts. The latter will soon be replaced by smart contracts: unbiased and infallible computer programs that form, perform and enforce agreements. Predictions of future revolutions must, however, be distinguished from the harsh reality of the commercial marketplace and the technical limitations of blockchain technologies. The fact that a technological solution is innovative and elegant need not imply that it is commercially useful or legally viable. Apart from attempting a terminological “clean-up” surrounding the term smart contract, this paper presents some technological and legal constraints on their use. It confronts the commonly made claims concerning their ability to automate the transacting process and to ensure perfect performance. It also examines the possibility of reducing contractual relationships into code and the ability to integrate smart contracts with the complexities of the real world. A closer analysis reveals that smart contracts can hardly be regarded as a semi-mythical technology liberating the contracting parties from the shackles of traditional legal and financial institutions. While some of their technical features seem prima facie attractive, especially to non-lawyers, a closer analysis reveals their many shortcomings.

Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.