# Glamsterdam consensus-layer specification inventory Read date: **2026-10-27 UTC**. This is public-source specification research, not client-code analysis or a claim that a devnet activation proves mainnet activation. Fork name for this layer: **Gloas**, spelled in the repository heading “Gloas -- The Beacon Chain”: [pinned spec][BC]. The default branch is **master**, confirmed by the [repository API][repo-api]. Its head at the time of reading was **`8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2`** (commit timestamp `2026-10-27T16:28:12Z`), from the [master commit API][head]. Every consensus-specs implementation reference below is pinned to that commit, called **C**. A release tag and a current branch snapshot are different versions. The exact intersection of EIP-7773's **“EIPs Scheduled for Inclusion”** with consensus-layer changes found in Gloas is **7688, 7732, 7843, 7928, 8045, 8061, 8282**. This includes the CL side of the cross-layer SLOTNUM and BAL proposals: the former adds the slot to payload attributes/payloads; the latter adds the BAL bytes to the SSZ execution payload. These are explicit fields in [the pinned spec][BC]. The [meta EIP][meta] does not label individual scheduled entries EL versus CL. Its other scheduled execution proposals are outside this inventory. **8070 and 8261 are shown separately in the same table to avoid silently losing features that Gloas itself lists**: they occur under the meta EIP's Other EIPs, not its Scheduled for Inclusion section. Gloas's introduction names eight EIPs (all table entries except 7928); 7928 is nevertheless explicitly annotated in its `ExecutionPayload` definition. [Sources: meta][meta], [Gloas introduction and payload][BC]. ## EIP table “Page last updated” means a date actually published by the EIP page, not its creation date, Last Call deadline, HTTP crawl date, or a guessed modification date. **None of these nine EIP pages or their current Markdown front matter supplies a last-updated date.** The table says so; supplementary Git file-history dates are given below. EIP pages are linked in the first column; their raw current headers were also checked. The EIPs repository snapshot at reading was `d4c575521d99ec881a444ab3af604e684b5f0743` ([API][eips-head]). The “targeted EIP revision” column quotes the exact EIPs-repository hash linked by Gloas's introduction, which explicitly warns that its targeted version can differ from the published EIP. It is not the consensus-specs commit C. Files below are relative to `specs/gloas/`; linked references resolve at C. The newest release containing Gloas is **`v1.7.0-beta.4`**, published `2026-10-08T19:27:03Z`, explicitly a **prerelease** ([release][release], [release API][releases-api], [tag directory API][release-tree]). It contains the same eight introductory EIP pins ([release beacon spec][release-bc]); the table does not assert that the entire release is identical to current master. | EIP | Title (current EIP page) | Status/location in EIP-7773 | EIP page's own status; page last updated | Current Gloas targeted EIP revision | Consensus spec files implementing or adapting to it (all at C) | consensus-specs commit | Newest release containing fork | Mainnet today | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [EIP-7688][e7688] | Forward Compatible Consensus Data Structures | Scheduled for Inclusion | **Review**; **not stated** | `f2e6d7fb01194d590e16fcdcae8061d06cf1a7f1` ([target][pin7688]) | [BC][BC] types/containers; [fork][F] state and attestation conversion; [P2P][P] SSZ bounds/sidecars; [light-client sync][LS] branches/header; [light-client fork][LF] conversion; [partial columns][PC] progressive bit lists | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-7732][e7732] | Enshrined Proposer-Builder Separation | Scheduled for Inclusion | **Last Call**; **not stated** | `c36a2e58a4496ed21bef6b1c97505b03fd159f0a` ([target][pin7732]) | [BC][BC] builders, bids, PTC, deferred payload processing; [builder][B]; [fork][F]; [fork choice][FC]; [P2P][P]; [validator][V]; [fast confirmation][FAST]; [light-client sync][LS], [full node][LN], [fork][LF] and [networking][LP]; [partial columns][PC] payload/sidecar adaptations | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-7843][e7843] | SLOTNUM Opcode | Scheduled for Inclusion | **Last Call**; **not stated** | `c3bfd4ba41cf0fcbfe8c404f33ba89f5174971e0` ([target][pin7843]) | [BC][BC] `ExecutionPayload.slot_number` (L964–965); [fork choice][FC] `PayloadAttributes.slot_number` (L170–171); [validator][V] `prepare_execution_payload` (L368–369) | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-7928][e7928] | Block-Level Access Lists | Scheduled for Inclusion | **Last Call**; **not stated** | **No EIP-7928 pin found in Gloas introduction**; current page source pinned at `d4c575521d99ec881a444ab3af604e684b5f0743` ([current source][current7928]); do not substitute it for an advertised target | [BC][BC] `BlockAccessList` type and `ExecutionPayload.block_access_list` (L962–963). This is CL transport/storage of an EL-defined BAL, not CL execution of BAL state-diff semantics | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-8045][e8045] | Exclude Slashed Validators from Proposing | Scheduled for Inclusion | **Last Call**; **not stated** | `414a8404198c5afaa3cfed10a385a9aae1dfaae3` ([target][pin8045]) | [BC][BC] `get_beacon_proposer_indices` (L1287–1306), filters slashed candidates before selecting future proposers | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-8061][e8061] | Increase Exit and Consolidation Churn | Scheduled for Inclusion | **Last Call**; **not stated** | `01f15c37c64114c478cb1136e0a6966084e4db14` ([target][pin8061]) | [BC][BC] separate activation/exit/consolidation churn, exit accounting, pending deposits; [P2P][P] `compute_min_epochs_for_block_requests` (L246–262); [weak subjectivity][WS] `compute_weak_subjectivity_period` | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-8070][e8070] | eth/72 - Sparse Blobpool | Other EIPs → Networking EIPs; **not Scheduled for Inclusion** | **Last Call (Networking)**; **not stated** | `f516cef8b482bf123d554ee12ff5b421f5578d38` ([target][pin8070]) | [fork choice][FC] `notify_forkchoice_updated.custody_columns` (L131–145); [validator][V] invocation (L379–380). These are CL/Engine API changes; eth/72 wire behavior is EL networking | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-8261][e8261] | Gas Limit Schedule | Other EIPs → Informational EIP; **not Scheduled for Inclusion** | **Last Call (Informational)**; **not stated** | `f6b4668ef37612feba85aef151303f4100b79360` ([target][pin8261]) | [BC][BC] optional `GAS_LIMIT_SCHEDULE` (L637–646), `get_scheduled_gas_limit` (L1152–1162); no new block-validity rule | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | | [EIP-8282][e8282] | Builder Execution Requests | Scheduled for Inclusion | **Last Call**; **not stated** | `de4c6f02c7bec4686762c55f8ab6abcf97a77d7d` ([target][pin8282]) | [BC][BC] builder request containers, `ExecutionRequests`, encoding and `process_builder_deposit_request` / `process_builder_exit_request` (L2265–2383); [builder][B] deposit/exit guide; [validator][V] `get_execution_requests` (L261–320); [fork][F] one-time pending-deposit onboarding shared with 7732 | `8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2` | `v1.7.0-beta.4` (prerelease) | **not live** [basis below](#mainnet-check) | For every Last Call entry, the page gives a **Last Call Deadline of 2026-11-01**, not a last-updated date. [EIP-7732][e7732], [7843][e7843], [7928][e7928], [8045][e8045], [8061][e8061], [8070][e8070], [8261][e8261], [8282][e8282]. EIP-7688 remains Review ([page][e7688]). Supplementary modification provenance, **not page-published last-updated dates**: GitHub's latest commit query restricted to each EIP path returned `f1ade090fd315895461fc3e249cb1a675aeb55a9`, `2026-10-22T14:08:27Z`, for [7688][hist7688], [7732][hist7732], [7843][hist7843], [8045][hist8045], [8061][hist8061], [8261][hist8261]; `5ef380124bd68d09c02fa90d0de0f2455f37d5ee`, `2026-10-06T21:57:47Z`, for [8070][hist8070] and [8282][hist8282]; and `d4c575521d99ec881a444ab3af604e684b5f0743`, `2026-10-27T16:04:29Z`, for [7928][hist7928]. Those dates include editorial/status changes and do not imply a protocol change on that date. ## Devnet target and activations The [ethpandaops glamsterdam-devnet-8 notes][notes], titled Plataberget spec, target **consensus-specs `v1.7.0-alpha.14`**, in Specs & Tests → Consensus Layer. This is an explicit test-network target, not the newest release. The notes also give that devnet's own Gloas transition epoch as **1536**; that is not either public-testnet epoch below. Only the CL version target is used here; the notes' client regression statements were not independently investigated in this bounded inventory. [EIP-7773 Activation][meta] gives: | Network | Activation epoch | Timestamp / UTC as printed | | --- | ---: | --- | | Sepolia | **353024** | `1791294816` / 2026-10-06 13:53:36 UTC | | Hoodi | **132352** | `1793036568` / 2026-10-26 17:42:48 UTC | | Mainnet | **blank** | **blank** | These are the meta EIP's published values; no RPC or client was run to verify activation. ## Mainnet check **All nine rows are classified “not live” for the new EIP logic as of the read date.** This is a documentary conclusion: the relevant EIP pages have Review/Last Call status and describe the new changes; [EIP-7773][meta] lists no mainnet activation. None of these nine numbers appears in the included-EIP lists of [Pectra/Prague–Electra EIP-7600][pectra] or [Fusaka/Fulu–Osaka EIP-7607][fusaka]. EIP-7600 gives mainnet epoch `364032`, timestamp `1746612311`; EIP-7607 gives mainnet epoch `411392`, timestamp `1764798551` (2025-12-03 21:49:11 UTC). Those earlier forks include related **dependencies**, not these new proposals: 7251/7685/6110/7002 in Pectra, and 7594/7917/7935 in Fusaka. In particular, 8045 is not the already-deployed proposer-lookahead EIP-7917, 8061 is not the already-deployed EIP-7251 churn logic, and 8261 is not EIP-7935's default-gas recommendation. [Sources: respective EIP Requires/Specification sections][e8045], [8061][e8061], [8261][e8261], [prior-fork inclusion lists][pectra], [Fusaka list][fusaka]. No claim is made here that all inherited functions in a Gloas document are inactive; the classification concerns each EIP's new logic. For optional/informational 8261 it means the post-Gloas schedule feature, not a consensus-enforced activation. ## Disagreements, stale pins, and limits These are documentation/version differences, not client bug findings. Scope categories, EIP lifecycle status, and deployment status are different concepts; Scheduled for Inclusion versus Last Call alone is not a contradiction. 1. **Feature coverage versus scheduled status.** The meta heading is “EIPs Scheduled for Inclusion”; 8070 is instead under “Networking EIPs” and 8261 under “Informational EIP” ([meta][meta]). Gloas explicitly includes both in its introductory feature list ([BC introduction][BC]). Therefore the list of features in the spec is broader than the formally scheduled list. This is a coverage/category difference, not grounds to silently promote the two to scheduled status. Their pages themselves identify 8070 as Networking ([page][e8070]) and 8261 as Informational ([page][e8261]). 2. **The spec's blanket draft warning is stale relative to the current EIP pages.** It says, “These EIPs are in draft and may change or be removed.” ([BC introduction][BC]). Current page status is Review for 7688 and Last Call for all seven other EIPs in that introductory list ([table page links](#eip-table)). The exact pins are older versions, not proof that today's EIPs are still Draft. At those pins 7732/7843/8045/8061/8261/8282 have `status: Draft`, while 8070 has `status: Review` and 7688 already has `status: Review` ([pinned EIP sources in the table](#eip-table)). Thus the warning is not an exact per-EIP status even for its own pins. 3. **EIP-7732's two-way references select different revisions and designs.** Current EIP-7732 delegates full consensus changes to consensus-specs ([EIP Consensus Layer][e7732]); its six links point to consensus-specs `d9663f85be248c4fd0ae95806da6070e17c2442b`, not C. In the other direction C's introduction pins EIP-7732 to `c36a2e58a4496ed21bef6b1c97505b03fd159f0a`; that old EIP's Execution Layer section says, “No changes are required.” ([old EIP][pin7732]). The current EIP instead says, “Two new system contracts are deployed in the execution layer:” ([current EIP][e7732]) and describes builder deposit/exit requests. C implements those requests ([BC][BC], [builder][B], [validator][V]). The old EIP also describes immediate deduction of a winning bid and builder use of the validator deposit/exit flows; the current page/C defer payment and use the dedicated request bus. These are substantive old-pin differences, not a reason to audit clients against the obsolete summary. The current EIP explicitly says its summary omits progressive-list/container distinctions, so that omission is **not** independently treated as a mismatch. 4. **SLOTNUM's advertised target has stale Engine method names.** The EIP-7843 version linked by C says: “The methods `engine_newPayloadV4`, `engine_getPayloadV6`, and `engine_forkChoiceUpdateV4` are added, to use the new objects.” ([target version][pin7843]). The current page instead specifies `engine_newPayloadV5`, `engine_getPayloadV6`, and `engine_forkchoiceUpdatedV4` ([current EIP][e7843]). C exposes the slot in its payload and payload attributes ([BC][BC], [fork choice][FC], [validator][V]). This establishes an EIP-version discrepancy; this item does not audit the separate Engine API repository. 5. **BAL is implemented but omitted from the introductory EIP pin list.** EIP-7928 says, “The consensus layer stores it as a field in the SSZ `ExecutionPayload` container.” ([EIP Engine API][e7928]). C does implement `BlockAccessList` and the payload field, explicitly annotating it EIP7928 at L962 ([BC][BC]), and the meta schedules 7928 ([meta][meta]). However, C's introductory list supplies no EIP-7928 target revision. Consequently there is no advertised 7928 EIP pin to quote from that list; the table records this gap rather than inventing one. This is an inventory omission, not evidence the feature is unimplemented. 6. **Sparse Blobpool's old pin differs from the current networking specification.** The version linked by C says, “Responses now elide blob payloads for type 3 transactions requested via this RPC.” ([target EIP-8070][pin8070]); it labels `PooledTransactions` as `0x10` and describes an RLP nil literal. The current EIP labels it `0x0a` and explicitly requires the RLP empty list `0xc0`, excluding the empty byte string `0x80` ([current EIP][e8070]). C's CL contribution is `custody_columns`, not an implementation of that EL message codec ([fork choice][FC], [validator][V]). The current versus pinned EIP drift therefore matters to cross-layer audit handoff, but does not establish a CL codec bug. 7. **Churn dependency typo in the advertised old EIP pin.** C links an EIP-8061 version whose metadata says `requires: 7521` ([target EIP][pin8061]); the current page says `Requires EIP-7251` ([current EIP][e8061]). The pinned prose itself already discusses EIP-7251. The header discrepancy is editorial; no different churn rule follows from the mistyped number. 8. **Builder-request prefix and top-up wording is inconsistent across versions.** The EIP-8282 version linked by C says, “There is no on-chain credential-prefix check on this path” ([target EIP][pin8282]); it records the first credential byte as a builder version and uses the old `0x03` prefix for fork seeding. C instead uses `BUILDER_WITHDRAWAL_PREFIX = 0xB0`, checks the credential prefix before either first registration or top-up, and stores `PAYLOAD_BUILDER_VERSION` for new entries ([BC constants and `process_builder_deposit_request`][BC]). Current EIP-8282 uses `0xB0` for fork seeding but describes top-ups as: “The `amount` is credited and the record's `withdrawal_credentials` and `signature` are ignored, as with validator deposits.” ([current EIP][e8282]). That unqualified summary omits C's prefix gate: a top-up with a non-builder prefix is ignored in C. The same current page delegates detailed transition behavior to consensus-specs, so this is recorded as a **summary-versus-detailed-spec ambiguity**, not a confirmed client bug. Current EIP-8282 also calls the `0xB0` prefix deprecated after the fork in its fork-onboarding paragraph, whereas C's builder guide requires it for steady-state builder deposit requests ([builder guide][B]). Finally, the linked old EIP says top-ups to exited entries reset the withdrawal delay; C resets it only when the exited entry's balance is zero. The current page's shorter summary no longer specifies that old unconditional reset. These differences reinforce the need to use C rather than the old pinned lifecycle prose. 9. **Title casing is editorial drift.** The old pinned titles for 7688, 7843, 8045 and 8061 use sentence casing, whereas today's EIP pages and the meta use title casing ([target links and current pages in table](#eip-table)). They refer to the same numbered proposals. No change in scope is inferred from capitalization. The current title of 8261 and C's optional schedule semantics agree: its EIP states that no consensus rules change ([EIP-8261][e8261]); C likewise says the optional schedule adds no validity rules ([BC schedule][BC]). No additional substantive disagreement was established from the reviewed sources. The requested six Gloas documents were fetched in full at C; ancillary Gloas Markdown documents were also read to avoid omitting light-client, partial-column, fast-confirmation, and weak-subjectivity adaptations. A nonexistent `specs/gloas/README.md` returned 404; the GitHub master directory rendering failed through the web reader, so the public GitHub tree API and pinned raw files supplied directory/file evidence. This item neither runs clients nor tests whether any implementation has these discrepancies. ## Sources and every URL read The reference definitions below supply permanent browser-readable citations. The subsequent URL ledger lists **all distinct URLs actually requested**, including API/raw fallbacks and unsuccessful requests; repeated reads of a URL are counted once. Linked URLs embedded in source pages were not automatically followed. In particular, EIP-7732's `d966...` links and the devnet release link were observed as page data, not separately fetched. [meta]: https://eips.ethereum.org/EIPS/eip-7773 [pectra]: https://eips.ethereum.org/EIPS/eip-7600 [fusaka]: https://eips.ethereum.org/EIPS/eip-7607 [notes]: https://notes.ethereum.org/@ethpandaops/glamsterdam-devnet-8 [repo-api]: https://api.github.com/repos/ethereum/consensus-specs [head]: https://api.github.com/repos/ethereum/consensus-specs/commits/master [eips-head]: https://api.github.com/repos/ethereum/EIPs/commits/master [release]: https://github.com/ethereum/consensus-specs/releases/tag/v1.7.0-beta.4 [releases-api]: https://api.github.com/repos/ethereum/consensus-specs/releases?per_page=3 [release-tree]: https://api.github.com/repos/ethereum/consensus-specs/contents/specs/gloas?ref=v1.7.0-beta.4 [release-bc]: https://raw.githubusercontent.com/ethereum/consensus-specs/v1.7.0-beta.4/specs/gloas/beacon-chain.md [BC]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/beacon-chain.md [B]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/builder.md [F]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/fork.md [FC]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/fork-choice.md [P]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/p2p-interface.md [V]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/validator.md [FAST]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/fast-confirmation.md [LF]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/light-client/fork.md [LN]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/light-client/full-node.md [LP]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/light-client/p2p-interface.md [LS]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/light-client/sync-protocol.md [PC]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/partial-columns/p2p-interface.md [WS]: https://github.com/ethereum/consensus-specs/blob/8a80ffa82bd49aac0dd6db17f9e8150aa257fbc2/specs/gloas/weak-subjectivity.md [e7688]: https://eips.ethereum.org/EIPS/eip-7688 [hist7688]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-7688.md&per_page=1 [pin7688]: https://raw.githubusercontent.com/ethereum/EIPs/f2e6d7fb01194d590e16fcdcae8061d06cf1a7f1/EIPS/eip-7688.md [e7732]: https://eips.ethereum.org/EIPS/eip-7732 [hist7732]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-7732.md&per_page=1 [pin7732]: https://raw.githubusercontent.com/ethereum/EIPs/c36a2e58a4496ed21bef6b1c97505b03fd159f0a/EIPS/eip-7732.md [e7843]: https://eips.ethereum.org/EIPS/eip-7843 [hist7843]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-7843.md&per_page=1 [pin7843]: https://raw.githubusercontent.com/ethereum/EIPs/c3bfd4ba41cf0fcbfe8c404f33ba89f5174971e0/EIPS/eip-7843.md [e7928]: https://eips.ethereum.org/EIPS/eip-7928 [hist7928]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-7928.md&per_page=1 [e8045]: https://eips.ethereum.org/EIPS/eip-8045 [hist8045]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-8045.md&per_page=1 [pin8045]: https://raw.githubusercontent.com/ethereum/EIPs/414a8404198c5afaa3cfed10a385a9aae1dfaae3/EIPS/eip-8045.md [e8061]: https://eips.ethereum.org/EIPS/eip-8061 [hist8061]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-8061.md&per_page=1 [pin8061]: https://raw.githubusercontent.com/ethereum/EIPs/01f15c37c64114c478cb1136e0a6966084e4db14/EIPS/eip-8061.md [e8070]: https://eips.ethereum.org/EIPS/eip-8070 [hist8070]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-8070.md&per_page=1 [pin8070]: https://raw.githubusercontent.com/ethereum/EIPs/f516cef8b482bf123d554ee12ff5b421f5578d38/EIPS/eip-8070.md [e8261]: https://eips.ethereum.org/EIPS/eip-8261 [hist8261]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-8261.md&per_page=1 [pin8261]: https://raw.githubusercontent.com/ethereum/EIPs/f6b4668ef37612feba85aef151303f4100b79360/EIPS/eip-8261.md [e8282]: https://eips.ethereum.org/EIPS/eip-8282 [hist8282]: https://api.github.com/repos/ethereum/EIPs/commits?path=EIPS/eip-8282.md&per_page=1 [pin8282]: https://raw.githubusercontent.com/ethereum/EIPs/de4c6f02c7bec4686762c55f8ab6abcf97a77d7d/EIPS/eip-8282.md [current7928]: https://github.com/ethereum/EIPs/blob/d4c575521d99ec881a444ab3af604e684b5f0743/EIPS/eip-7928.md URL ledger (raw files are public GitHub source pages; API responses are public repository metadata): - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -