From: Mark Friedenbach <mark@friedenbach•org>
To: DKBryant@gmail•com,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction aging to relieve user concerns.
Date: Thu, 28 Dec 2017 12:49:38 -0800 [thread overview]
Message-ID: <6A60B31A-41CE-40FF-A604-05EB97CAA3B4@friedenbach.org> (raw)
In-Reply-To: <CAAUFj12x+kRUkcWECesJJRybDsQWfNL_7-D3wYexr6mOUzBY9g@mail.gmail.com>
However users can’t know with any certainty whether transactions will “age out” as indicated, since this is only relay policy. Exceeding the specified timeout doesn’t prevent a miner from including it in the chain, and therefore doesn’t really provide any actionable information.
> On Dec 28, 2017, at 11:55 AM, Dan Bryant via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> The goal here is to make it easier for users to know with better certainty when an TXN is going to age out
prev parent reply other threads:[~2017-12-28 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 19:55 Dan Bryant
2017-12-28 20:49 ` Mark Friedenbach [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=6A60B31A-41CE-40FF-A604-05EB97CAA3B4@friedenbach.org \
--to=mark@friedenbach$(echo .)org \
--cc=DKBryant@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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