From: Prayank <prayank@tutanota•de>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Using transaction version number in different projects
Date: Sun, 29 Aug 2021 11:32:47 +0200 (CEST) [thread overview]
Message-ID: <MiGFGDc--3-2@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
print('Hello, world!')
I had asked related question on Bitcoin Stackexchange: https://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 outcomes:
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 wanted to confirm if everything looks okay until funding transaction. Nothing involves 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 user and other from mempool.
4.Funding transaction will use the version bits to indicate if Alice wants to bet on India or Australia.
--
Prayank
A3B1 E430 2298 178F
[-- Attachment #2: Type: text/html, Size: 1664 bytes --]
next reply other threads:[~2021-08-29 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 9:32 Prayank [this message]
2021-08-29 14:56 ` Pieter Wuille
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=MiGFGDc--3-2@tutanota.de \
--to=prayank@tutanota$(echo .)de \
--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