📅 Original date posted:2017-11-03
📝 Original message:Thank you for your answer, Russel.
When a code path takes advantage of a jet, does the Simplicity code still
need to be publicly available/visible in the blockchain? I imagine that for
big algorithms (say for example EDCA verification/SHA256 hashing etc), it
would take up a lot of space in the blockchain.
Is there any way to mitigate this?
I guess in a softfork for a jet, the Simplicity code for a jet could be
defined as "consensus", instead of needed 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 we would be sure they match.
Greetings
Hampus
2017-11-03 2:10 GMT+01:00 Russell O'Connor via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org>:
> Hi Jose,
>
> Jets are briefly discussed in section 3.4 of https://blockstream.com/
> simplicity.pdf
>
> 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.
>
> HTH.
>
>
> On Nov 2, 2017 18:35, "JOSE FEMENIAS CAÑUELO via bitcoin-dev" <
> bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> Hi,
>
> 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
> it.
> Can anyone give me a brief explanation and or a link pointing to this
> feature?
> Thanks
>
> On 31 Oct 2017, at 22:01, bitcoin-dev-request at lists.linuxfoundation.org
> wrote:
>
> 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
> discounted jets,
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171103/e9a5e8b1/attachment-0001.html>;
Hampus Sjöberg [ARCHIVE] /
npub10u…hln8t
2023-06-07 18:07:29
in reply to nevent1q…llcz
Author Public Key
npub10uzud4rf4636awmfgvarmcfndcmdnv8rfd2y3rx2sqgckv9zur4qahln8tPublished at
2023-06-07 18:07:29Event JSON
{
"id": "672872dd41b020a1a2a4198dfb5fb074dd199537db3a5571be1220b79d80e02e",
"pubkey": "7f05c6d469aea3aebb69433a3de1336e36d9b0e34b54488cca80118b30a2e0ea",
"created_at": 1686161249,
"kind": 1,
"tags": [
[
"e",
"f66293ea7a9b32888732d42282e8e2d2c8c37fd29a8c31abaf65ab4ee416ee28",
"",
"root"
],
[
"e",
"9728a4728013423a41a3b49835d54df898609ab38d8bf8b45c2a840bd45552e2",
"",
"reply"
],
[
"p",
"42c901fccda418477337afb5eb8e517266652306539ab9ced7196d4f3477bd14"
]
],
"content": "📅 Original date posted:2017-11-03\n📝 Original message:Thank you for your answer, Russel.\n\nWhen a code path takes advantage of a jet, does the Simplicity code still\nneed to be publicly available/visible in the blockchain? I imagine that for\nbig algorithms (say for example EDCA verification/SHA256 hashing etc), it\nwould take up a lot of space in the blockchain.\nIs there any way to mitigate this?\n\nI guess in a softfork for a jet, the Simplicity code for a jet could be\ndefined as \"consensus\", instead of needed to be provided within every\nscript output.\nWhen the Simplicity interpretor encounters an expression that has a jet, it\nwould run the C/Assembly code instead of interpreting the Simplicity code.\nBy formal verification we would be sure they match.\n\nGreetings\nHampus\n\n2017-11-03 2:10 GMT+01:00 Russell O'Connor via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e:\n\n\u003e Hi Jose,\n\u003e\n\u003e Jets are briefly discussed in section 3.4 of https://blockstream.com/\n\u003e simplicity.pdf\n\u003e\n\u003e The idea is that we can recognize some set of popular Simplicity\n\u003e expressions, and when the Simplicity interpreter encounters one of these\n\u003e expressions it can skip over the Simplicity interpreter and instead\n\u003e directly evaluate the function using specialized C or assembly code.\n\u003e\n\u003e For example, when the Simplicity interpreter encounters the Simplicity\n\u003e expression for ECDSA verification, it might directly call into libsecp\n\u003e rather than continuing the ECDSA verification using interpreted Simplicity.\n\u003e\n\u003e HTH.\n\u003e\n\u003e\n\u003e On Nov 2, 2017 18:35, \"JOSE FEMENIAS CAÑUELO via bitcoin-dev\" \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\n\u003e Hi,\n\u003e\n\u003e I am trying to follow this Simplicity proposal and I am seeing all over\n\u003e references to ‘jets’, but I haven’t been able to find any good reference to\n\u003e it.\n\u003e Can anyone give me a brief explanation and or a link pointing to this\n\u003e feature?\n\u003e Thanks\n\u003e\n\u003e On 31 Oct 2017, at 22:01, bitcoin-dev-request at lists.linuxfoundation.org\n\u003e wrote:\n\u003e\n\u003e The plan is that discounted jets will be explicitly labeled as jets in the\n\u003e commitment. If you can provide a Merkle path from the root to a node that\n\u003e is an explicit jet, but that jet isn't among the finite number of known\n\u003e discounted jets,\n\u003e\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171103/e9a5e8b1/attachment-0001.html\u003e",
"sig": "ed214a0741e38d4e988f50eed72493c2ca9dd6558f2a726736a1dc001bb424201ee378e1bdfd499bdb09c89d1e5b9829d937d9c458acb6739ffb6621fab7ea98"
}