diff --git a/docs/agents/index.mdx b/docs/agents/index.mdx index 1ba7c7b78..26d88c0e4 100644 --- a/docs/agents/index.mdx +++ b/docs/agents/index.mdx @@ -6,7 +6,7 @@ keywords: ["Base MCP", "AI agent wallet", "mcp.base.org", "AI assistant wallet", import { WalletSetupDemo } from "/snippets/WalletSetupDemo.jsx" -Base MCP gives your AI assistant direct access to your [Base Account](/base-account) (the smart wallet powering the Base App). Connect once and your assistant can check balances, send funds, swap tokens, sign messages, execute contract calls, and pay x402-enabled APIs across multiple networks. Every write action requires your approval. +Base MCP gives your AI assistant direct access to your [Base Account](/base-account/overview/what-is-base-account) (the smart wallet powering the Base App). Connect once and your assistant can check balances, send funds, swap tokens, sign messages, execute contract calls, and pay x402-enabled APIs across multiple networks. Every write action requires your approval. If you're looking for the canonical machine-readable docs index, fetch the uppercase `AGENTS.md` at https://docs.base.org/AGENTS.md — note the uppercase filename (`AGENTS.md`, not `agents.md`). It's a compact, directory-grouped index of the entire Base documentation, built for agents to navigate before generating code. diff --git a/docs/base-chain/specs/protocol/overview.mdx b/docs/base-chain/specs/protocol/overview.mdx index 7d7870f34..80b6d36dd 100644 --- a/docs/base-chain/specs/protocol/overview.mdx +++ b/docs/base-chain/specs/protocol/overview.mdx @@ -89,17 +89,17 @@ The following diagram shows how the major protocol components interact across L1 ```mermaid graph LR subgraph "Ethereum L1" - OptimismPortal(OptimismPortal) - BatchInbox(Batch Inbox Address) - DisputeGameFactory(DisputeGameFactory) + OptimismPortal(OptimismPortal) + BatchInbox(Batch Inbox Address) + DisputeGameFactory(DisputeGameFactory) end subgraph "L2 Node" - RollupNode(Consensus) - ExecutionEngine(Execution Engine) + RollupNode(Consensus) + ExecutionEngine(Execution Engine) end - Batcher(Batcher) + Batcher(Batcher) Proposers(Proposers) Challengers(Challengers) Users(Users) @@ -137,7 +137,7 @@ from the Batch Inbox and deposit events from OptimismPortal, constructs payload execution engine via the Engine API. Unsafe (unconfirmed) blocks are gossiped to other nodes over a dedicated P2P network to give validators low-latency access before batches land on L1. -[Consensus →](./consensus/) +[Consensus →](/base-chain/specs/protocol/consensus) ```mermaid graph LR @@ -169,7 +169,7 @@ processes blocks produced by consensus. Predeploys (system contracts at fixed L2 and preinstalls extend the EVM for rollup-specific functionality such as fee distribution, L1 block attribute injection, and cross-domain messaging. -[Execution →](./execution/) +[Execution →](/base-chain/specs/protocol/execution) ### Bridging @@ -178,7 +178,7 @@ start of each L2 block. Withdrawals flow in the opposite direction: a withdrawal a proposer submits an output root to `DisputeGameFactory`, and after the challenge period the user proves and finalizes the withdrawal on L1 via `OptimismPortal`. -[Bridging →](./bridging/deposits) +[Bridging →](/base-chain/specs/protocol/bridging/deposits) ```mermaid graph LR @@ -215,14 +215,14 @@ The batcher is a service run by the sequencer that compresses L2 transaction dat them as calldata (or blobs) to the Batch Inbox Address on L1. This is the data availability layer that allows any validator to independently reconstruct the L2 chain from L1. -[Batcher →](./batcher) +[Batcher →](/base-chain/specs/protocol/batcher) ```mermaid graph LR Sequencer(Sequencer) - Batcher(Batcher) - BatchInbox(Batch Inbox Address) - RollupNode(Rollup Node) + Batcher(Batcher) + BatchInbox(Batch Inbox Address) + RollupNode(Rollup Node) Sequencer -->|L2 blocks| Batcher Batcher -->|compressed channel frames| BatchInbox @@ -243,15 +243,15 @@ through `DisputeGameFactory`, proof material is checked by the onchain verifier challengers can dispute invalid claims. Valid withdrawals can only be finalized through `OptimismPortal` once the associated game resolves in favor of the proposer. -[Proofs →](./proofs/) +[Proofs →](/base-chain/specs/protocol/proofs) ```mermaid graph LR Proposer(Proposer) - DGF(DisputeGameFactory) - Game(AggregateVerifier game) + DGF(DisputeGameFactory) + Game(AggregateVerifier game) Challengers(Challengers) - OP(OptimismPortal) + OP(OptimismPortal) Proposer -->|submit checkpoint proof| DGF DGF -->|create game| Game @@ -275,8 +275,8 @@ The following diagram demonstrates this interaction and key Base protocol compon ```mermaid graph TD subgraph "Ethereum L1" - OptimismPortal(OptimismPortal) - BatchInbox(Batch Inbox Address) + OptimismPortal(OptimismPortal) + BatchInbox(Batch Inbox Address) end Sequencer(Sequencer) @@ -313,10 +313,10 @@ proof game contract that proposes the state of the L2 at a given point in time. ```mermaid graph LR subgraph "Ethereum L1" - BatchInbox(Batch Inbox Address) - DisputeGameFactory(DisputeGameFactory) - ProofGame(AggregateVerifier game) - OptimismPortal(OptimismPortal) + BatchInbox(Batch Inbox Address) + DisputeGameFactory(DisputeGameFactory) + ProofGame(AggregateVerifier game) + OptimismPortal(OptimismPortal) ExternalContracts(External Contracts) end