Smart contract: Difference between revisions
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{A|tech|}}Smart contracts cleave to [[Lawrence Lessig]]’s coinage [[Code is Law]] — you code legal rights into the electronic operating parameters between the parties: they physically constrain what you do to each other, rather than being abstract metaphysical considerations that float above your messy interactions which may or may not reflect those abstract terms. | {{A|tech|}}Smart contracts cleave to [[Lawrence Lessig]]’s coinage [[Code is Law]] — you code legal rights into the electronic operating parameters between the parties: they physically constrain what you do to each other, rather than being abstract metaphysical considerations that float above your messy interactions which may or may not reflect those abstract terms. | ||
Notwithstanding breathless [[distributed ledger technology]] chat to the contrary, we’ve had [[smart contract|smart contracts]] for a while: wherever counterparties interact electronically | Notwithstanding breathless [[distributed ledger technology]] chat to the contrary, we’ve had [[smart contract|smart contracts]] for a while: wherever counterparties interact electronically, as they do when posting collateral under a [[CSA]], for example: it is the algorithms, thresholds and validation sub-routines embedded in the technological infrastructure, rather than the abstract ones set out in paper, that, in practical terms, govern what, when and how much collateral the parties exchange. Everything happens fast, deus ex machina, and there is no articled clerk with a quill monitoring the data inflows and outflows and cross checking each against the eligibility criteria written in the CSA. Instead, that is all coded into the machine. All a smart contract amounts to is the insight that that operational handshake, rather than the bit of paper you first wrote it down on, governs. It is hardly a big leap to ditch the need for abstract textual reflections of operating parameters in separately executed "legal terms". | ||
and consider this: if, in a collateral arrangement, due to a mutual mis-key when setting up your the operating parameters in 1998, you allowed a wider range of collateral through than the CSA formally mandated, and no-one noticed this until your counterparty blew up in late 2008 and the ropey collateral it had been posting for a decade suddenly tanked, what good is your piece of paper then? Not much, in this commentator’s humble opinion. | |||
No smart contract will be able to measure these things, much less make an executory decision about them. | So, where the contract is of a highly operational nature — and much of the machinery of finance is — smart contracts aren’t so much a revolutionary idea as a necessary one. But the problem is this: while 80% of your {{t|contract}} is governed by electronic interaction and is suitably “smart” already, the 20% that matter when things turn growlish typically isn't. The [[close out]] rights, [[Termination event|termination triggers]] and [[events of default]]: matters that can hardly be ascertained by electronic transmission between the parties: they require judgment, experience and evaluation, both of their existence (is that [[Material adverse change|adverse change]] really “material”? Hey, [[legal eagles]]! What does “material” mean?) and in terms of one’s response: Ok, the [[NAV trigger]] has been hit. But is this the real thing or is this drill? Do we want to close out? How is our overall position? What do we think of the counterparty's forward prospects? What are the pros and cons? | ||
No [[smart contract]] will be able to measure these things, much less make an executory decision about them. | |||
{{seealso}} | {{seealso}} | ||
*{{br|Code: Version 2.0}} | *{{br|Code: Version 2.0}} | ||
{{C|Technology}} | {{C|Technology}} | ||
Revision as of 09:49, 20 September 2019
|
JC pontificates about technology
An occasional series.
|
Smart contracts cleave to Lawrence Lessig’s coinage Code is Law — you code legal rights into the electronic operating parameters between the parties: they physically constrain what you do to each other, rather than being abstract metaphysical considerations that float above your messy interactions which may or may not reflect those abstract terms.
Notwithstanding breathless distributed ledger technology chat to the contrary, we’ve had smart contracts for a while: wherever counterparties interact electronically, as they do when posting collateral under a CSA, for example: it is the algorithms, thresholds and validation sub-routines embedded in the technological infrastructure, rather than the abstract ones set out in paper, that, in practical terms, govern what, when and how much collateral the parties exchange. Everything happens fast, deus ex machina, and there is no articled clerk with a quill monitoring the data inflows and outflows and cross checking each against the eligibility criteria written in the CSA. Instead, that is all coded into the machine. All a smart contract amounts to is the insight that that operational handshake, rather than the bit of paper you first wrote it down on, governs. It is hardly a big leap to ditch the need for abstract textual reflections of operating parameters in separately executed "legal terms".
and consider this: if, in a collateral arrangement, due to a mutual mis-key when setting up your the operating parameters in 1998, you allowed a wider range of collateral through than the CSA formally mandated, and no-one noticed this until your counterparty blew up in late 2008 and the ropey collateral it had been posting for a decade suddenly tanked, what good is your piece of paper then? Not much, in this commentator’s humble opinion.
So, where the contract is of a highly operational nature — and much of the machinery of finance is — smart contracts aren’t so much a revolutionary idea as a necessary one. But the problem is this: while 80% of your contract is governed by electronic interaction and is suitably “smart” already, the 20% that matter when things turn growlish typically isn't. The close out rights, termination triggers and events of default: matters that can hardly be ascertained by electronic transmission between the parties: they require judgment, experience and evaluation, both of their existence (is that adverse change really “material”? Hey, legal eagles! What does “material” mean?) and in terms of one’s response: Ok, the NAV trigger has been hit. But is this the real thing or is this drill? Do we want to close out? How is our overall position? What do we think of the counterparty's forward prospects? What are the pros and cons?
No smart contract will be able to measure these things, much less make an executory decision about them.