Date: Sun, 29 Aug 2021 11:32:47 +0200 (CEST)
From: Prayank <prayank@tutanota.de>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <MiGFGDc--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_454059_1302865444.1630229567375"
Subject: [bitcoin-dev] Using transaction version number in different projects
Precedence: list

------=_Part_454059_1302865444.1630229567375
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

print('Hello, world!')

I had asked related question on Bitcoin Stackexchange:=C2=A0https://bitcoin=
.stackexchange.com/questions/108248/version-in-transaction

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 out=
comes:

https://gist.github.com/prayank23/6f54e9a27f057abd1182436e7f88d1ac

Anything wrong with this approach? We could use oracles (DLC) or something =
else later to settle the bet and create a release transaction. However want=
ed to confirm if everything looks okay until funding transaction. Nothing i=
nvolves any centralized server or trusting third parties:
1.Tx1 is a normal OP_RETURN transaction.
2.App will save results for `getrawmempool` regularly in local db. It will =
check if any transaction wants to participate in bets.
3.Multisig address will be created using two public keys. One entered by us=
er and other from mempool.
4.Funding transaction will use the version bits to indicate if Alice wants =
to bet on India or Australia.


--=20
Prayank

A3B1 E430 2298 178F

------=_Part_454059_1302865444.1630229567375
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=
">
  </head>
  <body>
<div>print('Hello, world!')<br></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">I had asked related question on Bitcoin Stackexchange:&nbsp;https=
://bitcoin.stackexchange.com/questions/108248/version-in-transaction<br></d=
iv><div dir=3D"auto"><br></div><div dir=3D"auto">Wanted to know if others t=
hink we should allow more numbers in transaction version by considering suc=
h transaction standard. I have shared an example how transaction version ca=
n be used to bet on something that involves 2 outcomes:<br><br></div><div d=
ir=3D"auto">https://gist.github.com/prayank23/6f54e9a27f057abd1182436e7f88d=
1ac<br><br>Anything wrong with this approach? We could use oracles (DLC) or=
 something else later to settle the bet and create a release transaction. H=
owever wanted to confirm if everything looks okay until funding transaction=
. Nothing involves any centralized server or trusting third parties:</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">1.Tx1 is a normal OP_RETURN tr=
ansaction.<br></div><div dir=3D"auto">2.App will save results for `getrawme=
mpool` regularly in local db. It will check if any transaction wants to par=
ticipate in bets.<br></div><div dir=3D"auto">3.Multisig address will be cre=
ated using two public keys. One entered by user and other from mempool.<br>=
</div><div dir=3D"auto">4.Funding transaction will use the version bits to =
indicate if Alice wants to bet on India or Australia.<br></div><div dir=3D"=
auto"><br></div><div><br></div><div>-- <br></div><div>Prayank<br></div><div=
><br></div><div dir=3D"auto">A3B1 E430 2298 178F<br></div>  </body>
</html>

------=_Part_454059_1302865444.1630229567375--