Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 3F4961100 for ; Wed, 30 May 2018 16:17:51 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ot0-f177.google.com (mail-ot0-f177.google.com [74.125.82.177]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DCD6C224 for ; Wed, 30 May 2018 16:17:50 +0000 (UTC) Received: by mail-ot0-f177.google.com with SMTP id g7-v6so21778568otj.11 for ; Wed, 30 May 2018 09:17:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=pQCNCaR0IylnKzfQimBhr9rv1u7aGxjVyou3XHeBAHc=; b=EcVhz1yG56EihLiwFrF0c4Ph/ZABKc0sRZVLPgHQTBn+Kt1MOYuGtVbPwr61MPD59W dKVLyTa7zXDFD0cQbzjoHUSLHOFrh98DEdlPmE7vGQFPf96RbWlMUkKnsprfW5V3befO Et6yNr15enX4hwZJU7WR8G77jiaiA2z43f6qTcAB/LZHbmQQ4EhxMo6RXKJm+ff5PV2j Mi4HSe3k0MZ5nfH61kyD94Mv6i3NsnIGi5HsATTjJLZvreCWbD4Kt144xLzubUWKrzRG hs41c7Pw8HEAWB3rHZrsT0KqVMfGKvG/VlFTKmQaAAsieSYZp9dne7/V35IrSIjPGq+H LpUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=pQCNCaR0IylnKzfQimBhr9rv1u7aGxjVyou3XHeBAHc=; b=PPLzr4jEBI5INki3q+C7KYx2CBDPGDcHEgEIwLUeP7d1GA/JcZurodaqv6ORcUdWqL lx54SW6a0wjiqiOHrLJ+29TBtyZzzZyrebUiFltyWq28nx1OPZ+Qqyq78rL49Vdc1SOx 6cCZ71e6Bqtrxolb+VidqppwrXfcOXpRYwwvZgBT1pKlyxlXr7EvhhoopNhXvgSb31kE luw86wT+5NgAfwCsUEJEoKvBT8lOzoMi2IuVFCjYlk7ly2tNunDqlnl73PVH7KC3yiNB /po+62iCcSr60Cxfio1UyJeiBfTCEh4nEZ3v932H9TzXIWBIHWXmSAoRD5D9WAGsO6LI JLIw== X-Gm-Message-State: ALKqPwdADc4X4EGPYviRt3jSEoGo3CVp5rRHTJWqF68R48SuQT/yCAZG KKrWrECGOjujP8x2VLAzYx6afHLRvLU43dr7N5d2fsQ0 X-Google-Smtp-Source: ADUXVKLQDK20+nfCIEp0uiztT5errvB9DMxIxwgui6kSZUDe/aLIZ1HdwSMwT1M+6pHslulxDkNj14AxfSI+QxbCyWc= X-Received: by 2002:a9d:1ba6:: with SMTP id z35-v6mr2294649otd.216.1527697070055; Wed, 30 May 2018 09:17:50 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:4a85:0:0:0:0:0 with HTTP; Wed, 30 May 2018 09:17:29 -0700 (PDT) From: Darren Weber Date: Wed, 30 May 2018 09:17:29 -0700 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="0000000000002f6701056d6eb10a" X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE 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: Thu, 31 May 2018 14:41:44 +0000 Subject: [bitcoin-dev] BIP suggestion: PoW proportional to block transaction sum 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: Wed, 30 May 2018 16:17:51 -0000 --0000000000002f6701056d6eb10a Content-Type: text/plain; charset="UTF-8" Apologies for brevity, noob here and just throwing out an idea in case it's useful (probably already covered somewhere, but I haven't got time to do all the necessary background research). From https://github.com/bitcoin/bitcoin/issues/13342 Suggestion: To make it more difficult for a malicious attacker to reap quick rewards by double-spending large amounts with a relatively brief majority of the network hashing power, introduce a hash workload that is proportional to the sum of transactions in a block (probably the sum of the absolute values, and a "proportionality function" could be linear or exponential). The motivation is to make it more difficult for malicious attacks to hash-power their way through a few large transactions. Obviously, there are costs in greater transaction delays (and fees?) for larger amounts (absolute value). If there is original value in the idea, I can try to make time to follow-up with a better BIP proposal. -- Darren --0000000000002f6701056d6eb10a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Apologies for brevity, noob here and j= ust throwing out an idea in case it's useful (probably already covered = somewhere, but I haven't got time to do all the necessary background re= search).


Suggestion:=C2=A0 To make it more difficult f= or a malicious attacker to reap quick rewards by double-spending large amou= nts with a relatively brief majority of the network hashing power, introduc= e a hash workload that is proportional to the sum of transactions in a bloc= k (probably the sum of the absolute values, and a "proportionality fun= ction" could be linear or exponential).=C2=A0 The motivation is to mak= e it more difficult for malicious attacks to hash-power their way through a= few large transactions.=C2=A0 Obviously, there are costs in greater transa= ction delays (and fees?) for larger amounts (absolute value).

If there is original value in the idea, I can try to make t= ime to follow-up with a better BIP proposal.

--
Darren

--0000000000002f6701056d6eb10a--