HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ethereum
EIPs
Python2016–2026
ethereum / EIPs

EIPs

The Ethereum Improvement Proposal repository

Finance & Commerce
Explore on GitHubRead Hacker News discussions
48Distinct people
54Mentions
0Explicit recommenders
14.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Ethereum Improvement Proposal repository

GitHub

Where it is used

  • MetaMask — MetaMask uses Ethereum’s EIP-1559 to power its gas fee handling and ships related UI changes in Extension v10.10.0. This is a live product feature for managing EIP-1559 gas fees in the wallet. Source

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year54 dated mentions

Observed mentions: 2016-03-03 04:37:54 UTC to 2026-09-08 01:43:21 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 12 mentions; 5 submissions, 7 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 3 submissions, 2 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 2 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC606
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC14212
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1257
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC532
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC422
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC725
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Ethereum Improvement Proposals (EIPs) ATTENTION: The EIPs repository has recently undergone a separation of ERCs and EIPs. ERCs are now accessible at https://github.com/ethereum/ercs. All new ERCs and updates to existing ones must be directed at this new repository. The editors apologize for this inconvenience. The goal of the EIP project is to standardize and provide high-quality documentation for Ethereum itself and conventions built upon it. This repository tracks past and ongoing improvements to Ethereum in the form of Ethereum Improvement Proposals (EIPs). EIP-1 governs how EIPs are published. The status page tracks and lists EIPs, which can be divided into the following categories: Core EIPs are improvements to the Ethereum consensus protocol. Networking EIPs specify the peer-to-peer networking layer of Ethereum. Interface EIPs standardize interfaces to Ethereum, which determine how users and applications interact with the blockchain. ERCs specify application layer standards, which determine how applications running on Ethereum can interact with each other. Meta EIPs are miscellaneous improvements that nonetheless require some sort of consensus. Informational EIPs are non-standard improvements that do not require any form of consensus. Before you write an EIP, ideas MUST be thoroughly discussed on Ethereum Magicians or Ethereum Research. Once consensus is reached, thoroughly read and review EIP-1, which describes the EIP process. Please note that this repository is for documenting standards and not for help implementing them. These types of inquiries should be directed to the Ethereum Stack Exchange. For specific questions and concerns regarding EIPs, it's best to comment on the relevant discussion thread of the EIP denoted by the discussions-to tag in the EIP's preamble. If you would like to become an EIP Editor, please read EIP-5069. Preferred Citation Format The canonical URL for an EIP that has achieved draft status at any point is at https://eips.ethereum.org/. For example, the canonical URL for EIP-1 is https://eips.ethereum.org/EIPS/eip-1. Consider any document not published at https://eips.ethereum.org/ as a working paper. Additionally, consider published EIPs with a status of "draft", "review", or "last call" to be incomplete drafts, and note that their specification is likely to be subject to change. Validation and Automerging All pull requests in this repository must pass automated checks before they can be automatically merged: eip-review-bot determines when PRs can be automatically merged 1 EIP-1 rules are enforced using eipw2 HTML formatting and broken links are enforced using HTMLProofer2 Spelling is enforced with CodeSpell2 False positives sometimes occur. When this happens, please submit a PR editing .codespell-whitelist and ONLY .codespell-whitelist Markdown best practices are checked using markdownlint2 It is possible to run the EIP validator locally: Make sure to add cargo's bin directory to your environment (typically $HOME/.cargo/bin in your PATH environment variable) cargo install eipw eipw --config ./config/eipw.toml <INPUT FILE / DIRECTORY> Build the status page locally Install prerequisites Open Terminal. Check whether you have Ruby 3.1.4 installed. Later versions are not supported. ruby --version If you don't have Ruby installed, install Ruby 3.1.4. Install Bundler: gem install bundler Install dependencies: bundle install Build your local Jekyll site Bundle assets and start the server: bundle exec jekyll serve Preview your local Jekyll site in your web browser at http://localhost:4000. More information on Jekyll and GitHub Pages here. Footnotes https://github.com/ethereum/EIPs/blob/master/.github/workflows/auto-review-bot.yml ↩ https://github.com/ethereum/EIPs/blob/master/.github/workflows/ci.yml ↩ ↩2 ↩3 ↩4
Read the full README on GitHub

What Hacker News says

