From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id A2956C002D for ; Wed, 2 Nov 2022 17:30:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 68E7660E5B for ; Wed, 2 Nov 2022 17:30:25 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org 68E7660E5B Authentication-Results: smtp3.osuosl.org; dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com header.i=@q32-com.20210112.gappssmtp.com header.a=rsa-sha256 header.s=20210112 header.b=JzHMSIG2 X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztVlk0nEkNKG for ; Wed, 2 Nov 2022 17:30:24 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org A6DDA60B5A Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) by smtp3.osuosl.org (Postfix) with ESMTPS id A6DDA60B5A for ; Wed, 2 Nov 2022 17:30:24 +0000 (UTC) Received: by mail-vs1-xe2b.google.com with SMTP id v129so17996342vsb.3 for ; Wed, 02 Nov 2022 10:30:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6xwj81uj5hWO26/lkgcauxRFwd7O7DqeDBUyOXoCjnE=; b=JzHMSIG2gEIAwJS09hm3BFQWLYQjat26qVZ/ReXuJNZgMFEy+EeMsP9Sux7u8mr8wV ZTcY5HvwIZ1pBPXPSfGMHEj4oC62898Pn4KW8ocR852Hxk9Hr+jsgHiS1PXqDH5//0ud 4HOKJRRuOubEOiTKOJCtJB3irZq4/jLcnMtFib93HL85jhA73KNmomHbUKctW8GrZJ88 16VygB2FXN75peZoGrdITYMPTQpCdtPtJ1ujp2a2BhVw3QzmiK1/3TkcZN5ND0DRro/G SolRE28nASzgbdfrQJv+K+Tp3pdz+tHjW3dF9vOczgcQ+uGb657dc5jxRLLyxarb8XIZ bezQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=6xwj81uj5hWO26/lkgcauxRFwd7O7DqeDBUyOXoCjnE=; b=RZPBaC4/JVjQDffi30Otn43nPb43a2ng09SolkZEdeNDIdUMrivxjRIrE9LLYcKNsQ uLbjrFJvGHnOV/gzDXjyjAYBny0O0s6X4eviuOzMb28ljSdv2q+wCXGhkA2P4TOYN0h9 FtuaPmHijDAYBCw8bDhe8KwX8BwteUfCiCDxxtt7P+xHYU+qqn81JV9L556nsZ8fX/2F DsBmt8tIjcf70cWgHv5ykMM79S8mH//uD9dmnQhrrzx4c+22thWjunQHYGeLuzzSa5sY pjdZG9o1wRXZwqKaiYoDNN3S+mg64BuLU/g9oVSW5x1ez0kpQJ7PBCj/K30i2gTXLuft xtOw== X-Gm-Message-State: ACrzQf3/lU2ehH5SAONCMSqq37j8ki0US5/NUbkZ2DOcg77pGRRMvwsV w1RACnwu/CFZp99otZrZnpzLXsf9aG+5K1w0ILt+x3s= X-Google-Smtp-Source: AMsMyM5cc8Uol2pNuQe8i9IxVa+6tNiIrblHaanHdHEN97/Dy1r85ZwIXQXlPq0cvEDUq3LiFc5Ds0cOLVh7TV/vzNA= X-Received: by 2002:a05:6102:14aa:b0:3ac:b1ee:5529 with SMTP id d42-20020a05610214aa00b003acb1ee5529mr11658544vsv.40.1667410223329; Wed, 02 Nov 2022 10:30:23 -0700 (PDT) MIME-Version: 1.0 References: <6016816a7ea36b8a88f48d69462d0308@riseup.net> <0555e82561666007e7ce367e3a204f53@riseup.net> In-Reply-To: From: Erik Aronesty Date: Wed, 2 Nov 2022 13:30:13 -0400 Message-ID: To: s7r , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="0000000000000e77a605ec80320a" X-Mailman-Approved-At: Wed, 02 Nov 2022 17:41:24 +0000 Subject: Re: [bitcoin-dev] Boost Bitcoin circulation, Million Transactions Per Second with stronger privacy 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: Wed, 02 Nov 2022 17:30:25 -0000 --0000000000000e77a605ec80320a Content-Type: text/plain; charset="UTF-8" > > (the only way to replace a transaction is Replace-By-Fee but this > implies the transaction that IS TO BE REPLACED has a certain flag set, > and it is optional). > 1. full rbf is becoming standard. tx without full rbf can just be rejected as a part of the sabu protocol 2. that's fine. watchtowers can be used to fix this that only have the ability to stop attacks in progress. guarantee transactions can include a small watchtower fee for your favorite always-on watchtower service 3. all parties need to maintain sabu state (it's just another mempool) --0000000000000e77a605ec80320a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
(the only way to replace a transaction is Replace-By-Fee= but this
implies the transaction that IS TO BE REPLACED has a certain f= lag set,
and it is optional).

1. full rbf is be= coming standard.=C2=A0 =C2=A0tx without full rbf can just be rejected as a = part of the sabu protocol
=C2=A0
2. that's fine.=C2=A0 wat= chtowers can be used to fix this that only have the ability to stop attacks= in progress.=C2=A0 =C2=A0guarantee transactions can include a small watcht= ower fee for your favorite always-on watchtower service

3. all parties need to maintain sabu state (it's just another=C2= =A0mempool)


--0000000000000e77a605ec80320a--