From: Zawy <wordsgalore@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Getting around to fixing the timewarp attack.
Date: Wed, 29 Aug 2018 05:54:17 -0400 [thread overview]
Message-ID: <CADtTMvkJHuz66KDNOnmsUBCEVkTpT7Ly9cB+o=C2n4KAR=4vZw@mail.gmail.com> (raw)
Rather than restricting every timestamp (or just the 2016*N+1
timestamps) to >= 1+ the previous timestamp as recorded on the
blockchain, the difficulty calculation could have the same restriction
but only in how the timestamps are used. I don't know about backwards
compatibility. Either way, this would also prevent the powLimit
attack that is also capable of getting "unlimited" blocks in less than
4 weeks of > 50% selfish mining. LTC, BCH, and LTC fixed to the
"Zeitgeist" or "timewarp" attack on GeistGeld in 2011 described by
Artforz in different ways, but all are still vulnerable by the
powLimit attack that I described here:
https://github.com/zawy12/difficulty-algorithms/issues/30
Other solutions may not prevent this other attack.
next reply other threads:[~2018-08-29 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 9:54 Zawy [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-20 20:14 Gregory Maxwell
2018-08-22 13:48 ` Jorge Timón
2018-08-24 9:35 ` Johnson Lau
2018-08-30 20:55 ` Bram Cohen
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='CADtTMvkJHuz66KDNOnmsUBCEVkTpT7Ly9cB+o=C2n4KAR=4vZw@mail.gmail.com' \
--to=wordsgalore@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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