Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id F0D02B9E for ; Mon, 20 May 2019 21:06:40 +0000 (UTC) X-Greylist: delayed 00:08:22 by SQLgrey-1.7.6 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 678FC7ED for ; Mon, 20 May 2019 21:06:40 +0000 (UTC) Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x4KKwFl6027420 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 20 May 2019 16:58:16 -0400 Received: by mail-ed1-f53.google.com with SMTP id f37so25755872edb.13 for ; Mon, 20 May 2019 13:58:16 -0700 (PDT) X-Gm-Message-State: APjAAAVkLxjmLP6gKBqbhP7blmi06HrpFOAFWJA1V2BvLQCCbuoM9CNi ElYz+eDuIiAMhX1oKryoFocrSlZuXpvTCX7wGdQ= X-Google-Smtp-Source: APXvYqwBB+YJwE7JCVbEIBanDYZehlME7kQ2TagVYqw25u9lDgQvKAl+OBGqSGOrACU0LLg4RhKH0D8FvLeAJJb3KKY= X-Received: by 2002:a50:ba1d:: with SMTP id g29mr24079097edc.298.1558385895209; Mon, 20 May 2019 13:58:15 -0700 (PDT) MIME-Version: 1.0 From: Jeremy Date: Mon, 20 May 2019 13:58:03 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Bitcoin development mailing list Content-Type: multipart/alternative; boundary="000000000000b500b6058957fd2d" X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 21 May 2019 18:36:00 +0000 Subject: [bitcoin-dev] Congestion Control via OP_CHECKOUTPUTSHASHVERIFY proposal X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2019 21:06:41 -0000 --000000000000b500b6058957fd2d Content-Type: text/plain; charset="UTF-8" Hello bitcoin-devs, Below is a link to a BIP Draft for a new opcode, OP_CHECKOUTPUTSHASHVERIFY. This opcode enables an easy-to-use trustless congestion control techniques via a rudimentary, limited form of covenant which does not bear the same technical and social risks of prior covenant designs. Congestion control allows Bitcoin users to confirm payments to many users in a single transaction without creating the UTXO on-chain until a later time. This therefore improves the throughput of confirmed payments, at the expense of latency on spendability and increased average block space utilization. The BIP covers this use case in detail, and a few other use cases lightly. The BIP draft is here: https://github.com/JeremyRubin/bips/blob/op-checkoutputshashverify/bip-coshv.mediawiki The BIP proposes to deploy the change simultaneously with Taproot as an OPSUCCESS, but it could be deployed separately if needed. An initial reference implementation of the consensus changes and tests which demonstrate how to use it for basic congestion control is available at https://github.com/JeremyRubin/bitcoin/tree/congestion-control. The changes are about 74 lines of code on top of sipa's Taproot reference implementation. Best regards, Jeremy Rubin --000000000000b500b6058957fd2d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello bitcoin-devs,

Below is a link to a BIP Draft for a new opcode, OP_CHECKOUTPUTSHASHVER= IFY. This opcode enables an easy-to-use trustless congestion control techni= ques via a rudimentary, limited form of covenant which does not bear the sa= me technical and social risks of prior covenant designs.

Congesti= on control allows Bitcoin users to confirm payments to many users in a sing= le transaction without creating the UTXO on-chain until a later time. This = therefore improves the throughput of confirmed payments, at the expense of = latency on spendability and increased average block space utilization. The = BIP covers this use case in detail, and a few other use cases lightly.
<= /div>

The BIP draft is here:

T= he BIP proposes to deploy the change simultaneously with Taproot as an OPSU= CCESS, but it could be deployed separately if needed.

An = initial reference implementation of the consensus changes and=C2=A0 tests w= hich demonstrate how to use it for basic congestion control is available at= https://github.com/JeremyRubin/bitcoin/tree/congestion-control.=C2=A0 = The changes are about 74 lines of code on top of sipa's Taproot referen= ce implementation.

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ;font-size:small;color:rgb(0,0,0)">Best regards,

Jeremy Rubin
--000000000000b500b6058957fd2d--