From: Dave Scotese <dscotese@litmocracy.com>
To: Vincent Truong <vincent.truong@procabiak.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Days Destroyed as block selection heuristic
Date: Sat, 12 Sep 2015 11:55:03 -0700 [thread overview]
Message-ID: <CAGLBAhfPckVHgTRXYck2xiS79CMyJdHZ4ej0_fGr=RchbrP5dA@mail.gmail.com> (raw)
In-Reply-To: <CACrzPe=kDVJHDMgyuFvVcPf1FbfzLbDYFKxzaxtdWnvkJ=HpLQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
>
> From the Bitcoin wiki page on transaction fees
> <https://en.bitcoin.it/wiki/Transaction_fees#Technical_info>:
>
> Transaction priority is calculated as a value-weighted sum of input age,
> divided by transaction size in bytes: priority =
> sum(input_value_in_base_units * input_age)/size_in_bytes
>
If I read that correctly, that is directly proportional to BTCDD, so
whatever effect concerns you has already been built into the code.
On Fri, Sep 11, 2015 at 3:21 PM, Vincent Truong <
vincent.truong@procabiak.com> wrote:
> Would this alter the way txns will be prioritised in order to try to win?
> You would always pick txns with the best BTCDD to maximize your chances of
> being the block to build on.
>
> I see this as potentially being a bad outcome for bitcoin's fungibility.
>
[-- Attachment #2: Type: text/html, Size: 1415 bytes --]
prev parent reply other threads:[~2015-09-12 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 16:27 [bitcoin-dev] Bitcoin Days Destroyed as block selection heuristic Dave Scotese
2015-09-11 16:32 ` Jorge Timón
2015-09-11 17:18 ` Christophe Biocca
2015-09-11 18:37 ` Jorge Timón
2015-09-11 19:06 ` Christophe Biocca
2015-09-11 19:26 ` Dave Scotese
2015-09-11 22:21 ` Vincent Truong
2015-09-12 18:55 ` Dave Scotese [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='CAGLBAhfPckVHgTRXYck2xiS79CMyJdHZ4ej0_fGr=RchbrP5dA@mail.gmail.com' \
--to=dscotese@litmocracy.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=vincent.truong@procabiak.com \
/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