From: Jakub Trnka <jakub.trnka@chainanalytics•net>
To: PJ Fitzpatrick <opensourcepj@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction Coins
Date: Thu, 12 Jul 2018 20:27:31 -0400 [thread overview]
Message-ID: <MQZ0Tsu-jXviDYi_QUADbNt91B3yobw1mVziogwRvabhcLT7Oxy-nsKDAKxCDphMlTs-n4U8T4ghDKOM_e7RC_xAeH-of1Uwt5LMF8tzFLc=@chainanalytics.net> (raw)
In-Reply-To: <CAEpNEN4wP3CMtrs1ivj_o+VN95fqaDswXeEq858zyJ03TjxuUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
I think building some overlay scarcity and value on top of bitcoin blockchain would incentivize people to transact a lot. An equilibrium would emerge between paying transaction fees and mining new coins. Which would effectively be equivalent to selling bitcoin and buying some mergemined altcoin, except this would congest the bitcoin network. You can easily borrow scarcity from bitcoin in some sidechain.
Jakub Trnka
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 12 July 2018 10:05 AM, PJ Fitzpatrick via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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: 2106 bytes --]
next prev parent reply other threads:[~2018-07-13 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 8:05 PJ Fitzpatrick
2018-07-13 0:27 ` Jakub Trnka [this message]
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='MQZ0Tsu-jXviDYi_QUADbNt91B3yobw1mVziogwRvabhcLT7Oxy-nsKDAKxCDphMlTs-n4U8T4ghDKOM_e7RC_xAeH-of1Uwt5LMF8tzFLc=@chainanalytics.net' \
--to=jakub.trnka@chainanalytics$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=opensourcepj@gmail$(echo .)com \
/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