Aidan Thornton [ARCHIVE]

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2011-09-14 to 2012-07-23
💬 Posted a total of 5 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Public Key

npub18raeljmr9tfjcj7ncvqgkvv744a48t6lpk90xz25zlv9sla6zv4quna0jy

Profile Code

nprofile1qqsr37uled3j45evf0fuxqytxx02676n4a0smzhnp92p0kzc07apx2sprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdks8m6x

Publishing to

relay.noswhere.com

Author Public Key

npub18raeljmr9tfjcj7ncvqgkvv744a48t6lpk90xz25zlv9sla6zv4quna0jy

Show more details

Last Notes

2023-06-07 02:25:37

- reply

📅 Original date posted:2011-09-14
🗒️ Summary of this message: Proposal to modify getwork code to discourage blocks with stale timestamps. Majority adoption would prevent cartels from manipulating difficulty.
📝 Original message:On Wed, Sep 14, 2011 at 3:45 PM, Gavin Andresen <gavinandresen at gmail.com> wrote:
> Modify the getwork code to build on the second-from-tip block if the
> first-on-tip block is on the discouraged list.
>
> Assuming a majority of pools/miners adopt the "discourage blocks with
> stale timestamps" rule, that should squash any incentive for cartels
> to try to start playing with difficulty-- you would have to have 50+%
> power to start, or you risk producing mostly orphan blocks.
Of course, if only a small percentage of mining power adopts this
scheme, everyone that does so will presumably be harming themselves by
doing so since they're essentially increasing the odds that the next
block they mine will become invalid...