From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] State of Bitcoin Development: October Brain Dump
Date: Thu, 13 Oct 2011 09:38:32 -0400 [thread overview]
Message-ID: <201110130938.35014.luke@dashjr.org> (raw)
In-Reply-To: <CABsx9T18uavGck3oCj=wkm3fe==N9DOAM+xN21+L8uS=sHb_kw@mail.gmail.com>
On Thursday, October 13, 2011 9:32:48 AM Gavin Andresen wrote:
> • Tighten up block-time rules to fix the potential "timejacking" attack.
Once again, this does not fix anything (they're already strict enough for the
2-week window), and just creates new problems.
> • Work on 'discouraging' blocks/transactions to punish
> bad-for-the-common-good-but-good-for-me behaviors from miners or
> nodes.
Flawed concept. Only even potentially useful for extreme cases (ie, a miner
intentionally making lots of 1 MB blocks of junk).
prev parent reply other threads:[~2011-10-13 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:32 Gavin Andresen
2011-10-13 13:38 ` Luke-Jr [this message]
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=201110130938.35014.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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