From: Mike Brooks <m@ib•tc>
To: bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Smaller Transactions with PubRef
Date: Fri, 31 Jul 2020 22:09:25 -0700 [thread overview]
Message-ID: <CALFqKjTDcsD4xpc-TryTRCNnCJivyqkU9dv0ff2emP5kxZF1bA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
The attached BIP describes a new opcode that unlocks the ability to have
transactions that are about 37% smaller than a traditional single-source
segwit transaction. (Savings vary based on the number of inputs.)
The pursuit of smaller transactions is vital for Inclusive Accountability
as less data needs to be recorded on chain. Frugality is improved in two
ways; more transactions can be confirmed in a block, and small value
inputs otherwise inaccessible can now be referenced without losing
unrecoverable value due to transaction overhead.
https://github.com/TheRook/bip-pubref/blob/master/bip-PubRef.mediawiki
The variant of this technology on the ethereum side is Ditto Transactions:
https://ethereum-magicians.org/t/eip-ditto-transactions/4455
[-- Attachment #2: Type: text/html, Size: 1033 bytes --]
next reply other threads:[~2020-08-01 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 5:09 Mike Brooks [this message]
2020-08-02 0:36 ` ZmnSCPxj
2020-08-02 1:12 ` Mike Brooks
2020-08-02 14:22 ` 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=CALFqKjTDcsD4xpc-TryTRCNnCJivyqkU9dv0ff2emP5kxZF1bA@mail.gmail.com \
--to=m@ib$(echo .)tc \
--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