From: "Adán Sánchez de Pedro Crespo" <adan@stampery•co>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Simplicity proposal - Jets?
Date: Fri, 3 Nov 2017 09:46:16 +0100 [thread overview]
Message-ID: <7d3a97f7-37c0-3eb6-6f39-00bd99c36132@stampery.com> (raw)
In-Reply-To: <CAMZUoKk+8MFLywQB3jQFkk7BYZ4Rw3Paj=ErQe8pZ0beGwu0RA@mail.gmail.com>
Oops. That makes much more sense than what I said. Thanks a lot for the
clarification.
On 03.11.2017 02:10, Russell O'Connor via bitcoin-dev wrote:
> 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@lists•linuxfoundation.org
> <mailto:bitcoin-dev@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@lists•linuxfoundation.org
>> <mailto:bitcoin-dev-request@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@lists•linuxfoundation.org
> <mailto:bitcoin-dev@lists•linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
Adán Sánchez de Pedro Crespo
CTO, Stampery Inc.
San Francisco - Madrid
next prev parent reply other threads:[~2017-11-03 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5469.1509483670.27509.bitcoin-dev@lists.linuxfoundation.org>
2017-11-01 10:34 ` JOSE FEMENIAS CAÑUELO
2017-11-03 0:45 ` Adán Sánchez de Pedro Crespo
2017-11-03 1:10 ` Russell O'Connor
2017-11-03 8:46 ` Adán Sánchez de Pedro Crespo [this message]
2017-11-03 12:59 ` Hampus Sjöberg
2017-11-03 16:19 ` Mark Friedenbach
2017-11-03 16:42 ` Adán Sánchez de Pedro Crespo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d3a97f7-37c0-3eb6-6f39-00bd99c36132@stampery.com \
--to=adan@stampery$(echo .)co \
--cc=adan@stampery$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox