Lexon
{"title": "LEXON", "logoImg": "bafkreicrbynk75jdla6i2vnnma3q3cfnljpuxrzyzetc6ufua5umlki3l4", "website": "https://www.lexon.org", "bannerImg": "bafkreifzm6tnebkndqf4jseduuyynvdglzyc2chvpkamowffpkie6b36m4", "createdAt": 1732106900277, "userGithub": "lexonian", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-31T17:55:07.184Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0x61ae3d0c28187a965fae749a6c110650e0bb4dc1628dde16348b7561c29f576428220e23de72f4dcaaa2c8f5f6dda461d2f191913be890f09a33a395bd0310cb1c", "eip712Domain": {"types": {"Proof": [{"name": "@context", "type": "string"}, {"name": "created", "type": "string"}, {"name": "proofPurpose", "type": "string"}, {"name": "type", "type": "string"}, {"name": "verificationMethod", "type": "string"}], "@context": [{"name": "nullifiers", "type": "NullifiersContext"}, {"name": "provider", "type": "string"}], "Document": [{"name": "@context", "type": "string[]"}, {"name": "credentialSubject", "type": "CredentialSubject"}, {"name": "expirationDate", "type": "string"}, {"name": "issuanceDate", "type": "string"}, {"name": "issuer", "type": "string"}, {"name": "proof", "type": "Proof"}, {"name": "type", "type": "string[]"}], "EIP712Domain": [{"name": "name", "type": "string"}], "CredentialSubject": [{"name": "@context", "type": "@context"}, {"name": "nullifiers", "type": "string[]"}, {"name": "id", "type": "string"}, {"name": "provider", "type": "string"}], "NullifiersContext": [{"name": "@container", "type": "string"}, {"name": "@type", "type": "string"}]}, "domain": {"name": "VerifiableCredential"}, "primaryType": "Document"}, "proofPurpose": "assertionMethod", "verificationMethod": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb#controller"}, "issuer": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb", "@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/vc/status-list/2021/v1"], "issuanceDate": "2025-03-31T17:55:07.184Z", "expirationDate": "2025-06-29T17:55:07.184Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x05f6efaa0E7F00dB09C1f7fd91F7e7f5ec92e19c", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextGithubOrg#lexon-org#193349241", "nullifiers": ["v0.0.0:se6rgvshmxI4fIEOl2dUZMn+8fC2kUw2R2M7BLp/990="]}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-31T13:46:52.816Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0xecdc35f51626dd6e103753bf2978487b5f2b276ed03caafd7f4092298cc552b24b6fbede0da1461b852fa47d25740840c5d665fdba0c759458e0598b4123ba351b", "eip712Domain": {"types": {"Proof": [{"name": "@context", "type": "string"}, {"name": "created", "type": "string"}, {"name": "proofPurpose", "type": "string"}, {"name": "type", "type": "string"}, {"name": "verificationMethod", "type": "string"}], "@context": [{"name": "nullifiers", "type": "NullifiersContext"}, {"name": "provider", "type": "string"}], "Document": [{"name": "@context", "type": "string[]"}, {"name": "credentialSubject", "type": "CredentialSubject"}, {"name": "expirationDate", "type": "string"}, {"name": "issuanceDate", "type": "string"}, {"name": "issuer", "type": "string"}, {"name": "proof", "type": "Proof"}, {"name": "type", "type": "string[]"}], "EIP712Domain": [{"name": "name", "type": "string"}], "CredentialSubject": [{"name": "@context", "type": "@context"}, {"name": "nullifiers", "type": "string[]"}, {"name": "id", "type": "string"}, {"name": "provider", "type": "string"}], "NullifiersContext": [{"name": "@container", "type": "string"}, {"name": "@type", "type": "string"}]}, "domain": {"name": "VerifiableCredential"}, "primaryType": "Document"}, "proofPurpose": "assertionMethod", "verificationMethod": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb#controller"}, "issuer": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb", "@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/vc/status-list/2021/v1"], "issuanceDate": "2025-03-31T13:46:52.816Z", "expirationDate": "2025-06-29T13:46:52.816Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x05f6efaa0E7F00dB09C1f7fd91F7e7f5ec92e19c", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextTwitter#hdiedrich", "nullifiers": ["v0.0.0:nf4DJjQwCmNm5eETjF/IvAJDU2pWgKb1951MaHy/P0Y="]}}}, "description": "**Lexon enables no-code smart contracts that read like plain English.**  \n\n\n---\n\n\nLexon texts are plain English program code, making smart contracts readable for all, by deterministically compiling English to Solidity.    \n\n  \n\n**Current milestone 0.4:** enhancing the language to work for DAOs, on the way to implement the grammar as exemplified in the  [Oversimplicated DAO](https://www.lexon.org/oversimplicated.html) example.  \n\nAlso see the [Hybrid AI](https://explorer.gitcoin.co/#/projects/0x81f132f2b8ef92b6f9c706b968c8e71b8175c4543dd962b20664476ca292f675) project for effortless smart contract creation via text chat and the  space game concept [Stardust](https://explorer.gitcoin.co/#/projects/0xcebab1a84662472fb39bba11ff4c22ba17a66644a1c3dd8103444bff6be5a96a) that uses Lexon for crafting and custom clan rules.\n\n---\n\n\n*Created by [Henning Diedrich](https://x.com/hdiedrich)*\n\n\n\n⟶    The [Lexon Book](https://www.amazon.com/dp/169774768X).\n\n\n\n⟶    The [Lexon site](https://www.lexon.org).\n\n\n\n---\n\n\n\n## On Lexon\n\n\n\nLexon is a plain-text programming language for law and smart contracts. It is the first of a new generation of languages. Its grammar describes the intersection of natural human language and higher order logic in the way that Wittgenstein demanded. To a degree, it ends the quest for an unambiguous universal language for philosophy and pure thought as envisioned by Leibniz, Frege, Russel, or Carnap. The key to this is how Lexon maps natural language to compiler building tools, which is intuitively convincing, and in line with what the tools were designed for, but different from what computer sciences had gotten used to.\n\n\n\nLexon is the language that Robotic Laws will be articulated in, to embed unambiguous limitations into autonomous machines, written by lawmakers, the code being official law, created and approved in the democratic process. Lexon thus solves a long-standing quest of Computational Law. It works for blockchain smart contracts as well as off-line, and also off-machine. For its advantages in transparency and accessibility, it may become a mainstream programming language. Beyond its uses in connection with computers, it may over time replace today's legalese as a more useful language for law and contracting. The counter arguments of the legal profession are addressed in the available publications that discuss Lexon. The work of professors of law about Lexon may serve as invitation to imagine that progress is possible, also for a two thousand years old industry.\n\n\n\nLexon is the language of lawmakers and programmers alike, enabling the coming profession of the legal engineer.\n\n\n\nLexon is under development. The current consistent distribution is 1.2. It unites compiler binaries, source code and documentation in a consistent package.\n\n\n\nhttps://github.com/lexonian/lexon/releases/tag/Lexon-Distribution-1.2\n\n\n\n.\n\n\n## Example\n\n\n\nMore examples are collected (with links that enumerate each word’s use), at\n\n\n\nhttps://www.lexon.org/vocabulary.html#examples\n\n\n\nand at:\n\n\n\nhttps://github.com/lexonian/lexon/tree/master/examples (see descriptions in README).\n\n\n\n\n\n\nThis is an example of a Lexon text:\n\n\n    LEX Escrow.\n\n    \"Payer\" is a person.\n    \"Payee\" is a person.\n    \"Arbiter\" is a person.\n    \"Payment\" is an amount.\n    \"Fee\" is an amount.\n\n    The Payer pays a Payment into escrow,\n    appoints the Payee,\n    appoints the Arbiter,\n    and also fixes the Fee.\n\n    CLAUSE: Pay Out.\n    The Arbiter may pay from escrow the Fee to the Arbiter,\n    and afterwards pay the remainder of the escrow to the Payee.\n\n    CLAUSE: Pay Back.\n    The Arbiter may pay from escrow the Fee to the Arbiter,\n    and afterwards return the remainder of the escrow to the Payer.\n\n\n\n\nThis is a smart contract. You compile it to Solidity with\n\n    lexon --sol escrow.lex\n\nThe result looks like this https://github.com/lexonian/lexon/blob/master/tests/escrow.0.solx.exp\n\n\n(Please star the repo, thanks.)\n\n\nAnyone can read this Lexon text—this digital contract—and understand what it means. It can be shown to a judge, it can be understood by business partners and customers as well as a company’s management and legal department; and it can also – as is – be run as a program, for example on a blockchain, i.e. as smart contract.\n\n\n\nSoon, any type of program can be written this way. And any type of agreement can be automated and made impossible to be broken. This will uncouple business necessities from the judicative and executive powers, their astronomical costs and glacial speed. Digital Contracts cost pennies to set in motion and can securely make any sum of money change hands in minutes. This will be a game changer for a massive slice of commercial activity and enable a long tail of private trade. It will also change the standards for governance and government.\n\n\n.\n\n## AUDIENCE \n\n\n\nEveryone — Lexon is designed to broaden crypto adoption by including non-programmers. It can also be used off-chain with Javascript.\n\n\n\nParticularly, blockchain-affine lawyers have been excited about Lexon (see papers).\n\n\n\nTo the degree that smart contracts are used as legal agreements, judges are a relevant target group.\n\n.\n\n\n## Inclusion\n\n\n\nBlockchain technology was made by hackers for hackers – but with Lexon, anyone can read programs now without any knowledge of programming. And thus, consumers, as well as businesspeople, judges, jury members, even lawmakers will be able to read any smart contract about which they might be tasked to decide about, investigate, legislate, to verify or enter. Through this, contracting may become part of the definition of literacy and a silver arrow in the quiver of democracy.\n\n.\n\n\n\n## MISSION — Access to Justice\n\n\n\nAs lawyers confirm, the code above is a legally enforceable contract: it can be used to demonstrate to a judge what the meeting of the minds of the parties to the contract was. There are no style requirements for a contract. There can't be any, or else a typo or poor grasp of grammar could render contracts invalid. But smart contract code, e.g., written in Solidity or Sophia, would always lead to a battle of experts if brought to court. Because non-programmers cannot read them.\n\n\n\nNot all contracts need to be in writing. The ‘contract’ itself is always the abstract agreement of two parties, no matter how it was expressed. A signed paper merely proves it. \n\n\n\n**Now, a readable, digitally signed program can prove and perform this will.**\n\n\n\n[WWW.LEXON.ORG](https://www.lexon.org)\n\n\n---\n\n\n# IN DEPTH \n\n---\n\n\n\n## OBJECTIVE\n\n\n\n\nThe goal is to make smart contracts part of daily life for everyone like a smart phone. In the form of bespoke agreements tailored to the plethora of situations of real life, to onboard the next billion users to blockchain generally and the Ethereum ecosystem specifically.\n\n\n\nThe current roadmap for the language has its focus on creating a [Hybrid AI](https://explorer.gitcoin.co/#/projects/0x81f132f2b8ef92b6f9c706b968c8e71b8175c4543dd962b20664476ca292f675) interface to ease the effort of writing Lexon texts; extending the Lexon grammar for DAOs; creating awareness and traction for Lexon by demonstrating its power in the shape of an [MMORPG](https://explorer.gitcoin.co/#/projects/0xcebab1a84662472fb39bba11ff4c22ba17a66644a1c3dd8103444bff6be5a96a) project; and finding first professional customers—law firms—with a groundbreaking implementation of the new U.S. trade law on the blockchain.\n\n\n\n\nThe online compiler, around which this application revolves, did in an earlier iteration have the capability to create smart contracts with one click, on Ethereum. This is too expensive for small contracts at this point in time.\n\n.\n\n## PROBLEM\n\n\n\nLexon generally helps overcoming the hurdles to mainstreaming crypto, because it reduces the opaqueness of smart contract technology, making it more transparent and acceptable.\n\n\n\nThis can solve the question, whether smart contracts are real contracts. With Lexon, an English-language legal agreement and the smart contract become the same.\n\n\n\nIn sum, this could address the problem of the exclusion of weaker and poorer demographics from digital commerce: Lexon can enable a very long tail of markets that cannot exist at this point, because the cost of policing them would be higher than their margins. Crypto should in theory be able to do that on its own. But Lexon might provide the necessary accessibility and free compatibility with the existing legal system.\n\n\n\nLexon also addresses the dilemma that a fork-lift replacement of many existing processes by crypto is unrealistic. Instead, Lexon makes crypto “backwards compatible” —simply: readable— which allows for a smooth step-by-step transition. Because language is the medium of commerce and law. Lexon makes crypto compatible with the legacy protocol. This is no aphorism. It is very concrete and powerful.\n\n\n\n.\n\n\n\n## SOLUTION\n\n\n\nLexon leverages natural language processing research, going as far back as the 80s to employ the fitting approach to ‘calculate with words’ (Leibniz). Language is not used as a specification with Lexon, but immediately executed, as if it was a program.\n\n\n\nIndustry standard compiler-building is used to implement a natural language like a programming language, interpreting English grammar like a programming language grammar.\n\n\n\nThis is not a statistical approach but linguistic, and precise. It creates fully transparent and repeatable results. It has an internal representation of meaning that is grammatical and directly accessible. It is not generative AI, although there are similarities. The Lexon compiler is an AI tool in the same sense that a Prolog compiler is. However, Lexon is more precise.\n\n\n\n \n\n.\n\n\n\n## VALIDATION\n\n\n\nThe Lexon concept has been validated in-depth through interviews, tests and workshops with target groups, including lawyers and judges. It is subject of academic papers. There is ongoing work to pinpoint Lexon’s killer app.\n\n\n\nAsst. prof. Carla Reyes — Cryptolaw \n\nhttps://scholarlycommons.law.wlu.edu/wlulr/vol78/iss4/7/\n\n\n\nProf. Christopher Clack — Languages\n\nhttps://arxiv.org/abs/2104.03764\n\n\n\nThe underlying linguistic and CS concept has been proven by creating the Lexon compiler 0.3, which implements the natural language programming approach and is conceptually clean and stable within its scope.\n\n\n\nhttps://github.com/lexonian/lexon/releases/tag/Lexon-Distribution-1.2\n\n\n\n\n\n.\n\n\n\n## RELEVANCE\n\n\n\nOvercoming the opaqueness of smart contracts is rated a key factor to encourage participation in smart contract technology. Lexon allows everyone concerned to verify what a smart contract means.\n\n\n\nIt has also been shown that Lexon can be used to write law. This feature may become the crucial tool to evolve our democratic processes, regain trust in institutions, and help countries to avoid suffocating themselves with red tape.\n\n\n\nFor its propensity of making crypto superpowers available to mundane and key processes, Lexon might play an essential role in retaining evolutionary capacity of governance and politics, providing a path to meaningful change and a dial back of current excesses.\n\n\n\n\n\n.\n\n\n\n## HOW LEXON BENEFITS BLOCKCHAIN\n\n\n\nThe accessibility and inclusivity Lexon brings can make trustless technology appealing to a much wider audience, helping to drive adoption.\n\n\n\nLexon’s transparency should help unlock the potential of smart contracts for SME.\n\n\n\nFor the crypto community, Lexon revives the vision of DIY smart contracts, created for one specific use case.\n\n\n\nLexon aligns with blockchains in the Ethereum ecosystem naturally as it is globally available free, open source, can be used with complete privacy, without restrictions, and is not controlled by any company.\n\n\n\n.\n\n\n\n## HOW LEXON ENABLES USERS\n\n\n\nLexon is a tool that empowers developers to create applications that are more accessible for *their* users: i.e., it empowers multiple layers across the crypto user community.\n\n\n\nSmall, situational smart contracts, in natural language, may become part of the notion of digital literacy.\n\n\n\n.\n\n\n\n## FREE AND OPEN SOURCE\n\n\n\nThe Lexon language and compiler are free and open source, they are not monetized.\n\n\n\nThe expectation is that projects that use Lexon, and the crypto ecosystem at large will take part in developing Lexon, contributing code and grants, and eventually having employees dedicated to it, like in the gcc ecosystem.\n\n\n\n\n\nBeing open source, Lexon should stay the focal point for natural language programming, because being open source should have the effect of bundling efforts in this technological direction: anyone can use it and/or improve it, reducing the incentive to create a competing project.\n\n\n\nFor the near future, the same diligence and grass roots work that brought Lexon to where it is now will carry it forward: a lot of communication with the target group and iterations to make sure to arrive at simplicity and accessibility, based on sound technical foundations that draw on deep experience in crypto, linguistics and programming language design, in both theory and practice.\n\n\n\nOn the conceptual side, the complete argument about its relevance is laid out in the book Characteristica Universalis (https://www.amazon.com/dp/B0D8Y6F8DW).\n\n\n\nLexon is not just a theory but working code, it proves the controversial idea about language and programming that it is based on.\n\n\n\nOnce the current gen AI focus has relaxed, it will be easier to recognize Lexon as a pioneering effort in breaking down the border between natural language and programming, by interpreting natural language as if it were a program.\n\n \n\n .\n\n\n\n ## ON AI \n\n\n\nA blood feud between generic and symbolic AI research has been going for some decades.\n\n\n\nAccordingly, some casual observers have dismissed Lexon’s approach as worthless.\n\n\n\nTo others, it is obvious that Lexon has a place in the history of logic.\n\n\n\nWhile goals are similar, priorities are not. Lexon has a different workflow and different strengths. It “just” makes machine execution transparent for everyone. This is the opposite of gen AI.\n\n\n\nLexon does so by unfailing accessibility, providing perfect agency. It is aligned by design.\n\n\n\nHow similar Lexon code is to tensors see: \n\n\n\nhttps://github.com/lexonian/lexon/blob/dbb46e554c7c444bbf3d114c15a1f6faa11f76ff/build/scanner.c#L456 \n\n\n\nThese tables are the translated model of the grammar:\n\n\n\nhttps://github.com/lexonian/lexon/blob/master/grammar/english.lgf\n\n\n\nThe tables can be small, because they are precise.\n\n\n\n.\n\n\n\n\n\n.\n\n\n\n## COMPETING APPROACHES\n\n\n\nMore relevant predecessors and contemporaries to Lexon are discussed in the LEXON BIBLE, Appendix III (https://www.amazon.com/dp/1656262665). Here are the most important similar projects:\n\n\n\n\n\n### GENERATIVE AI\n\n\n\nLexon is fully transparent, thus accessible, and aligned, has an internal representation of meaning, and is fully deterministic, thus always precise.\n\n\n\nSee above, “ON AI.”\n\n\n\n\n\n### LOGICAL ENGLISH\n\n\n\nLogical English also reads like natural language. But it does not execute language like a program, instead, it interprets language as first-order logic rules. Its execution is not deterministic and logic programming, in general, does not work well with time and change. \n\n\n\n\n\n### LOGLAN\n\n\n\nThe artificial human language Loglan has a regular, unambiguous logical grammar, like Lexon. But it does not read like natural language (at all) and it does not include a mapping of programming paradigms to natural language, as Lexon does.\n\n\n\n\n\n### SOLIDITY\n\n\n\nLexon can compile English to Solidity, which indicates that the two compilers are complementary and not in competition. Lexon is concerned with the very last mile that separates humans and machines.\n\n\n\n\n\n### GRAPHICAL CODING\n\n\n\nVisual coding tools have a focus on program creation. Lexon’s main contribution is that texts are readable without any training and can double as normal contracts.\n\n\n\n\n---\n\n\n# TEAM\n\n---\n\nThe grant application is submitted by the creator of Lexon.\n\n\n\nI wrote the first book on Ethereum, debugged geth for IBM in 2016, been to every Devcon, architected IBM’s blockchain, and DeBeers’ diamond chain. \n\n\n\nI did decades of freelance and open source programming. Love crypto for the tech & its world-changing potential.\n\n\n\nAs a freelancer, I had to experience that it can be difficult to get paid if people decide to just not honor a contract. That is definitely part of why I love smart contracts.\n\n\n\nI created systems, blockchains and worked across the full stack, and beyond, creating languages, database drivers, twitch games.\n\n\n\nI have always been interested in AI, and acquired strong opinions about it. I believe that understanding the limits of AI well allowed me to navigate the edge of what is possible.\n\n\n\nMy interest in computer languages lead me to learning and using two dozen different ones, from mainstream to arcane. I find they have different characters, different feels, different communities of course, and hence different vibes. I sure love creating them. I used 23 computer languages professionally, and created 2 relevant domain specific languages (for insurance and law).\n\n\n\nI often use bleeding edge, newest tech to build new apps. But very old, very stable tech to build new tools.\n\n\n\nThe way I build is usually with a lot of responsibility, including creating the spec, interviewing future users, to find out what is really needed.\n\n\n\nCrypto is my daily bread for 10 years, since Ethereum came to Berlin. I grew interested in the legal side of smart contracts while giving talks and being exposed to fellow speakers with a legal education.\n\n\n\nIBM later tapped me to become their “Mr. Blockchain,” as I got called. And I became the first architect of IBM’s own blockchain, Hyperledger.\n\n\n\nI have created a successful (proprietary) programming language before, specialized for a financial industry: retail insurances.\n\n\n\nThe essential, linguistic element of Lexon likely benefits from my experience as a performing artist. This might have helped to pinpoint the program-like elements in natural grammar.\n\n\n\nI am in blockchain tech for 10 years.\n\n\n\n---\n\n\n# MORE INFORMATION\n\n---\n\n\nPlease note that to READ Lexon texts, NO preparation is necessary.\n\n\nThe Lexon subset of English is optimized for readability—because any program, and contract, is more often read than written (*Brian J. Fox*).\n\n\nMost documentation below revolves around *writing* Lexon. Some literature on Lexon is scientific and philosophic, comparing it to similar approaches and suggesting its place in the history of logic.\n\n\nLexon is documented in articles, books, and academic papers, and supported by hands-on documentation: a manual, tutorial, etc. The central place to learn about it is the lexon site at https://www.lexon.org\n\n\nThe source code is at github.com/lexonian/lexon.\n\n* Writer’s Manual\t\thttps://lexon.org/docs/Lexon%20Manual%200.3.pdf\n* Writer’s Tutorial \t\thttps://lexon.org/docs/Lexon%20Tutorial%200.3.pdf\n* Vocabulary \t\t\thttps://lexon.org/vocabulary.html\n* Examples \t\t\thttps://lexon.org/examples.html\n* Resources \t\t\thttps://lexon.org/resources.html\n* Papers \t\t\thttps://lexon.org/papers.html\n* Books \t\t\thttps://lexon.org/books.html\n* Site \t\t\t\thttps://lexon.org\n\n\n\n\n\n\n\n\n## R E C O M M E N D E D  •  R E A  D I N G\n\n\n\n\n\n\n\n\n### 1.\tEXAMPLES \n\n\n\nBecause Lexon is self-explanatory by its very nature, examples are a great start.\n\n\n\nThese example texts are cross-linked to detailed explanations:\n\n\n\nwww.lexon.org/vocabulary.html#examples. \n\n\n\n\n\n### 2.\tSOURCE\n\n\n\nTo check out the tech, consider a review of the source repo, including the README:\n\n\n\nhttps://www.github.com/lexonian/lexon. \n\n\n\n\n\n### 3.\tBIBLE\n\n\n\nCasually browsing—cherry-picking—the Lexon BIBLE should be a great way to go deeper:\n\n\n\nhttps://www.amazon.com/dp/1656262665\n\n\n\n\n\n### 4.\tACADEMIC PAPERS\n\n\n\nRemarkable academic papers have been written that inspect Lexon. One demonstrates how to write statute (law) in Lexon. The other compares Lexon to other attempts to make language computable.\n\n\n\na. Asst. prof. Carla Reyes — Cryptolaw \n\nhttps://scholarlycommons.law.wlu.edu/wlulr/vol78/iss4/7/\n\n\n\nb. Prof. Christopher Clack — Languages\n\nhttps://arxiv.org/abs/2104.03764\n\n\n\n\n\n### 5.\tPHILOSOPHY\n\n\n\nThe book Characteristica Universalis explains the philosophy behind Lexon:\n\n\n\nhttps://www.amazon.com/dp/B0D8Y6F8DW\n\n\n\n\n\n### 6. \tSITE\n\n\n\nMore information is presented at the Lexon site, especially the resources page:\n\n\n\nhttps://www.lexon.org/resources.html\n\n--- \n\nJoin @Lexonians on Telegram https://t.me/lexonians\n\n\n\n\n\n\n\n\n\n", "logoImgData": {}, "bannerImgData": {}, "projectGithub": "lexon-org", "projectTwitter": "hdiedrich"}