docs(chain): Move B20 spec to References, Create B20 and Native AA in Core Concepts, change Chain landing page - #1829
docs(chain): Move B20 spec to References, Create B20 and Native AA in Core Concepts, change Chain landing page#1829youssefea wants to merge 11 commits into
Conversation
…oncepts The Chain tab opened on the Beryl upgrade page because a "Beryl Upgrade" group sat above Introduction. Remove that group so the tab lands on Chain Overview. Core Concepts gains two pages at the top: - B20 Token Standard: a conceptual, non-technical introduction to B20 with the chain.base.org/demos/b20 demo embedded, covering why it exists, what it provides, the Asset and Stablecoin variants, who it is for, and how it compares to a custom ERC-20. - Native Account Abstraction: the conceptual half of the EIP-8130 page — why native AA, the five concepts, and what it unlocks. Upgrades collapses Cobalt and Beryl to one page each (via sidebarTitle); Azul and Optimism are untouched. Both specs move into Reference: - Reference > B20 (un-nested from "B20 Specification"): overview, constants and addresses, errors and events, interfaces, plus a new B20 changelog. - Reference > Native Account Abstraction: eip-8130.mdx, rewritten as the technical reference now that the concepts live in Core Concepts. Adds a Cobalt upgrade overview shaped like Beryl's, with activation timestamps marked TBD pending scheduling. Spec file paths are unchanged, so no existing URLs move. The b20/demos stub is removed and redirected to the new core concept, which embeds the same demo. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
🟡 Heimdall Review Status
|
The Chain tab's "B20 Specification" anchor used a site-relative href, which the Mintlify CLI rejects with "must be a valid url", failing the prebuild step so `mintlify dev` could not start at all. Use an absolute docs.base.org URL, matching the Get Started tab's Faucet and Bridge anchors. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Two sentences was longer than the neighbouring cards. Drop the audience framing, which the B20 page itself opens with. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
| @@ -0,0 +1,87 @@ | |||
| --- | |||
| title: "Native Account Abstraction" | |||
There was a problem hiding this comment.
Can we have a "coming soon" tag on the side nav for this one given its not mainnet live yet?
There was a problem hiding this comment.
Done — added in 3ae34aa8, before this reply. The page now carries tag: "Coming Soon" in its frontmatter, so the pill renders in the side nav next to "Native Account Abstraction" (the B20 page alongside it uses tag: "New").
There was a problem hiding this comment.
Ended up pulling this back out. In the side nav the pill sits awkwardly: "Native Account Abstraction" is already a long label, and the tag pushes onto a second line, which makes the entry look overlong next to the rest of Core Concepts.
The signal is still on the page itself — there is a callout at the top stating that EIP-8130 is experimental and currently runs only on the vibenet devnet, and the Cobalt overview lists mainnet and Sepolia activation as TBD. So a reader learns it is not mainnet-live in the first screen, just not from a nav pill.
There was a problem hiding this comment.
Added "Soon" instead of "Coming Soon" that was too long
The page opened with prose I wrote rather than sourced material, including a "why B20 exists" narrative and a comparison table whose rows were not backed by anything in the repo. Replace it with technical content drawn from existing pages: - Intro and the ERC-20 build-audit-maintain framing from launch-b20-token - ERC-20 parity list, roles, policy registry and scopes, seize, pause, memos, supply cap, permit, contract URI, factory, address derivation, admin renunciation, variants, and precompile addresses from the B20 specification - The decimals caveat and integration notes from accept-b20-payments - Activation gating and the base-forge note from launch-b20-token - "When to use B20" verbatim from b20-playground - Activation dates from the Beryl overview Drops the invented "why B20 exists" section and the B20-vs-ERC-20 table. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
|
|
||
| ## Why B20 exists | ||
|
|
||
| Ask an issuer what their token contract has to do beyond moving balances, and the list is long: freeze an account when a court order lands, seize a balance, pause one operation without halting the rest, tag a transfer with an invoice number, cap total supply, run a stock split, publish a dividend. Every team builds that logic again, in a custom contract, and then pays to audit it. |
There was a problem hiding this comment.
Is this the normal voice of our text ?
The comparison of native account abstraction against ERC-4337 and EIP-7702 applies across EVM networks, not Ethereum L1 specifically. Also updates the secp256k1 descriptor on both halves of the page so the two stay consistent. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
| { | ||
| "group": "Core Concepts", | ||
| "pages": [ | ||
| "base-chain/network-information/b20-token-standard", |
There was a problem hiding this comment.
Can we move the new ones below "Network Fees" and above bridging?
Generally ordering based on most commonly asked plus logical building up from the foundation.
| { | ||
| "group": "B20", | ||
| "pages": [ | ||
| "base-chain/specs/upgrades/beryl/b20/specification/index", |
There was a problem hiding this comment.
Think we should update these urls so that they match they IA here, which is now much cleaner
Some of these b20 urls have gotten a bit wild: /specs/upgrades/beryl/b20/specification/reference/**
There was a problem hiding this comment.
moved files so the paths match the nav. /specs/upgrades/beryl/b20/specification/reference/** is now /specs/reference/b20/**, and upgrades/cobalt/eip-8130 is now specs/reference/native-account-abstraction. All old urls redirect, and every internal link is updated.
|
Review Error for ericbrown99 @ 2026-08-18 18:24:56 UTC |
EIP-8130 is experimental and runs only on the vibenet devnet, so the nav should signal that it is not yet available on mainnet or Sepolia. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Addresses review feedback that the B20 urls had gotten unwieldy: /specs/upgrades/beryl/b20/specification/reference/** did not reflect that these pages now live under Protocol Specifications > Reference. Moves 113 files so paths match the nav: specs/upgrades/beryl/b20/specification -> specs/reference/b20 .../specification/reference/constants-and-addresses -> specs/reference/b20/constants-and-addresses .../specification/reference/errors-and-events-index -> specs/reference/b20/errors-and-events .../specification/reference/interfaces/** -> specs/reference/b20/interfaces/** specs/upgrades/beryl/b20/changelog -> specs/reference/b20/changelog specs/upgrades/cobalt/eip-8130 -> specs/reference/native-account-abstraction Rewrites 390 internal urls across 117 content files, and adds redirects covering every old path, using :slug* wildcards for the interface tree in keeping with the existing redirects. Ordered most-specific-first so the errors-and-events rename is not shadowed by the wildcard. Also reorders Core Concepts per review: the two new pages now sit after Network Fees and before Bridging and Withdrawals, rather than at the top. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Reverts 3ae34aa at the author's request. The page's own warning still states that EIP-8130 is experimental and vibenet-only, and the Cobalt overview lists mainnet and Sepolia activation as TBD. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
Restores a nav tag on the page, shortened from "Coming Soon" so it fits alongside the label without pushing onto a second line. Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
What changed? Why?
The Chain tab opened on the Beryl upgrade page, because a
Beryl Upgradegroup sat aboveIntroductionin the nav. It now lands on Chain Overview.Two new pages at the top of Core Concepts:
Upgrades collapses to one page per upgrade for the two newest forks, via
sidebarTitle:Azul and Optimism are untouched.
Both specs move into Reference:
eip-8130.mdx, rewritten as a technical reference (network details, client setup, transaction structure, account configuration, authenticators, payers) now that the conceptual material lives in Core Concepts.Also adds a Cobalt upgrade overview shaped like Beryl's, and a B20 card to Chain Overview since that's the new landing page.
Second commit — unrelated bug, found while testing:
mintlify devcurrently fails to start onmaster. #1812 added a Chain anchor with a site-relativehref, and the CLI rejects it (#.navigation.tabs[1].global.anchors[0].href: Must be a valid url), failing the prebuild step.cc8ee918makes it an absolutedocs.base.orgURL, matching the Get Started tab's Faucet and Bridge anchors. Happy to split this out if you'd rather land it separately.Notes to reviewers
docs.jsoninstead of ~120 redirects, and no external link to a spec page breaks.specs/upgrades/cobalt/overview.mdxhasTBDactivation timestamps and no required-software table, since Cobalt isn't scheduled. Please fill in if those numbers exist.b20/changelog.mdxhas one entry (the Beryl initial release, reconstructed from the specification). Worth a check that nothing is missing or mischaracterised.sidebarTitle; their on-page titles stay "Overview", consistent with Azul and the Optimism forks.b20/demos.mdx(an external-link stub) is deleted and redirected to the new core concept, which embeds the same demo.beryl/b20-playground.mdxis left as-is. It was already orphaned from the nav before this PR; worth a follow-up decision on whether to surface or delete it.How has it been tested?
mintlify devruns locally (after the anchor fix above). All affected pages return 200: Chain Overview, both new core concepts, Cobalt overview, the EIP-8130 reference, Beryl overview, the B20 changelog, the B20 specification, and the Reference glossary. The only nav warning isget-started/build-app, already missing onmaster.https://chain.base.org/demos/b20sends noX-Frame-Optionsand no CSPframe-ancestors, so the iframe embed renders rather than falling back.node scripts/lint-mdx.json each new and changed file: 0 errors, 0 warnings on the new pages. The 3 "code block missing language" hits oneip-8130.mdxandspecification/index.mdxare a pre-existing linter quirk that flags closing fences (297 of them repo-wide onmaster), not new issues.pagesentry indocs.jsonresolves to a file: the only unresolved entry isget-started/build-app, already broken onmaster.node scripts/agents.jsre-run;docs/AGENTS.mdindex updated.