name: base-technical
description: "Deep technical specifications for Base-specific protocols (ERC-8004, x402, Basenames, Smart Wallets, Builder Rewards)."
metadata:
{
"openclaw":
{
"emoji": "⚡",
"requires": {},
},
}

Base Technical Specifications

Deep technical specs for Base protocols that BAiSED advocates for. Use when precision is required for implementation.

Guidelines

1. Precision is Key: Reference specific constants (e.g., 0.005 ETH fee) from instruction files
2. Flow Accuracy: Describe technical flows exactly as defined — don't simplify to the point of error
3. Code First: Provide implementation snippets from spec files when asked
4. Builder Value: Link technical features to Builder Rewards to show economic alignment

Core Protocols

ERC-8004 Identity Registry

• Contract: 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 (Base mainnet)
• Discovery fee: 0.005 ETH
• Purpose: Decentralized identity verification and discovery

x402 HTTP Payment Protocol

• Flow: 402 Response → Payment Selection → Settlement → Access
• Currencies: USDC on Base (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
• Methods: ERC-3009, Permit2

Basenames (.base names)

• Registrar Controller: 0x4cCb0720c37C1658477b9C7A3aEBb87f1a067292
• Registry: 0xb94704422c2a1e396835a571837aa5ae53285a95
• Pricing: 5+ chars ~$5/yr, 4 chars ~$50/yr, 3 chars ~$500/yr

Smart Wallets (Account Abstraction)

• EntryPoint: 0x0576a174D229E3cFA37253523E645A78A0C91B57 (ERC-4337)
• Paymaster: Gas sponsorship for seamless UX
• Integration: Works with Basenames and ERC-8004

Builder Rewards

• Scoring: Based on onchain activity, documentation, ecosystem contributions
• Distribution: Through verified ERC-8004 identities
• Goal: Incentivize real building over speculation

Implementation Patterns

x402 Client Flow

// 1. Initial request
const response = await fetch('/protected-resource');

// 2. Handle 402 Payment Required
if (response.status === 402) {
  const paymentHeader = response.headers.get('PAYMENT-REQUIRED');
  const paymentInfo = JSON.parse(atob(paymentHeader));

  // 3. Construct payment
  const paymentPayload = {
    amount: paymentInfo.amount,
    currency: paymentInfo.currency,
    method: 'erc3009'
  };

  // 4. Submit with signature
  const retryResponse = await fetch('/protected-resource', {
    headers: { 'PAYMENT-SIGNATURE': btoa(JSON.stringify(paymentPayload)) }
  });
}

ERC-8004 Identity Registration

// Register identity with 0.005 ETH fee
function registerIdentity(
    bytes32 identityHash,
    bytes memory data
) external payable {
    require(msg.value >= 0.005 ether, "Insufficient fee");
    // Registration logic
}

When to Use This Skill

• User asks about protocol specifications
• Implementation details needed for Base-specific features
• Contract addresses or exact fees required
• Technical architecture discussions
• Building on Base infrastructure

Reference the full instruction files in the baised-skills repo for complete implementation details.