Skip to content

blog: add draft — EIP-8130: Account Abstraction Without the Simulation Tax#734

Closed
claude[bot] wants to merge 1 commit intodevelopfrom
blog/eip-8130-account-abstraction
Closed

blog: add draft — EIP-8130: Account Abstraction Without the Simulation Tax#734
claude[bot] wants to merge 1 commit intodevelopfrom
blog/eip-8130-account-abstraction

Conversation

@claude
Copy link
Copy Markdown
Contributor

@claude claude Bot commented Mar 17, 2026

Summary

  • Adds draft article explaining EIP-8130, the Coinbase/Base-authored account abstraction proposal targeting Ethereum's Hegota fork (H2 2026)
  • Covers: verifier model, permissionless payer, cross-chain sig security, and comparison with EIP-4337 and EIP-8141
  • Also contextualizes EIP-7979 (static EVM control flow), ERC-8180 (Blob Authenticated Messaging), and EIP-8189 (snap/2) as the broader 2026 protocol cluster
  • ~1,500 words, status: draft

Notes

  • Cover images (eip-8130-account-abstraction.png / -og.png) need to be generated once GEMINI_API_KEY is available: bash blog/pipeline/generate-cover.sh eip-8130-account-abstraction "<prompt>"

🤖 Generated with Claude Code

…n Tax

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Mar 17, 2026

Greptile Summary

This PR adds a draft blog article (eip-8130-account-abstraction.md) covering EIP-8130, Coinbase/Base's account abstraction proposal targeting the Hegota fork. The post is well-structured, technically accurate, and correctly gated behind status: draft so it will not appear in any static build output until explicitly published.

Key observations:

  • Dockerfile / new directory: No Dockerfile changes are needed. Dockerfile.caddyfile already copies the entire blog/ directory (COPY blog/ ./), and the new file lands in the pre-existing blog/src/content/blog/ folder — no new directories introduced.
  • Draft gating is correct: Both src/pages/[...slug].astro and src/pages/index.astro filter with data.status === 'published', so the post and its missing images will not be included in the Astro static build while it remains a draft.
  • Missing cover images: The frontmatter references eip-8130-account-abstraction.png and eip-8130-account-abstraction-og.png in blog/public/images/, neither of which has been committed. This is acknowledged in the PR description, but there is no gate preventing the post from being published with broken images. This needs to be resolved before the status is flipped to published.
  • Content accuracy: Technical claims (EIP-4337 March 2023 deployment, verifier model, permissionless payer design, cross-chain sig domain separation) are consistent with the referenced upstream PRs and well-cited.
  • readingTime field: Set to 8 minutes; at ~1,500 words the actual reading time is closer to 6–7 minutes, but this is a minor cosmetic point consistent with how other posts in the collection round up.

Confidence Score: 4/5

  • Safe to merge as-is; the draft status prevents any broken-image exposure on the live site, but the missing cover images must be committed before publishing.
  • The change is a single Markdown file with no code logic, no new dependencies, and no structural changes to the repository. The status: draft flag correctly prevents the incomplete post (missing images) from reaching the live site. The only risk is a future regression if someone flips the status to published before the cover images are added, which is an out-of-band operational concern rather than a code defect in this PR.
  • blog/src/content/blog/eip-8130-account-abstraction.md — cover images referenced in frontmatter are absent and must be added before publishing.

Important Files Changed

Filename Overview
blog/src/content/blog/eip-8130-account-abstraction.md New draft blog article covering EIP-8130 account abstraction; well-structured with accurate technical content and proper status: draft gating, but the two referenced cover images (eip-8130-account-abstraction.png / -og.png) are absent from blog/public/images/ and must be added before publishing.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[EIP-8130 AATx received by node] --> B{payer is zero address?}
    B -- Yes --> C[Sender pays gas]
    B -- No --> D[Payer pays gas]
    C --> E[Lookup sender in ACCOUNT_CONFIG_ADDRESS]
    D --> E
    E --> F["STATICCALL verifier.verify(txHash, sender_auth) → ownerId"]
    F --> G{ownerId matches registered sender config?}
    G -- No --> H[Reject transaction]
    G -- Yes --> I{Separate payer present?}
    I -- Yes --> J["STATICCALL verifier.verify(txHash, payer_auth) → payer ownerId"]
    J --> K{payer ownerId valid and SCOPE_PAYER set?}
    K -- No --> H
    K -- Yes --> L[Transaction valid - execute callData]
    I -- No --> L
