public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Bernd Jendrissek <bitcoin@bpj-code.co.za>
To: simondev1 <random@gmx.ch>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] new BIP: Self balancing between excessively low/high fees and block size
Date: Mon, 8 Apr 2019 00:11:55 +0200	[thread overview]
Message-ID: <CAF7PVPrXg2nefBkPH6E1Qz8hvL8JVSn-mCRCK60TtY1NjA-z3w@mail.gmail.com> (raw)
In-Reply-To: <trinity-9a1b0170-a250-4c06-a8e1-0f281499c4da-1554627046019@3c-app-gmx-bs53>

On Sun, 7 Apr 2019 at 17:45, simondev1 via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> ==Implementation==
> Sort transactions by FeeInSatoshiPerByte (lowest first)
> For each transaction starting from lowest FeeInSatoshiPerByte: Sum up the bytes of space used so far. Check if summed up bytes of space used so far is smaller or equal than the formula result.
> If this is valid for each transaction then the blocksize is valid.

Doesn't this break CPFP? I think to avoid that you'll need to rework
your proposed algorithm to treat chains of transactions as a group.
(And note that you could have multiple transactions in one block that
depend on the same "parent" transaction, also in the same block.)


  parent reply	other threads:[~2019-04-07 22:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07  8:50 [bitcoin-dev] new BIP: Self balancing between excessively low/high fees and block size simondev1
2019-04-07 18:52 ` Natanael
2019-04-07 22:11 ` Bernd Jendrissek [this message]
2019-04-12 15:45   ` simondev1
2019-04-08  0:55 ` ZmnSCPxj
2019-04-12 15:49   ` simondev1
2019-04-09  0:13 ` Omar Shibli

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=CAF7PVPrXg2nefBkPH6E1Qz8hvL8JVSn-mCRCK60TtY1NjA-z3w@mail.gmail.com \
    --to=bitcoin@bpj-code.co.za \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=random@gmx.ch \
    /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