From: Mostafa Sedaghat joo <mostafa.sedaghat@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Stamping transaction
Date: Fri, 5 Jun 2020 20:05:20 +0800 [thread overview]
Message-ID: <CAJr8eKuFv7R-1HRft-hLFTSdpWUL2uOtkDtisL2+iPaEvvH_hA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Hi
*stamping transactions* is as simple idea but has huge impact.
Simply, stamping transaction means putting previous block hash in the
header of the transaction. With this simple technique we can *decouple
*translation from
the block.
I have described my idea here:
https://b00f.github.io/blockchain/stamping_transactions
I know bitcoin developers tends to not change the core, but you can
consider it for next big change.
Regards,
Mostafa
[-- Attachment #2: Type: text/html, Size: 1035 bytes --]
next reply other threads:[~2020-06-05 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 12:05 Mostafa Sedaghat joo [this message]
2020-06-07 0:40 ` [bitcoin-dev] Stamping transaction ZmnSCPxj
2020-06-07 7:27 ` Mostafa Sedaghat joo
2020-06-07 15:01 ` ZmnSCPxj
2020-06-09 9:34 ` Mostafa Sedaghat joo
2020-06-09 14:16 ` Chris Riley
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=CAJr8eKuFv7R-1HRft-hLFTSdpWUL2uOtkDtisL2+iPaEvvH_hA@mail.gmail.com \
--to=mostafa.sedaghat@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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