Architecture

Chain & Infrastructure

Deployed on Base. Built for one thing: non-human finance.

Why Base?

FIBOR deploys on Base — Coinbase's OP Stack L2 with native USDC support through Circle's partnership. This gives FIBOR access to existing liquidity, low gas costs, and fast confirmations without the overhead of bootstrapping a new chain.

Agent transactions are high frequency and low value. Base's sub-cent gas fees and two-second block times are ideal for this pattern. And because Base is built on the OP Stack, FIBOR inherits Ethereum-grade security without running its own sequencer or validator set.

Infrastructure

  • Ethereum-grade security inherited through Base's OP Stack architecture
  • Native USDC on Base — no bridging required for deposits
  • Sub-cent gas fees optimized for high-frequency agent transactions
  • Existing developer tooling, block explorers, and wallet support
  • Protocol-first — FIBOR focuses on credit infrastructure, not chain operations

What lives on the chain

FIBOR token

ERC-20 governance token

USDC

Native stablecoin on Base (Circle partnership)

FIBOR IDs

Persistent identity registry for all agents

FIBOR Scores

Real-time credit scores computed from onchain data

Credit pacts

Individual credit line terms and repayment windows

FiborAccounts

Bank accounts with checking, savings, and auto-repay

Revenue distribution

Automatic fee collection and depositor payouts

External integrations

  • USDC (Circle) — Native USDC on Base — the underlying asset for all protocol operations
  • Base (OP Stack L2) — Settlement, block production, inherited Ethereum L1 security
  • x402 Protocol — HTTP-native agent payment integration
  • Chainlink / API3 — Price feeds if needed for USD conversions

Graduation path

FIBOR launches on Base to access existing liquidity and tooling. When transaction volume justifies dedicated throughput and custom gas parameters, FIBOR can graduate to its own OP Stack appchain.

Because Base is itself OP Stack, this migration is a clean upgrade path — same EVM, same bridge architecture, same tooling. The contracts, identities, and credit histories port directly. But that's a decision for the future, driven by real demand.

Developer Reputationx402 Integration