From: PJ Fitzpatrick <opensourcepj@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Transaction Coins
Date: Thu, 12 Jul 2018 09:05:42 +0100 [thread overview]
Message-ID: <CAEpNEN4wP3CMtrs1ivj_o+VN95fqaDswXeEq858zyJ03TjxuUA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 646 bytes --]
I am considering a method to derive digital scarcity from bitcoin
transactions. Coins are created from transactions if their hash is among
the closest n to the non zero portion of the block hash. Only a single coin
can be created per transaction irrespective of the size of the transaction.
Therefore n coins are created per block.
The initial coin supply and addresses can be fully determined by the
existing blockchain. Additionally coins are scarce as coins can only be
produced by transactions.
There are a number of variants such as creating computation puzzles from
the previous block.
Has anyone seen anything similar.
PJ Fitzpatrick
[-- Attachment #2: Type: text/html, Size: 1028 bytes --]
next reply other threads:[~2018-07-12 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 8:05 PJ Fitzpatrick [this message]
2018-07-13 0:27 ` [bitcoin-dev] Transaction Coins Jakub Trnka
2018-07-13 10:11 ` PJ Fitzpatrick
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=CAEpNEN4wP3CMtrs1ivj_o+VN95fqaDswXeEq858zyJ03TjxuUA@mail.gmail.com \
--to=opensourcepj@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