54 sources
alita-moore·Sep 8, 2026
Location: Chicago, IL (also Denver) Remote: Yes, US only Willing to relocate: No Technologies: TypeScript, Next.js, React, React Native, Python, Postgres (internals and extensions), Kubernetes, PyTorch Résumé/CV: https://alita-moore.github.io/portfolio Email: alita.moore805@gmail.com Looking for: one fractional retainer, ~20 hrs/week, $5-6k/month, cash only, no equity, month-to-month. US-based, founded two companies, and I do the customer conversations and product decisions as well as the code. I'm bootstrapping my own company and want one stable engagement that covers my costs so I can do that. That's the whole reason the rate is what it is. Not looking for a career move, equity, or a path to full-time. What you get is someone who can be your only engineer, from customer discovery through product, backend, Postgres, infra, and on-call. S
Read the rest
ome things I've built: - ethereum/EIP-Bot, the bot that governed the Ethereum Improvement Proposals repo for a year with direct commit rights: https://github.com/ethereum/EIPs/pull/3351 - deno lsp go-to-definition from 32s to 131ms, six defects found by counting directory opens instead of timing, every result with a repro script: https://github.com/alita-moore/deno-lsp-performance - At Snackpass: led a team of six, built the React Native point-of-sale, took the Android app from 3.2 to 4.7 stars in three months, and built an inventory system in a weekend that helped land a major partner. - Co-founded a company that trained a production OCR model on 8 GPUs; owned the model, the training pipeline, and the Kubernetes serving stack. - 13 tested, self-contained packages rebuilding patterns from those systems (typed Next.js routes, a Postgres extension toolchain, GitOps cluster, PyTorch training harness): https://github.com/alita-moore/portfolio Best fit: pre-seed or bootstrapped founders who need a senior engineer and can't or don't want to pay for a full-time one. Happy to start with a paid trial ticket.
In Ask HN: Who wants to be hired? (September 2026)
x-complexity·Mar 24, 2023
> Motherfucker, the entire crypto industry is in the middle of a collapse. It lasted less than a decade at scale and that’s just the 10% that weren’t an out and out scam (I lean toward that number being closer to 0%, but I’ll throw you a bone since you sound like you’re caught up in it). 1) Stick to overcollateralized stablecoins (MAI, DAI, FRAX, sUSD, sEUR, etc.) & Layer 2s (Arbitrum, Optimism, zkSync). If you're okay with the centralization risks, then USDC & fiat-backed stablecoins can enter into the picture. 2) Account abstraction's an important step in providing the necessary security & recovery features to make it easier to use & secure. One of the parts required was ERC-4337, which has been in the works for some time and was recently publicly announced. https://github.com/ethereum/EIPs/blob/master/EIPS/eip-4337.m... Before the cont
Read the rest
rarians come in for the quick gotcha and say that it bring in centralization: That's been made painfully aware multiple times over. However, Vitalik's 2021 post on social recovery wallets puts it best: https://vitalik.ca/general/2021/01/11/recovery.html > One common response to suggestions to use any form of multisig, social recovery or otherwise, is the idea that this solution goes back to "trusting people", and so is a betrayal of the values of the blockchain and cryptocurrency industry. While I understand why one may think this at first glance, I would argue that this criticism stems from a fundamental misunderstanding of what crypto should be about. > To me, the goal of crypto was never to remove the need for all trust. *Rather, the goal of crypto is to give people access to cryptographic and economic building blocks that give people more choice in whom to trust, and furthermore allow people to build more constrained forms of trust*: giving someone the power to do some things on your behalf without giving them the power to do everything. Viewed in this way, *multisig and social recovery are a perfect expression of this principle*: each participant has some influence over the ability to accept or reject transactions, but no one can move funds unilaterally. This more complex logic allows for a setup far more secure than what would be possible if there had to be one person or key that unilaterally controlled the funds.
In Sex worker-led payment platform shuts down after being cut off by processor
simonebrunozzi·Jan 8, 2022
> NFTs are only 3 years old No they're not. I co-founded Fabrica.land in 2017, and in mid 2018 we used an NFT to perform a real estate transaction. That's already 3.5 years, and NFTs were already around. The first transaction was a bit "rough", but perfectly valid. Lot of progress since then. From [0]: The ERC-20 (Ethereum Request for Comments 20), proposed by Fabian Vogelsteller in November 2015, is a Token Standard that implements an API for tokens within Smart Contracts. Note: yes, ERC-20 has a few flaws [1], and subsequent ERC have improved on it. [0]: https://ethereum.org/en/developers/docs/standards/tokens/erc... [1]: https://github.com/ethereum/EIPs/issues/20
In In Response to My first impressions of Web3
brian_cloutier·Oct 18, 2021
> Has this ever happened in the history of cryptocurrency? You're replying to a comment which mentions that yes, in fact, this has happened. https://www.gemini.com/cryptopedia/the-dao-hack-makerdao However, it is unlikely that this will ever happen again. The coordination costs behind pulling off this kind of fork are massive. It's difficult to imagine today's more decentralized community could ever agree to do such a thing. As an example, Parity later lost an incredibly large amount of other people's money and the community decided not to roll that particular mistake back: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-999.md
In I accidentally compromised my hot wallet
ekir·Jun 28, 2021
It's fairly common to deploy a proxy contract, which allows for a sort of updating. Basically you deploy a new contract and have the proxy point to that new contract instead of the old one. There are definitely some limitations and it's not fully standardized yet. There's a tentative standard here https://github.com/ethereum/EIPs/issues/1538 and OpenZeppelin also has their own implementation. Although neither of these things will actually help if your contract gets exploited before you can push a fix.
In SafeDollar ‘stablecoin’ drops to $0 following DeFi exploit on Polygon
jamespitts·Jan 13, 2021
I should also add two more important pieces to this: 1. In-person meetings and real-time calls have been a major part of the work. There is an agenda and very good notes are taken during these sessions (https://github.com/ethereum/pm). The calls have been essential for coordinating in a more formal setting and to get a feel for when consensus is achieved on a particular topic or proposal. What threaded forums later added was the ability for others to get involved in the discussion, particularly those who are not core developers or not able to attend. 2. Another important medium has been GitHub issues (e.g. https://github.com/ethereum/EIPs/issues/2315). Proposals are submitted as a PR and, earlier in the evolution of the governance process, many people would comment on them. These were not ideal due the flat nature of the format. What gene
Read the rest
rally changed on GitHub issues in recent years was the encouraging of commenters to go to an external forum thread (https://github.com/ethereum/EIPs/issues/2315#issuecomment-63...), leaving editors and authors to work out structural and other basic issues about a proposal in GitHub PR comments.
In If it will matter after today, don't talk about it in a chat room

Showing the 15 most recent of 54 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.