1. Introduction and Scope
1.1 Purpose
This Technical Specification (Yellow Paper) is the engineering companion to the Baseline Protocol Overview (White Paper). Where the White Paper defines what Baseline is and why it exists, this document defines how it works at the level of data structures, algorithms, and operational requirements.
This specification is intended for:
- Engineers building the Baseline Verification Engine
- Developers integrating with the Baseline API
- Validators implementing the replay protocol
- Auditors evaluating the correctness of verification outputs
1.2 Normative Language
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC 2119.
1.3 System Boundaries
The Baseline system comprises four primary subsystems:
Data Ingestion Layer — Real-time on-chain event streaming, social content aggregation, and market data collection from supported chains and external sources.
Verification Engine — The constrained runtime that evaluates claims against evidence using versioned methods and produces Verification Objects.
Attestation Network — The validator infrastructure (inherited from FirmaChain) that replays verifications and produces cryptographic attestations.
Product Layer — API services, web interfaces, and AI agent systems that present Verification Objects to end users. Products are views over verification.
1.4 Supported Chains
| Chain | Chain ID | Finality Model | Evidence Sources |
|---|---|---|---|
| Solana | solana |
Slot-based (32 conf) | Account state, tx logs, program events |
| Ethereum | ethereum |
Block-based (12 conf) | State trie, event logs, trace data |
| Base | base |
Block-based (L2 seq) | State trie, event logs |
| Arbitrum | arbitrum |
Block-based (L2 seq) | State trie, event logs |
Adding a new chain requires:
- Defining chain-specific
EvidenceSourceTypeentries (Section 3.2) - Implementing canonical form mappings for BCE (Section 3.4)
- Specifying finality parameters and block anchor semantics
- Registering chain in the
ChainRegistry
1.5 Relationship to FirmaChain
Baseline is built on the foundation of FirmaChain, a Cosmos SDK blockchain. The native token LINE (formerly FCT) powers the verification economy. The existing validator set transitions to support verification replay duties. This specification assumes the FirmaChain network layer as given infrastructure and focuses on the verification-specific protocol extensions.