AI content updates#17994
Conversation
…into ai-content-updates
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
UI polish pass on the two landing pages.
/ai-agents/banner: add breathing room around the info Alert./ai-agents/: convert the four capability bullets (Programmable wallets, Verifiable inference, Machine payments, Agent identity) into aCardGrid, matching the pattern used on other use-case pages./decentralized-ai/: add breathing room around the three inline Alerts (Are you a builder?,Early blockchain media authenticity proofs,Before using AI wallet tools).
All suggestions are one-click committable. Rationale per comment.
konopkja
left a comment
There was a problem hiding this comment.
Scannability pass: proposing bold on key phrases across both landing pages.
Scope.
/ai-agents/ethereum/: 22 paragraph-level suggestions covering the lead paragraph of each section and the load-bearing paragraphs elsewhere./decentralized-ai/: 19 suggestions following the same pattern.
Principles applied.
- Bold 1 to 3 phrases per paragraph. Beyond that, bold loses signal.
- Target phrases that carry the claim. A scanner should reconstruct the section by reading only the bold.
- Skip paragraphs whose lead is already bold (
session keys,x402 protocol,Zero-knowledge machine learning,Censorship-resistance, etc.) and pure-link lists. - No wording, punctuation, or link changes. One exception flagged inline: the typo
auditabileon/decentralized-ai/line 31.
All suggestions are one-click committable.
Co-authored-by: Jakub <100724231+konopkja@users.noreply.github.com>
Co-authored-by: Jakub <100724231+konopkja@users.noreply.github.com>
Jakub edits to content/decentralized-ai/index and content/ai-agents/ethereum/index Co-authored-by: Jakub <100724231+konopkja@users.noreply.github.com>
…into ai-content-updates # Conflicts: # src/intl/en/template-usecase.json
b12b63c to
927a051
Compare
Co-authored-by: Jakub <100724231+konopkja@users.noreply.github.com>
Co-authored-by: Jakub <100724231+konopkja@users.noreply.github.com>
Co-authored-by: Jakub <100724231+konopkja@users.noreply.github.com>
…into ai-content-updates # Conflicts: # src/intl/en/common.json # src/lib/nav/buildNavigation.ts
phipsae
left a comment
There was a problem hiding this comment.
Hi everyone,
Really nice and comprehensive work on this.
I gave the /ai-agents/ landing page a read and left some comments, mostly around a few claims that could use softening or a citation, plus the agents-vs-bots table. Happy to look at the other pages next if helpful.
Let me know if some comments are unclear.
Best, Philip
| summaryPoint3: Hires humans or other agents for work | ||
| alt: Developer working with AI agent architecture on Ethereum | ||
| summaryPoint1: Programmable wallets with spending limits and session keys | ||
| summaryPoint2: Verifiable behavior via zkML proofs and TEE attestations |
There was a problem hiding this comment.
Verifiable behavior via TEE attestations today, with zkML proofs emerging for smaller models.
| AI agents are software programs that observe their environment, make decisions, and take actions, including sending transactions, paying for services, and interacting with smart contracts, without requiring human input on every step. | ||
|
|
||
| On Ethereum, we’re seeing innovations of AI agents ranging from virtual influencers and autonomous content creators to real-time market analysis platforms, empowering users by delivering insights, entertainment, and operational efficiency. | ||
| Ethereum provides the infrastructure these agents need: programmable wallets that enforce spending limits, verifiable computation that proves an agent followed its rules, open payment rails for machine-to-machine commerce, and a permissionless identity layer that any application can verify. These are **not properties that a centralized server can replicate**, because they depend on a network that no single party controls. |
There was a problem hiding this comment.
- "verifiable computation that proves an agent followed its rules": Reads like Ethereum provides this already today
- "not properties that a centralized server can replicate": a centralized server can publish enforce spending limits, zk proofs, TEE attestations --> better framing about who controls the rules and can change or shut them down
| | -------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------- | | ||
| | **Decision-making** | Autonomous; adapts to new inputs and conditions | Rule-based; executes fixed, pre-programmed logic | | ||
| | **Learning** | Can update behavior from real-time data and feedback | Operates on pre-trained data or hardcoded rules | | ||
| | **Onchain identity** | Holds a programmable wallet, can sign and send transactions | Typically reads data; does not hold assets | |
There was a problem hiding this comment.
Also bots can hold wallets (e.g. trading bots)
| | **Decision-making** | Autonomous; adapts to new inputs and conditions | Rule-based; executes fixed, pre-programmed logic | | ||
| | **Learning** | Can update behavior from real-time data and feedback | Operates on pre-trained data or hardcoded rules | | ||
| | **Onchain identity** | Holds a programmable wallet, can sign and send transactions | Typically reads data; does not hold assets | | ||
| | **Composability** | Can discover and interact with any open protocol | Limited to the APIs it was explicitly integrated with | |
There was a problem hiding this comment.
dynamic discovery vs. static integration
| | **Learning** | Can update behavior from real-time data and feedback | Operates on pre-trained data or hardcoded rules | | ||
| | **Onchain identity** | Holds a programmable wallet, can sign and send transactions | Typically reads data; does not hold assets | | ||
| | **Composability** | Can discover and interact with any open protocol | Limited to the APIs it was explicitly integrated with | | ||
| | **Guardrails** | Enforced by smart contract logic (spending limits, session keys, allowlists) | Enforced by the operator's server configuration | |
There was a problem hiding this comment.
a bot could also hold a smart contract with sessions keys, etc.
| In traditional finance, AI agents often operate in centralized environments with limited data inputs. This hinders their ability to learn or manage assets autonomously. | ||
| | | AI agents | AI bots | | ||
| | -------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------- | | ||
| | **Decision-making** | Autonomous; adapts to new inputs and conditions | Rule-based; executes fixed, pre-programmed logic | |
There was a problem hiding this comment.
- "Rule-based; executes fixed, pre-programmed logic": thats more an algorithm not AI, maybe drop AI in front of bot
| | **Onchain identity** | Holds a programmable wallet, can sign and send transactions | Typically reads data; does not hold assets | | ||
| | **Composability** | Can discover and interact with any open protocol | Limited to the APIs it was explicitly integrated with | | ||
| | **Guardrails** | Enforced by smart contract logic (spending limits, session keys, allowlists) | Enforced by the operator's server configuration | | ||
| | **Verification** | Behavior can be proven onchain via zkML or TEE attestations | Behavior is attested only by the operator | |
| ## AI agents vs AI bots {#ai-agents-vs-bots} | ||
|
|
||
| In traditional finance, AI agents often operate in centralized environments with limited data inputs. This hinders their ability to learn or manage assets autonomously. | ||
| | | AI agents | AI bots | |
There was a problem hiding this comment.
Maybe just bots? AI bots contradicts with AI agents
| | **ERC-4337** — Smart account standard | Production EntryPoint deployments on all major networks (v0.7 widely adopted; v0.8, v0.9 also live) | | ||
| | **ERC-8004** — Onchain agent identity registry | Draft — in active adoption; live on 20+ chains since January 2026 | | ||
| | **x402** — Machine-to-machine HTTP payments | Production-ready since Q1 2026 | | ||
| | **L2 transaction cost** | $0.001–$0.003 per operation | |
There was a problem hiding this comment.
Maybe: sub-cent to low-cents per operation
Resolves conflicts from PR 18198 (Topic layout consolidation) landing in dev while PR 17994 introduced AiAgents as another per-template layout. The AiAgents layout is replaced by a TopicConfig (src/data/topics/ai-agents.ts) plus an aiAgentsComponents bundle (HubCard, CardGrid). Layout wiring: src/layouts/index.ts maps ai-agents to TopicLayout + topicComponents.aiAgentsComponents. src/layouts/md/ folder deleted. i18n: src/intl/en/page-ai-agents.json renamed to template-ai-agents.json with every key prefix renamed accordingly; src/lib/utils/translations.ts LAYOUT_NAMESPACES["ai-agents"] points at template-ai-agents. Types: src/lib/interfaces.ts takes dev's TopicFrontmatter shape (with hideEditBanner); AiAgentsFrontmatter and StakingFrontmatter removed. src/lib/types.ts Frontmatter union drops the removed types. Compile pipeline: src/lib/md/compile.ts taken as-is from dev (sizeOf for image dimensions, async extractLayoutFromMarkdown). src/lib/md/data.ts updated to await extractLayoutFromMarkdown. Content: public/content/ai-agents/index.md uses template: ai-agents and summaryPoints array. All nine ai-agents sub-pages converted from summaryPoint1/2/3 keys to summaryPoints array so the new TopicLayout hero renders the description list. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
- Updates non-English versions as well given no manifest established yet -- string value to be re-translated via intl-pipeline
- Converts html to markdown where it suffices, removing custom className alignment
- Removes `variant="info"` from ui/alert ("info" variant used by default)
same here on main https://deploy-preview-17994--ethereumorg.netlify.app/ai-agents/getting-started/ |
- Remove custom margin overrides within markdown usage of `Alert` component - Apply minimal 2rem top and bottom margins broadly to the `Alert` component for all markdown usage via `MdComponents/index.tsx` (additional margins from components above or below will automatically collapse and not add together)
Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
- Updates [svg] to [svg:not(.lucide-external-link)] for SVG coloring in alert variants - Avoids re-coloring the external link arrow within Alert component Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Handled automatically via layout using `title` front matter Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
- Removes redundant `const Pre` declaration in `Static` layout Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>
Co-Authored-By: wackerow <54227730+wackerow@users.noreply.github.com>




Description
Builder pages added
Layout and components
Navigation changes:
Deviations from original Issue scope:
body text to match faqItems schema answers, eliminating "on this page" references, and removing substantive content (contract addresses, SDK lists) that only appeared in one location
Note: Original change to add FAQ JSON schemas reverted per @wackerow - FAQ schemas will be updated site-wide rather than bespoke implementation on this PR
Related Issue