From: Pieter Wuille <bitcoin-dev@wuille•net>
To: Prayank <prayank@tutanota•de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Using transaction version number in different projects
Date: Sun, 29 Aug 2021 14:56:16 +0000 [thread overview]
Message-ID: <yOqiOQR1CIkTZxaWD4RtISMbpaDldcI0gBENXJj3blXBOuK2nDROxa6hECucO01mTpNcZtwqqzXwrVf8aC2YpFr7lznBxc2xKqiBECvVkzw=@wuille.net> (raw)
In-Reply-To: <MiGFGDc--3-2@tutanota.de>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
On Sunday, August 29th, 2021 at 5:32 AM, Prayank via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> Wanted to know if others think we should allow more numbers in transaction version by considering such transaction standard. I have shared an example how transaction version can be used to bet on something that involves 2 outcomes:
> https://gist.github.com/prayank23/6f54e9a27f057abd1182436e7f88d1ac
I can't say I understand what you're suggesting, or what transaction version numbers have to do with it, so take the following with the caveat that I may be missing your point.
Generally, my view is that Bitcoin transactions should solely contain the information necessary for the world to validate them. Given that, as of now, there are no consensus rules (or even generally-adopted relay policies) that care about the version number except it being 1 or 2 (due to BIP68), I would say that the usage of anything but those 2 possible numbers is both pointless and a gratuitous loss of privacy: for numbers with no protocol-defined meaning, the usage of an uncommon one reveals something to the world that should be privately communicated to the parties involved instead.
Combined with the fact that currently-unused version numbers may well be used for future consensus rules like BIP68, which any use you're suggesting may interfere with, I say no: versions numbers with no protocol-defined meaning should not be standard. They are reserved for future extensions.
Cheers,
--
Pieter
[-- Attachment #2: Type: text/html, Size: 1919 bytes --]
prev parent reply other threads:[~2021-08-29 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 9:32 Prayank
2021-08-29 14:56 ` Pieter Wuille [this message]
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='yOqiOQR1CIkTZxaWD4RtISMbpaDldcI0gBENXJj3blXBOuK2nDROxa6hECucO01mTpNcZtwqqzXwrVf8aC2YpFr7lznBxc2xKqiBECvVkzw=@wuille.net' \
--to=bitcoin-dev@wuille$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=prayank@tutanota$(echo .)de \
/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