Solana native routing layer Read the docs
Cons
Docs Open App

Cross chain routing.
Simplified.

Token CA Coming Soon

Built natively on Solana

Networks

    One interface for tokens and messages.
    Cons finds the path.

    Open App Docs
    Cons/Routes/New token route
    Best RouteIllustrative

    Discovering routes

    ProviderCostETASecurityStatusScore

    Speaks Solana natively

    • Program
    • PDA
    • Instruction
    • Account
    • Mint
    • SPL Token
    • Token 2022
    • Token Account
    • CPI
    • Signature

    Cons discovers routes, compares providers and confirms delivery.

    Discover routes. Every compatible path, found in one call.

    Compare providers. Cost, speed and security, side by side.

    Confirm delivery. One status model from signature to receipt.

    One route.
    Every chain.

    Integrate once. Cons handles the paths.
    Routing01

    Describe the intent.
    Cons finds the path.

    Tokens and messages share one engine, one lifecycle and one receipt.

    Token routing. Assets resolved by mint, never by ticker alone.

    Message routing. Arbitrary payloads to programs and contracts. Delivery and execution tracked apart.

    • AvailabilityRequired
    • Cost
    • Speed
    • Security
    • Reliability

    Route intelligence. Eligibility first. Then cost, speed, security and health.

    Solana to Base · 100 USDC Illustrative
    ProviderCostETASecurityStatus

    Route comparison. Every eligible provider, normalized into one view.

    1. Created
    2. Submitted
    3. In Transit
    4. Received
    5. Confirmed
    Retrying Failed Expired Cancelled

    CREATED

    One lifecycle. Every provider state maps to nine Cons states.

    Route receiptConfirmed
    Request
    Request ID
    Source
    Solana signature
    Destination
    Base tx hash
    Provider
    Selected route
    Submitted
    timestamp
    Confirmed
    timestamp

    Unified receipt. Solana signature and destination ID in one record.

    Reliability02

    Reliable by design.
    Explicit by default.

    Every trust assumption stays visible and selectable.

    • Provider AActive
    • Provider BActive
    • Provider CActive
    • Provider DDegraded
    • Provider EPaused
    Illustrative

    Provider health. Supported is not the same as usable. Cons checks both.

    Retry and fallback. Retry repeats the route. Fallback switches it, only when policy allows.

    Multi path messaging. Require two of three confirmations before a message counts.

    • Provider A
    • Provider B
    • Provider C
    • Provider D

    3 eligible routes

    Provider policy. Allowlist the providers your application trusts. Try it.

    Solana native03

    Native to Solana.
    Honest about the rest.

    Deterministic rules live on chain. Dynamic routing stays off chain.

    Program and PDAs

    SPL Token and Token 2022

    Signatures in every receipt

    Developers04

    Ship cross chain
    like a single call.

    One interface. One status model. Multiple providers.

    transfer.tsInterface
    const route = await cons.transfer({
  sourceChain: "solana",
  destinationChain: "base",
  token: "USDC",
  amount: "100",
  recipient,
  priority: "cost"
})

route.status  // IN_TRANSIT
    • One interface

      Routes, quotes and requests through one SDK and API.

    • One status model

      Provider states normalized into Cons states.

    • Provider adapters

      Quote, prepare, send, status and verify. Same shape everywhere.

    • Normalized receipts

      Chain specific IDs without forcing one hash format.

    • Route commitment

      A signed request cannot silently switch routes.

    • Observability

      Signatures, program errors and retries in one view.

    Integrate once.
    Route everywhere.

    No bridge by bridge integrations.

    Open App
    1. 01Describe the intent

      Source, destination, asset or payload, and policy.

    2. 02Cons selects the route

      Eligible routes compared. One committed.

    3. 03Track one receipt

      From Solana signature to confirmation.