Examples of Lexon Texts
The examples described in the following are from academic papers and the Lexon documentation.
Some are wired into the online vocabulary where every word is clickable. All examples can also be viewed in plain text format that can be helpful to copy-paste or download them.
Escrow
From the paper: The Holy Grail of Computational Law
Example > Plain > Paper >This is the example that features frequently in Lexon resources. It is discussed in the 2023 paper as well as the 2024 Lexon book and BIBLE. You can conjure it up in the Lexon online compiler by clicking the example button, and directly compile it.
Compiler >Asst. prof. Carla L. Reyes, SMU
U.C.C. Financing Statement
From the paper: Creating Cryptolaw for the Uniform Commercial Code
Example > Plain > Paper > Screen >Lexon allows for law to be executed as a program. Asst. prof. Carla L. Reyes of SMU pioneers the use of Lexon to write statute in her seminal 2021 paper. She created Lexon code as a proposal to the commission that is tasked with the reform of the U.S. trade law, which she advises on blockchain topics. This code could become model law, be adapted by states to be executed on the computers of their local agencies and protect billions of dollars of collateral.
Read Carla's paper that explains the background; use the Screen button to view a terminal interaction with a Javascript target.
Paper > Screen >Florian Idelberger, EUI
License Agreement
From the paper: Merging traditional contracts (or law) and (smart) e-contracts – a novel approach
Example > Plain > Paper >This test case is a license contract to license a copy of a software or other specified work for use and evaluation, in exchange for a licensing fee. Furthermore, sublicensees can be specified. These grants and license are defined in article 1. The sublicense part was inspired by Surden’s description of a licensing system where universities can automatically manage the licenses of their libraries and conclude more tailored licensing agreements. In article 2, it is defined that optionally, the licensee or sublicensee is commissioned to publish comments about the use of the product. This approves publication, but also requires it. In article 3, publishing of comments about the use and evaluation of the asset without approval by the licensor beforehand is prohibited. In case of unauthorized publication, the licensee has 24 hours to remove the published material. This improves the test case, as it requires use of external agents or data sources depending on the system, as otherwise there is no basis on which to automate or act. Additionally, the passing of time is tested with the time limit. Finally, in article 4, it is laid out that the license agreement terminates automatically upon breach of the licensing agreement, and that the licensee has to pay a fee in case of breach. The resulting license agreement is simplified for publication, but includes the most important features of license contracts.
Read Florian's paper that explains the background:
Paper >Lexoni 0.4 Preview
Oversimplicated DAO
From the book: Lexon. Also featured in the Lexon BIBLE.
Example > Plain > Book >This is an operating agreement, the smart contract code of the Oversimplicated DAO LLC, an algorithmically controlled legal person. Because it is written in Lexon, this document is at once legally binding prose and unstoppable blockchain code. The Oversimplicated DAO is a fund whose members appoint a manager, who appoints a trader who during the week trades the fund’s capital on an exchange. Over the weekend, members can exchange the manager or make an upgrade to this document, i.e., amend this operating agreement and at the same time, the smart contract whose algorithms govern the company.
This example is a preview of the coming Lexon 0.4 that has a focus on DAOs.