Author: Mark Friedenbach 2017-11-03 16:19:39
Published on: 2017-11-03T16:19:39+00:00
The Simplicity proposal discusses the use of 'jets' in section 3.4, which allows for recognition of popular Simplicity expressions. When the Simplicity interpreter encounters one of these expressions, it can skip over the Simplicity interpreter and directly evaluate the function using specialized C or assembly code. This would save space on the blockchain as large algorithms, such as EDCA verification/SHA256 hashing, would not need to be publicly available/visible in the blockchain. The idea is that discounted jets will be explicitly labeled as jets in the commitment. These jets would have to be specified and agreed to upfront for costing reasons, and so they would be known to all validators. There would be no reason to include anything more than the identifying hash in any contract using the jet. In a softfork for a jet, the Simplicity code for a jet could be defined as "consensus", instead of needing to be provided within every script output. When the Simplicity interpretor encounters an expression that has a jet, it would run the C/Assembly code instead of interpreting the Simplicity code. By formal verification, it would be ensured that they match.
Updated on: 2023-06-12T21:57:40.584023+00:00