[bitcoin-dev] Simplicity proposal - Jets?
roconnor at blockstream.io
Fri Nov 3 01:10:42 UTC 2017
Jets are briefly discussed in section 3.4 of
The idea is that we can recognize some set of popular Simplicity
expressions, and when the Simplicity interpreter encounters one of these
expressions it can skip over the Simplicity interpreter and instead
directly evaluate the function using specialized C or assembly code.
For example, when the Simplicity interpreter encounters the Simplicity
expression for ECDSA verification, it might directly call into libsecp
rather than continuing the ECDSA verification using interpreted Simplicity.
On Nov 2, 2017 18:35, "JOSE FEMENIAS CAÑUELO via bitcoin-dev" <
bitcoin-dev at lists.linuxfoundation.org> wrote:
I am trying to follow this Simplicity proposal and I am seeing all over
references to ‘jets’, but I haven’t been able to find any good reference to
Can anyone give me a brief explanation and or a link pointing to this
On 31 Oct 2017, at 22:01, bitcoin-dev-request at lists.linuxfoundation.org
The plan is that discounted jets will be explicitly labeled as jets in the
commitment. If you can provide a Merkle path from the root to a node that
is an explicit jet, but that jet isn't among the finite number of known
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bitcoin-dev