LLL_erc20 | An implementation of Ethereum ERC20 tokens in LLL | Blockchain library

LLL_erc20 is a JavaScript library typically used in Blockchain, Ethereum applications. LLL_erc20 has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

According to the Ethereum Homestead Documentation,. Lisp Like Language (LLL) is a low level language similar to Assembly. It is meant to be very simple and minimalistic; essentially just a tiny wrapper over coding in EVM directly. LLL is one of the three living languages for Ethereum contract creation, alongside Solidity and Serpent/Viper (which itself compiles to LLL). If you have the Solidity compiler, then you may well have LLL already. It's bundled with some of the solc releases as lllc. It's fair to say that LLL is lagging substantially behind Solidity in popularity for contract creation. But Daniel Ellison of ConsenSys is on a mission to revive it. Here as well. LLL is a low-level language, just one step above Ethereum Virtual Machine (EVM) bytecode. Why would we choose to go back to the 1970s in programming terms when we have all the object-oriented joys of Solidity at our disposal?. Well, the EVM is a severely resource-constrained environment. Execution, memory and storage all have significant costs. For all its popularity, the Solidity compiler is not great at producing very efficient code. The bytecode generated by Solidity is full of redundancies, bloat, pointless jumps and other inefficiencies that cause steam come out of my ears, but, much more importantly, unnecessarily high gas usage. The low-level nature of LLL reminds you constantly that you are dealing with a resource-constrained environment. The LLL compiler doesn't auto-generate any of the junk you see in Solidity bytecode. This typically results in LLL bytecode being substantially more compact and efficient to run than Solidity bytecode. It is for this reason that the deployed ENS registry was written in LLL. Of course, there are downsides. High-level languages exist for a reason. But it's not as bad as you might imagine. After only a week's spare time dabbling with LLL I was able to code up the erc20.lll example here. And I'm not any kind of developer by profession (which may be apparent from the code). A fully functional implementation of the ERC20 token standard. I know it looks a bit long-winded, but of the (original) 349 lines, 84 are blank, 138 are comment, and only 127 are actual code. These Lisp-like languages lend themselves to sparse layout and lots of whitespace. I like this. It makes me feel calm. Actually, quite a lot of the preamble is re-usable and could be moved to an include file (yes, LLL has a mechanism for this). It is possible to write LLL code much more compactly, but that makes my eyes hurt, and there's really no efficiency advantage in the compiled code.