2017
DOI: 10.2139/ssrn.3038406
|View full text |Cite
|
Sign up to set email alerts
|

Smart Contracts: Terminology, Technical Limitations and Real World Complexity

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
42
0
2

Year Published

2018
2018
2024
2024

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 39 publications
(44 citation statements)
references
References 3 publications
0
42
0
2
Order By: Relevance
“…In particular, the wording of regulatory policies in plain text can be rather convoluted and such policies do not lend themselves easily to mapping into an executable language with the correct semantics. To illustrate, consider a sample clause in the purchase agreement between Fresh Export and Best Fruit: “in case of an unforeseen situation, such as drought, excessive rain, fire, war, or for any other reasonable cause that is beyond the parties’ control, neither party shall be considered liable for losses and damages.” First, this clause contains “desired ambiguities” (Mik, ), such as “reasonable cause,” which leave parties the flexibility to work out a resolution when an unanticipated event occurs. However, such a clause can hardly be represented formally or measured objectively to translate accurately into smart contract code.…”
Section: Blockchain System Design: Challenges and Research Opportunitiesmentioning
confidence: 99%
See 3 more Smart Citations
“…In particular, the wording of regulatory policies in plain text can be rather convoluted and such policies do not lend themselves easily to mapping into an executable language with the correct semantics. To illustrate, consider a sample clause in the purchase agreement between Fresh Export and Best Fruit: “in case of an unforeseen situation, such as drought, excessive rain, fire, war, or for any other reasonable cause that is beyond the parties’ control, neither party shall be considered liable for losses and damages.” First, this clause contains “desired ambiguities” (Mik, ), such as “reasonable cause,” which leave parties the flexibility to work out a resolution when an unanticipated event occurs. However, such a clause can hardly be represented formally or measured objectively to translate accurately into smart contract code.…”
Section: Blockchain System Design: Challenges and Research Opportunitiesmentioning
confidence: 99%
“…However, it is practically impossible to ensure that the software code is bug‐free. Hence, risk is not entirely eliminated (Mik, ). This is clearly a limitation of blockchain technology.…”
Section: Blockchain System Design: Challenges and Research Opportunitiesmentioning
confidence: 99%
See 2 more Smart Citations
“…Essentially, smart contracts do not rely on human intervention, and their implementation is guided and overseen by other nodes in the blockchain network. Therefore, once the contract is triggered, the scripted contract self-executes (Mik, 2017). This is often achieved using trigger events when scripting the contact.…”
Section: Speed and Efficiencymentioning
confidence: 99%