Skip to content

Update EIP-969: fix broken link to nonexistent Ethereum discussion #10513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 15, 2025
Merged

Update EIP-969: fix broken link to nonexistent Ethereum discussion #10513

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion EIPS/eip-969.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@
eip: 969
title: Modifications to ethash to invalidate existing dedicated hardware implementations
author: David Stanfill <[email protected]>
discussions-to: https://gitter.im/ethereum/topics/topic/5ac4d974109bb043328911ce/eip-969-discussion
status: Stagnant
type: Standards Track
category: Core
Expand All @@ -10,7 +9,7 @@
---


## Simple Summary

Check warning on line 12 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

body has extra section(s) 

warning[markdown-order-section]: body has extra section(s)
   --> EIPS/eip-969.md
    |
 12 | ## Simple Summary
    |
   ::: EIPS/eip-969.md
    |
 51 | ## EthashV2
    |
   ::: EIPS/eip-969.md
    |
 73 | ## Agent Changes (Optional Variant)
    |
   ::: EIPS/eip-969.md
    |
227 | ## Implementation
    |
    = help: see https://ethereum.github.io/eipw/markdown-order-section/

Check warning on line 12 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

body has extra section(s) 

warning[markdown-order-section]: body has extra section(s)
   --> EIPS/eip-969.md
    |
 12 | ## Simple Summary
    |
   ::: EIPS/eip-969.md
    |
 51 | ## EthashV2
    |
   ::: EIPS/eip-969.md
    |
 73 | ## Agent Changes (Optional Variant)
    |
   ::: EIPS/eip-969.md
    |
227 | ## Implementation
    |
    = help: see https://ethereum.github.io/eipw/markdown-order-section/

This EIP modifies ethash in order to break ASIC miners specialized for the current ethash
mining algorithm.
Expand Down Expand Up @@ -79,7 +78,7 @@
field so a miner does not require special configuration when mining on a chain
that chooses not to implement the `ASIC_Mitigation` hardfork.

Due to compatibility concerns with implementations that already add additional

Check warning on line 81 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-969.md
   |
81 | Due to compatibility concerns with implementations that already add additional
   |
   = help: see https://ethereum.github.io/eipw/markdown-rel-links/

Check warning on line 81 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-969.md
   |
81 | Due to compatibility concerns with implementations that already add additional
   |
   = help: see https://ethereum.github.io/eipw/markdown-rel-links/
parameters to `GetWork`, it is desired to add `BlockNumber` as an explicit 4th parameter
as suggested in https://github.com/ethereum/go-ethereum/issues/2333. Algorithm
should then be returned as either `"ethash"` or `"ethashV2"` according to the
Expand All @@ -95,7 +94,7 @@

Goal #1 is something that we can only do probabilistically without detailed
knowledge of existing ASIC miner design. The known released miner is available for
purchase [here](https://shop.bitmain.com/product/detail?pid=00020180403174908564M8dMJKtz06B7),

Check warning on line 97 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-969.md
   |
97 | purchase [here](https://shop.bitmain.com/product/detail?pid=00020180403174908564M8dMJKtz06B7),
   |

Check warning on line 97 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
  --> EIPS/eip-969.md
   |
97 | purchase [here](https://shop.bitmain.com/product/detail?pid=00020180403174908564M8dMJKtz06B7),
   |
with delivery slated for mid-summer 2018.

Our approach should balance the inherent security risks involved with changing
Expand Down Expand Up @@ -123,7 +122,7 @@
POS development as well as larger algorithm changes to be well analyzed by
experts.

The choice of FNV constants is made based on the formal specification at

Check warning on line 125 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
125 | The choice of FNV constants is made based on the formal specification at
    |

Check warning on line 125 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
125 | The choice of FNV constants is made based on the formal specification at
    |
https://tools.ietf.org/html/draft-eastlake-fnv-14#section-2.1

@goobur provided the following python code to output primes matching this criteria:
Expand Down Expand Up @@ -197,14 +196,14 @@
It is worth noting that FNV is not a cryptographic hash, and it is not used as
such in ethash. That said, a more invasive hash algorithm change could be considered.

One suggestion has been [MurmurHash3](https://github.com/aappleby/smhasher/blob/master/src/MurmurHash3.cpp).

Check warning on line 199 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
199 | One suggestion has been [MurmurHash3](https://github.com/aappleby/smhasher/blob/master/src/MurmurHash3.cpp).
    |

Check warning on line 199 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
199 | One suggestion has been [MurmurHash3](https://github.com/aappleby/smhasher/blob/master/src/MurmurHash3.cpp).
    |

[Other suggestions have been made](https://twitter.com/el33th4xor/status/981292363627810818):

Check warning on line 201 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
201 | [Other suggestions have been made](https://twitter.com/el33th4xor/status/981292363627810818):
    |

Check warning on line 201 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
201 | [Other suggestions have been made](https://twitter.com/el33th4xor/status/981292363627810818):
    |
[Argon2](https://github.com/P-H-C/phc-winner-argon2),

Check warning on line 202 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
202 | [Argon2](https://github.com/P-H-C/phc-winner-argon2),
    |

Check warning on line 202 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
202 | [Argon2](https://github.com/P-H-C/phc-winner-argon2),
    |
[Equihash](https://blog.z.cash/why-equihash/) of Zcash fame, and

Check warning on line 203 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
203 | [Equihash](https://blog.z.cash/why-equihash/) of Zcash fame, and
    |

Check warning on line 203 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
203 | [Equihash](https://blog.z.cash/why-equihash/) of Zcash fame, and
    |
[Balloon Hashing](https://crypto.stanford.edu/balloon/).

Check warning on line 204 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
204 | [Balloon Hashing](https://crypto.stanford.edu/balloon/).
    |

Check warning on line 204 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
204 | [Balloon Hashing](https://crypto.stanford.edu/balloon/).
    |

Another possible candidate is [Cuckoo Cycle](https://github.com/tromp/cuckoo),

Check warning on line 206 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
206 | Another possible candidate is [Cuckoo Cycle](https://github.com/tromp/cuckoo),
    |

Check warning on line 206 in EIPS/eip-969.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

non-relative link or image 

warning[markdown-rel-links]: non-relative link or image
   --> EIPS/eip-969.md
    |
206 | Another possible candidate is [Cuckoo Cycle](https://github.com/tromp/cuckoo),
    |
although there are some concerns regarding unaddressed optimization
vulnerabilities. One review can be found
[here](https://da-data.blogspot.com/2014/03/a-public-review-of-cuckoo-cycle.html).
Expand Down
Loading