public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed

From: Dave Scotese <dscotese@litmocracy•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Masked bits and isStandard
Date: Sat, 10 Oct 2015 14:41:24 -0700	[thread overview]
Message-ID: <CAGLBAhcW2Av7X92LjXk+SjK+Dj4Hw4VapGSoiKQggE6wi4r0kg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

Thanks again.  The description of bits 16..29 as "can take any value"
suggests to me an improvement for isStandard: if any bits "can take any
value" without affecting the script then they must be off for the script to
pass isStandard.

If I understand it correctly, this requirement will serve as a backup to
future uses of those bits if such uses are deployed as soft forks.

I'm sorry if my suggestion reflects a poor understanding of isStandard, but
I offer it as evidence on whether the mechanism is as well understood as it
should be, since we use soft forks.  If I have misunderstood, feel free to
educate me with a reply.

Thanks!
Notplato



On Oct 10, 2015, at 8:22 AM, G1lius Caesar via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:


bits 16..29 are masked off and can take any value.



-- 
I like to provide some work at no charge to prove my value. Do you need a
techie?
I own Litmocracy <http://www.litmocracy.com> and Meme Racing
<http://www.memeracing.net> (in alpha).
I'm the webmaster for The Voluntaryist <http://www.voluntaryist.com> which
now accepts Bitcoin.
I also code for The Dollar Vigilante <http://dollarvigilante.com/>.
"He ought to find it more profitable to play by the rules" - Satoshi
Nakamoto

[-- Attachment #2: Type: text/html, Size: 3230 bytes --]

                 reply	other threads:[~2015-10-10 21:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGLBAhcW2Av7X92LjXk+SjK+Dj4Hw4VapGSoiKQggE6wi4r0kg@mail.gmail.com \
    --to=dscotese@litmocracy$(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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox