Path Protocol

Path Protocol is a prediction market infrastructure protocol built on Solana, designed to serve as an underlying platform for developers and front-end operators rather than a consumer prediction market in its own right. Launched in late 2025, the project aims to solve two persistent challenges in decentralized prediction markets: bootstrapping liquidity without requiring upfront capital from the protocol or liquidity providers, and achieving decentralized, credibly neutral resolution.

Infrastructure Layer Approach

Rather than competing head-on with consumer-facing prediction market apps, Path Protocol positions itself as the base layer — handling market creation, liquidity mechanics, and resolution infrastructure — while allowing third-party operators to build their own branded interfaces on top. A permissionless platform registry lets any developer deploy a prediction market front-end using Path Protocol's shared infrastructure and earn a share of protocol revenue. This architecture targets builders rather than end-users directly, functioning closer to an application framework than a standalone venue.

Market Creation and Structure

Markets on Path Protocol use standardized templates covering binary (yes/no), scalar (numeric range), and categorical (multi-outcome) formats. Each market is represented as a Program Derived Address (PDA) on Solana, keeping the structure non-custodial and fully on-chain. Markets progress through explicitly defined states: PROPOSED → ACTIVE → RESOLVING → DISPUTED → RESOLVED → CLOSED. Because Solana programs cannot self-execute, external keeper bots — referred to as "crank turners" — trigger each state transition.

Phased Dynamic LMSR AMM

The core liquidity mechanism is a phased implementation of the Logarithmic Market Scoring Rule (LMSR), a well-established automated market maker model for prediction markets. Path Protocol adapts LMSR into a two-phase design to address the cold-start liquidity problem.

In the bounding phase, a market operates in buy-only mode, accumulating real capital into a pool before any two-sided trading begins. This removes the need for the protocol to seed markets with its own reserves and prevents thin early markets from generating heavily distorted prices.

Once the real pool reaches a sufficient level, the market enters the active phase, where virtual reserves are layered over the real pool to provide consistent, liquid pricing throughout the market's life. Dynamic fees ranging from 1 to 30 basis points apply to trades, adjusting with market conditions.

Resolution Architecture

Resolution uses a tiered commit-reveal oracle system with three levels.

Automated resolution handles the majority of markets — approximately 80% — through median aggregation from multiple independent oracle sources, with outlier detection applied to prevent manipulation from any single feed.

Staked resolver voting covers around 15% of cases where automated resolution is insufficient. Resolvers stake $PATH tokens and submit votes using a commit-reveal scheme: votes are first submitted as hashed commitments, then revealed after the commit window closes, preventing frontrunning and collusion during the voting period.

Byzantine fault-tolerant consensus handles disputed outcomes, with a resolution design targeting a 67% fault tolerance threshold.

Timing constraints are built into the process: after a market closes, resolvers have a 30-minute window for oracle reports, followed by a one-hour commit period and a 24-hour challenge window before resolution finalizes. The maximum total resolution timeframe including disputes is seven days.

Resolvers face economic penalties for incorrect resolutions, with a 10% slashing penalty on staked $PATH. The protocol also requires total resolver stake to equal at least 10% of a market's volume to maintain adequate economic security. Where provable randomness is needed, the protocol integrates with Switchboard VRF.

$PATH Token

The protocol's native token is $PATH, with a total supply of one billion tokens. The initial distribution allocates 20% (200 million tokens) to a public launch and 80% to a project allocation subject to a six-month linear vesting schedule.

$PATH serves four functions within the protocol. First, it secures resolution: a minimum of 10,000 $PATH is required to register as a resolver, with stake size determining voting weight alongside an accuracy-based reputation multiplier. Second, token holders receive tiered fee discounts based on holdings ranging from 1,000 to 100,000+ $PATH. Third, stakers receive 30% of protocol fees, with the remaining 70% directed to a treasury. Fourth, $PATH is required to pay market creation fees, which run $5–$50 per market, with 50% of each fee burned.

The baseline protocol fee is 0.1% on all trading volume. Path Protocol's whitepaper notes that all fee structures and financial projections are preliminary and subject to change. The $PATH token contract address on Solana is 8eHeSgFm9Rb43TYfPNQ4woaeK2189B3JEA7NzWk1jupx.

Security Design

The commit-reveal voting design and multi-source oracle aggregation provide structural defenses against common prediction market attack vectors including frontrunning, oracle manipulation, and Sybil attacks. Sybil resistance is reinforced through the minimum stake requirement for resolvers. No independent third-party security audit has been publicly disclosed in the documentation available at launch.

Ecosystem Context

Path Protocol enters a Solana prediction market landscape that expanded significantly through 2025 and into 2026, with Polymarket integrating Solana, Phantom adding access to Kalshi's regulated markets, and new dedicated protocols emerging on-chain. Path Protocol's infrastructure-and-SDK model distinguishes it from consumer venues by targeting builders — offering white-label solutions, revenue share for platform operators, and modular market templates — rather than trying to aggregate end-users directly.

Solana's throughput and low per-transaction costs suit prediction markets well, reducing friction for the frequent small trades that characterize these venues. The protocol's non-custodial PDA architecture and keeper-based state management align with Solana's programming model.

Path Protocol's team has not been publicly identified in available documentation. The project maintains an active presence on X under the handle @predictonpath, with its official site at pathtech.io and technical documentation at docs.pathtech.io.