Description
Build on vibenet — Base's devnet for native account abstraction (EIP-8130) and payer gas sponsorship (ERC-8168) using viem's eip8130 module. Use whenever the user mentions vibenet, EIP-8130, ERC-8168, 8130 accounts, native account abstraction, session keys, actors, policies, payers, or gas sponsorship on Base — or is writing code that creates or operates 8130 smart accounts, authorizes session-key actors, sends batched calls, sponsors gas with a payer, or wires a frontend/script against the vibenet devnet or Base Sepolia.
SKILL.md
Vibenet
Vibenet is Base's devnet for EIP-8130 native account abstraction: account
abstraction in the protocol itself. Accounts are portable across EVM chains,
support multiple signer types (secp256k1, P-256, WebAuthn), key rotation
without changing address, scoped session-key actors, on-chain policies, and
native ERC-8168 gas sponsorship. The tooling lives in viem's eip8130
module (fork branch — not yet in npm viem).
Network
| Endpoint | Value |
|---|---|
| Chain ID | 84538453 |
| Public execution RPC | https://rpc.vibes.base.org — 8130-capable (AA_TX_TYPE / 0x79), serves access-control-allow-origin: * |
| Browser RPC proxy | https://api.vibes.base.org/api/vibenet/account/rpc — passes through all eth_*, including 0x79 broadcasts and receipt polling |
| Hosted payer (ERC-8168) | https://api.vibes.base.org/api/vibenet/account/payer |
| Faucet | POST https://api.vibes.base.org/api/vibenet/faucet/drip with { "address": "0x…" } |
| Faucet status | GET https://api.vibes.base.org/api/vibenet/faucet/status — drip size, cooldowns, USDV/NFV token addresses |
| Chain health | GET https://api.vibes.base.org/api/vibenet/chain-health — { healthy, head, headAgeSecs, … } |
| Landing page / explorer | https://chain.base.org/vibenet, https://chain.base.org/vibenet/explorer |
| Base Sepolia (also 8130-enabled) | https://sepolia.base.org, chain id 84532 |
The API host is api.vibes.base.org, not vibes.base.org. The bare host
302-redirects to the chain.base.org/vibenet HTML page; viem's HTTP transport
then tries to parse that as JSON and throws Unrecognized token '<', which
reads like a code bug rather than a wrong URL.
All api.vibes.base.org endpoints (RPC proxy, payer, faucet) send permissive
CORS headers, and so does rpc.vibes.base.org — so browser apps can talk to
either. Prefer rpc.vibes.base.org for execution and reserve the account/rpc
proxy for when you specifically want the hosted path.
The 8130 modules are additive to viem itself, proposed upstream in
wevm/viem#5004 (still an open draft —
not yet released to npm). Until it ships, they have to be built from the fork
branch the PR is opened from: chunter-cb/viem feat/eip-8130-production.
Use the bundled installer — it does the whole clone→build→link dance, which is error-prone by hand:
scripts/setup-viem-8130.sh [APP_DIR] # defaults to the current directory
When PR #5004 merges and a viem release ships the modules, this collapses to
npm install viem@latest — the imports (viem/eip8130, viem/eip8168) and
APIs are unchanged, so no code moves.
What the script does, and why each step is needed
The tooling is not installable from git directly: viem's workspace uses
pnpm's catalog: protocol, so npm install "viem@github:…" fails outright, and
bun add "viem@github:…" "succeeds" but leaves you an unbuilt monorepo with no
exports field. So you clone, build, then depend on the built package (which
lives in viem's src/):
git clone -b feat/eip-8130-production https://github.com/chunter-cb/viem viem-fork
cd viem-fork && npx pnpm install --ignore-scripts && npx pnpm run build
# then in your app — --install-links is required:
npm install --install-links "viem@file:../viem-fork/src"
--install-links is required. Without it npm symlinks node_modules/viem
to a path outside the project root, and Turbopack/Next.js then fails with
Module not found: Can't resolve 'viem' for a package that is plainly there
(tsc resolves it fine, which makes it look like a bundler bug).
Then import from viem/eip8130 (and viem/eip8168 for payers). Core helpers
like createPublicClient / parseEther come from plain viem — the 8130
module does not re-export them.
If your TypeScript build rejects the module's BigInt literals, set
"target": "ES2020" or later in tsconfig.json. Next.js 16's generated config
already works as-is, since its lib includes esnext.
Accounts Have No Deploy Step
Creating an account derives a CREATE2 address locally — synchronous, zero RPC,
eth_getCode still 0x. It becomes real as a side effect of its first
transaction, which carries account.createChange alongside your actual calls.
There is nothing else to call. The shortest path from nothing to a deployed
account is a sponsored first tx (no faucet, no funding); the self-paid route
needs the address funded first. Read deployment state from eth_getCode, never
from optimistic local state — it decides whether the next tx carries
createChange. Full lifecycle:
references/eip8130-accounts.md.
Safety Guardrails
- Never commit private keys — generate throwaway keys for devnet scripts, read real ones from env vars.
key.k1(...)builds an actor identity, not a signer — passing it (or a raw private-key hex) assignerfails with an opaquepad()TypeError. UseprivateKeyToAccount(pk).- Verify config changes by on-chain read-back (
isActor/getConfigSequence), never by receipt logs orstatus: success— a skipped authorize is silent. - Read the live config sequence right before signing — a hardcoded sequence causes silent no-ops.
Task Routing
Read the reference for your task:
| Task | When to Use | Reference |
|---|---|---|
| Accounts & transactions | Create an 8130 smart account, the counterfactual→deployed lifecycle, send batched calls, attribution metadata, gas estimation, reading account state, locking, gotchas | references/eip8130-accounts.md |
| Session keys & policies | Authorize/revoke actors, scopes, SessionPolicy spend limits, config sequences, verifying "silent" changes | references/session-keys-and-policies.md |
| Gas sponsorship | Sponsor gas with a payer (ERC-8168), gasless onboarding, send vs sign modes | references/payer-sponsorship.md |
Operating Procedure
- Classify the task using the table above and read the relevant reference before implementing.
- Pick the right RPC:
rpc.vibes.base.orgworks from both Node and the browser;api.vibes.base.org/api/vibenet/account/rpcis the hosted proxy to the same chain. Nevervibes.base.org— that host is not an API. - Implement with explicit chain id, the
scripts/setup-viem-8130.shinstall, and read-back verification for any account-config change. - Deliver runnable code, install commands, and any manual steps (env vars, faucet funding).
For Edge Cases and Latest API Changes
- EIP-8130 spec: eip.tools/eip/8130 (payer standard: eip.tools/eip/8168)
- viem fork:
chunter-cb/viemfeat/eip-8130-production(upstream PR: wevm/viem#5004; API surface:src/eip8130/index.ts; docs:site/pages/eip8130) - Deep guide (chaptered):
github.com/chunter-cb/eip-8130-web(/guide/*) - Session-key walkthrough: gist.github.com/chunter-cb/bf70c53a5ab6d8361ce7f4215b776114
Installation
npx skills add base/skills --skill vibenet