Skip to main content

Overview

Use this page for the public mainnet values needed by TxLINE integrations. Keep the Solana RPC, program ID, TxL mint, guest JWT host, activation endpoint, and API host on the same network.
Do not activate a mainnet transaction on the devnet API host. A mainnet subscription transaction must be activated with https://txline.txodds.com.

Mainnet Values

Activation

After subscribe(serviceLevelId, durationWeeks) confirms, activate the API token by signing this exact message with the same wallet that submitted the transaction:
For the standard free bundle, selectedLeagues = [], so the message is:
Send the detached wallet signature as base64 in walletSignature, and send the guest JWT from the mainnet host as Authorization: Bearer <jwt>.

Validation Accounts

The epoch day is the number of whole UTC days since 1 January 1970: Math.floor(timestampMs / 86_400_000). The aligned epoch day rounds it down to a multiple of 10. See Epoch Day for details.
Derive the epoch day from the timestamp in the proof response, never from Date.now(). For scores and odds V4 validation, use payload.ts; for fixtures, use snapshot.Ts. Recompute it for every proof.

Ticket Accounts

These accounts belong to the booking and V4 validation instructions. They apply on mainnet once mainnet runs the program version that includes book_fixture, validate_fixture_for_tree, and close_worker_ticket.
The IDL does not embed PDA seeds for these accounts, so the seeds above are not read from it. fixtureId is encoded as 4 bytes.
domain and workerId are client-chosen. See On-Chain Validation for the sequence that uses them.

Score Validation

The public score validation endpoints: Book the fixture with book_fixture before validating it; see Booking Fixtures. Use a real seq value from an observed score record. For V4 validation, keep the requested statKeys order stable because strategy indexes refer to those same positions.