Skip to main content
The TxLINE scores feed delivers granular sports score data that can be validated against on-chain Merkle roots. Current documentation covers soccer, US football, and basketball score encodings, with World Cup and International Friendlies coverage available through the free tiers where enabled. Every supported stat is encoded with deterministic keys and published through batches whose roots are anchored on Solana. Use the feed-specific pages for stat-key encoding, and use the Schedule and API responses to confirm current fixture availability. For on-chain validation, use On-Chain Validation. The current examples include both legacy validateStat requests and validateStatV2 multi-stat strategies through the runnable devnet scripts in Runnable Devnet Examples. For final match outcome settlement, scores records with action=game_finalised use statusId=100 and period=100 on the current devnet and mainnet releases. That gives integrations a single final-outcome marker independent of whether the match ended in regulation, extra time, penalties, or abandonment.

​
Built for Settlement & Micro-Markets

This feed is built for applications that need deterministic event data and proof-based settlement.
  • Deterministic Encoding: Every stat maps to a fixed cryptographic key with period multipliers applied on top.
  • Reliable Proofs: If you are building automated smart contract settlement logic or validation proofs, the exact layout schemas are defined in the technical specifications below.
  • Network-Aware Access: Use mainnet credentials with mainnet APIs and devnet credentials with devnet APIs.

​
Technical Capabilities

Scout-Sourced Data

Direct-from-stadium collection removes broadcast lag and delay vulnerabilities.

Deterministic Architecture

Fixed-key encoding tailored for programmatic trade settlement and smart contracts.

High-Availability Pipelines

Redundant infrastructure engineered for zero data loss during peak tournament events.
If a live stream is connected but no data messages arrive, there may be no covered fixture actively producing updates at that moment. Check the Schedule, keep the stream open during live windows, or use historical endpoints for completed fixtures.