Loading
Prompt To Fix All With AI
This is a comment left during a code review.
Path: blog/src/content/blog/eip-8130-account-abstraction.md
Line: 11-12

Comment:
**Missing cover images not added to repository**

The frontmatter references two image files that do not yet exist in `blog/public/images/`:
- `eip-8130-account-abstraction.png`
- `eip-8130-account-abstraction-og.png`

While the current `draft` status means the Astro build will skip this post (both `[...slug].astro` and `index.astro` filter to `status === 'published'` only), these files must exist before the status is changed to `published` — otherwise the article and OG image will render broken on the live site and in social previews.

The PR description acknowledges this dependency (`bash blog/pipeline/generate-cover.sh eip-8130-account-abstraction "<prompt>"`), but there is no follow-up issue, TODO comment, or CI gate to enforce that the images are added before this is published. Consider either:
1. Adding a placeholder image now (or reusing an existing one temporarily), or
2. Tracking the missing images as a required prerequisite before flipping `status: draft``status: published`.

How can I resolve this? If you propose a fix, please make it concise.

Last reviewed commit: 0455a64

Comment on lines +11 to +12
image: "/blog/images/eip-8130-account-abstraction.png"
ogImage: "/blog/images/eip-8130-account-abstraction-og.png"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Missing cover images not added to repository

The frontmatter references two image files that do not yet exist in blog/public/images/:

  • eip-8130-account-abstraction.png
  • eip-8130-account-abstraction-og.png

While the current draft status means the Astro build will skip this post (both [...slug].astro and index.astro filter to status === 'published' only), these files must exist before the status is changed to published — otherwise the article and OG image will render broken on the live site and in social previews.

The PR description acknowledges this dependency (bash blog/pipeline/generate-cover.sh eip-8130-account-abstraction "<prompt>"), but there is no follow-up issue, TODO comment, or CI gate to enforce that the images are added before this is published. Consider either:

  1. Adding a placeholder image now (or reusing an existing one temporarily), or
  2. Tracking the missing images as a required prerequisite before flipping status: draftstatus: published.
Prompt To Fix With AI
This is a comment left during a code review.
Path: blog/src/content/blog/eip-8130-account-abstraction.md
Line: 11-12

Comment:
**Missing cover images not added to repository**

The frontmatter references two image files that do not yet exist in `blog/public/images/`:
- `eip-8130-account-abstraction.png`
- `eip-8130-account-abstraction-og.png`

While the current `draft` status means the Astro build will skip this post (both `[...slug].astro` and `index.astro` filter to `status === 'published'` only), these files must exist before the status is changed to `published` — otherwise the article and OG image will render broken on the live site and in social previews.

The PR description acknowledges this dependency (`bash blog/pipeline/generate-cover.sh eip-8130-account-abstraction "<prompt>"`), but there is no follow-up issue, TODO comment, or CI gate to enforce that the images are added before this is published. Consider either:
1. Adding a placeholder image now (or reusing an existing one temporarily), or
2. Tracking the missing images as a required prerequisite before flipping `status: draft``status: published`.

How can I resolve this? If you propose a fix, please make it concise.

@antoinedc
Copy link
Copy Markdown
Member

Closing — blog drafting is handled by the server-side pipeline, not GitHub Actions.

@antoinedc antoinedc closed this Mar 17, 2026
@antoinedc antoinedc deleted the blog/eip-8130-account-abstraction branch March 17, 2026 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant