From: Darren Weber <dweber.consulting@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIP suggestion: PoW proportional to block transaction sum
Date: Wed, 30 May 2018 09:17:29 -0700 [thread overview]
Message-ID: <CAJfMfCoK5=KVr6NB-dxddbjB+ufZxgaUBqwxN+_O3f9JWuut0w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1251 bytes --]
next reply other threads:[~2018-05-30 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 16:17 Darren Weber [this message]
2018-06-05 10:50 ` [bitcoin-dev] BIP suggestion: PoW proportional to block transaction sum Thomas Guyot-Sionnest
2018-06-06 21:01 ` Darren Weber
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='CAJfMfCoK5=KVr6NB-dxddbjB+ufZxgaUBqwxN+_O3f9JWuut0w@mail.gmail.com' \
--to=dweber.consulting@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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