From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: Russell O'Connor <roconnor@blockstream•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Beyond Jets: Microcode: Consensus-Critical Jets Without Softforks
Date: Tue, 22 Mar 2022 16:47:33 +0000 [thread overview]
Message-ID: <YPjiBkZGybpJua2yLGnibTqJQXEb_7bj-e1Co1O2FX1S6PPyew7hKiLKebrlOPbvxDdQlWuew6EyaQRU8ECnRnAnQ9ELzMtKP6s0vHVuv1k=@protonmail.com> (raw)
In-Reply-To: <b44RnTZqVC01psPp8Iijmj2oGLcm7CnG56UaT5xEvtNkVVOfK4YAka_jf-zey7_Kkou7ewNWbGx9sBDoF3Fu9OA2aL2FCVY4u0ZI6geOCpU=@protonmail.com>
Good morning again Russell,
> Good morning Russell,
>
> > Thanks for the clarification.
> > You don't think referring to the microcode via its hash, effectively using 32-byte encoding of opcodes, is still rather long winded?
For that matter, since an entire microcode represents a language (based on the current OG Bitcoin SCRIPT language), with a little more coordination, we could entirely replace Tapscript versions --- every Tapscript version is a slot for a microcode, and the current OG Bitcoin SCRIPT is just the one in slot `0xc2`.
Filled slots cannot be changed, but new microcodes can use some currently-empty Tapscript version slot, and have it properly defined in a microcode introduction outpoint.
Then indication of a microcode would take only one byte, that is already needed currently anyway.
That does limit us to only 255 new microcodes, thus the cost of one microcode would have to be a good bit higher.
Again, remember, microcodes represent an entire language that is an extension of OG Bitcoin SCRIPT, not individual operations in that language.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2022-03-22 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 5:37 ZmnSCPxj
2022-03-22 15:08 ` Russell O'Connor
2022-03-22 16:22 ` ZmnSCPxj
2022-03-22 16:28 ` Russell O'Connor
2022-03-22 16:39 ` ZmnSCPxj
2022-03-22 16:47 ` ZmnSCPxj [this message]
2022-03-22 23:11 ` Anthony Towns
2022-03-23 0:20 ` ZmnSCPxj
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='YPjiBkZGybpJua2yLGnibTqJQXEb_7bj-e1Co1O2FX1S6PPyew7hKiLKebrlOPbvxDdQlWuew6EyaQRU8ECnRnAnQ9ELzMtKP6s0vHVuv1k=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=roconnor@blockstream$(echo .)com \
/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