public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: Chun Wang <1240902@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Upcoming Transaction Priority Changes
Date: Thu, 12 Nov 2015 20:25:23 +0000	[thread overview]
Message-ID: <201511122025.24518.luke@dashjr.org> (raw)
In-Reply-To: <CAFzgq-xZA7VApQJv-b9n12H+GmL7u4Qv_481UsHWNqXGn6NubA@mail.gmail.com>

On Thursday, November 12, 2015 8:20:45 PM Chun Wang wrote:
> The sort by priority part in the block is always the best place for spam
> nowadays.

What are you saying here? Spammers generally can't use the priority space at 
all, and it is a major way for legitimate users to get their transactions 
mined cheaply despite ongoing spam attempts. You're suggesting the exact 
opposite is true?? Please explain.

Luke


  reply	other threads:[~2015-11-12 20:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 19:47 [bitcoin-dev] Upcoming Transaction Priority Changes Matt Corallo
2015-11-12 20:12 ` Luke Dashjr
2015-11-12 20:20   ` Chun Wang
2015-11-12 20:25     ` Luke Dashjr [this message]
2015-11-12 20:35       ` James Hilliard
2015-11-12 20:43   ` Jorge Timón
2015-11-12 21:10     ` Luke Dashjr
2015-11-12 21:21       ` Alex Morcos
2015-11-12 21:26         ` Luke Dashjr

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=201511122025.24518.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=1240902@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