docs(specs): explain how eip-8430 relates to eip-8130

[youssefea]

What changed? Why?

Adds a short "Relationship to EIP-8130" section to docs/specifications/base-transactions.mdx. It explains that EIP-8430 is a separate transaction-type proposal split out of EIP-8130, not a rename. EIP-8130 now specifies Keystore Accounts and describes an integration with the EIP-8430 transaction type. The section also notes that earlier EIP-8130 drafts defined type 0x79, which is why older material calls these "EIP-8130 transactions". It states that EIP status does not tell you whether Base Transactions are live on Base.

This closes Base Knowledge Base gap gap-20261013-eip-8430-everest-transactions-vs-eip: "How does EIP-8430 (Base Transactions, Everest) relate to EIP-8130 (native account abstraction on vibenet)? Is 8430 a successor/rename of 8130 or a separate transaction type?" In an agent evaluation, web-search agents answered "EIP-8130" when asked which EIP defines Base Transactions in Everest.

• Gaps log: https://bdocs.cbhq.net/d/base-knowledge-gaps-log
• Linear: DEVREL-859

Notes to reviewers

Primary sources for each fact:

• EIP-8430 is an independent transaction type split out of EIP-8130, with no Keystore dependency; type 0x79; EIP-8130 specifies an integration: Add EIP: AA Transaction Type ethereum/EIPs#12385 (open), PR description and EIPS/eip-8430.md.
• EIP-8130 is now "Keystore Accounts" with Draft status and specifies the AA Transaction Type integration: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8130.md and Update EIP-8130: scope to the Keystore, move the transaction type to a new EIP ethereum/EIPs#12386 (merged, "scope to the Keystore, move the transaction type to a new EIP").
• Earlier EIP-8130 drafts defined AA_TX_TYPE = 0x79: EIPS/eip-8130.md at ethereum/EIPs commit 16390e1f, before the split commit 1a1f470f.

SME confirmation is not required. The section does not claim that either EIP has been accepted, or give an Everest activation date or Mainnet availability.

Out of scope, flagged for follow-up:

• docs/build-on-base/run-a-local-devnet.mdx still says "EIP-8130 transactions", matching the base/base devnet README. The new section explains that legacy name.
• node scripts/validate-docs-structure.js already fails on master because of the /upgrades/denim/eip-8130 redirect chain to the missing /specifications/native-account-abstraction. This PR doesn't touch docs.json.

How has it been tested?

• node scripts/lint-mdx.js --files-from=<changed files>: 0 errors. There are 2 warnings, both on an existing code block.
• node scripts/validate-docs-structure.js: the same 2 redirect errors appear with and without this change, so they come from master.
• New external link https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8130.md returns HTTP 200.

Screenshots

N/A (text-only change)

Generated with Toshi

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
base	🟢 Ready	View Preview	Oct 15, 2026, 3:01 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1

[linear]

DEVREL-859