public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: PJ Fitzpatrick <opensourcepj@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Transaction Coins
Date: Fri, 13 Jul 2018 11:11:27 +0100	[thread overview]
Message-ID: <CAEpNEN476OWtUNL3=7GQEwLTZ1wXZjKkOtgx+q-MS-F3-x_ktw@mail.gmail.com> (raw)
In-Reply-To: <MQZ0Tsu-jXviDYi_QUADbNt91B3yobw1mVziogwRvabhcLT7Oxy-nsKDAKxCDphMlTs-n4U8T4ghDKOM_e7RC_xAeH-of1Uwt5LMF8tzFLc=@chainanalytics.net>

[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]

On Fri, Jul 13, 2018 at 1:27 AM Jakub Trnka <jakub.trnka@chainanalytics.net>
wrote:

> 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.
>

Yes  what you say is correct. Therefore n could be a function of the
transaction fees of the block. I think this should be on bitcointalk and I
am going to start a discussion there.
PJ Fitzpatrick


> 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: 3004 bytes --]

      reply	other threads:[~2018-07-13 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12  8:05 [bitcoin-dev] Transaction Coins PJ Fitzpatrick
2018-07-13  0:27 ` Jakub Trnka
2018-07-13 10:11   ` PJ Fitzpatrick [this message]

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='CAEpNEN476OWtUNL3=7GQEwLTZ1wXZjKkOtgx+q-MS-F3-x_ktw@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