Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 8821AC000B for ; Thu, 10 Feb 2022 23:52:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 5986340291 for ; Thu, 10 Feb 2022 23:52:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvQeN93U1dan for ; Thu, 10 Feb 2022 23:52:01 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) by smtp2.osuosl.org (Postfix) with ESMTPS id 18F5F401C9 for ; Thu, 10 Feb 2022 23:52:01 +0000 (UTC) Received: by mail-yb1-xb35.google.com with SMTP id o19so20017809ybc.12 for ; Thu, 10 Feb 2022 15:52:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sURubZ7KYypKjuXaxzWz3DmNp/kVrvNDC/QuHIhE7s8=; b=CbFi7XxYfYSjMX7OGKivnzqrUbW+L0Zvmrj6KOqLUzEYvacDl8xEt6Uzq5/mrmWVn+ GvKVntlQcSRII1FQxGXnaKWscvA2rdnzsDsPXx0NIDCM/euxveu2O4YyMYtbOBC7M4Jl ZFOkOgP2NJHux0s/nTHYxV/rtLbNWWWU1+qnZ6VBM0BP2bPTi0mCrrrrBLXYEJ5u1Wjk 8x9rKnEzf6AW3+urVjE40aOorsLyg8IhToEaUx14EjO1OAUY3KDux7baJFDIiNiHPm8d 5xFCfWmE9eb/VVvLQOcpsrg+tPvTVAINf0yB7sdjeR/3lrX758qB9CffqfYCVNQnZZs/ 6+lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sURubZ7KYypKjuXaxzWz3DmNp/kVrvNDC/QuHIhE7s8=; b=TbD348zldMFAUjZqP/tGdpY7KU7cbxXWc6j551GJbiTUR+Q51nZAPEAJB9BgQuSvIQ psX7UikB1XzJ9Obl3pv1Ev0r24bGMxMLoOL5vtyLHahGOC1pZakYnyc3MCwRZTKMyBrc uorW3dazEhXOHaNqLv4FJdeoElAyJWKBcffREGCuri2K6XXBBNjBBCnu08jFtn+3uehr Yp8CYA2gNyH3J7+D2CC1XKv3SUnbJkRHk47uO8KQoXXC79Dh+G7gq5zC2r/8h7jN3dcw Iue63npdJWsWUnYGf4dM9tTllVgB8eNaPWSPJkZrch4tWDP7Vid8AT25pWwH8nuvCvq+ R+gw== X-Gm-Message-State: AOAM532c88h9z4gy/BontpPpGI3MU1MR1ksoyAeOXxznTMTpd3SyhBXn e2rgXe6L8IpVAGRPaVET93zqYx9o3pSp7ESS9VwBju6RthrjAw== X-Google-Smtp-Source: ABdhPJzaQ7F9C4CMPj0VE4mSU7gul0yhXN55YvGaR3XjlQFIMz5YyqeKXb5I5nGZVCilmmh+DMc8bfv2b7EvGWWNv1w= X-Received: by 2002:a25:d846:: with SMTP id p67mr8960482ybg.618.1644537119865; Thu, 10 Feb 2022 15:51:59 -0800 (PST) MIME-Version: 1.0 References: <9Vw6LCkr2d2uOBanXeIuGxA1fUGGOeV1OHlgBifbmij1Afs0ISjfKK-vmcnRZfBG4GwJhIVLMisjvS_zohS-cW0FkzZaCKa6Mn7VWolznJs=@protonmail.com> In-Reply-To: <9Vw6LCkr2d2uOBanXeIuGxA1fUGGOeV1OHlgBifbmij1Afs0ISjfKK-vmcnRZfBG4GwJhIVLMisjvS_zohS-cW0FkzZaCKa6Mn7VWolznJs=@protonmail.com> From: "James O'Beirne" Date: Thu, 10 Feb 2022 18:51:47 -0500 Message-ID: To: darosior Content-Type: multipart/alternative; boundary="000000000000d97f4a05d7b2a231" Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Thoughts on fee bumping X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Feb 2022 23:52:02 -0000 --000000000000d97f4a05d7b2a231 Content-Type: text/plain; charset="UTF-8" > It's not that simple. As a miner, if i have less than 1vMB of transactions in my mempool. I don't want a 10sats/vb transaction paying 100000sats by a 100sats/vb transaction paying only 10000sats. I don't understand why the "<1vMB in the mempool" case is even worth consideration because the miner will just include the entire mempool in the next block regardless of feerate. --000000000000d97f4a05d7b2a231 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> It's not that simple. As a miner, if i have less = than 1vMB of=20 transactions in my mempool. I don't want a 10sats/vb transaction paying= =20 100000sats by a 100sats/vb transaction paying only 10000sats.

I don't understand why the "<1vMB in the mempool" ca= se is even worth consideration because the miner will just include the enti= re mempool in the next block regardless of feerate.
--000000000000d97f4a05d7b2a231--