Integrate the workflow
Use focused APIs and streams for market data, transaction construction, execution and order automation instead of stitching together unrelated providers.
Production trading infrastructure · private API access
Build the trading product. Not the trading stack.
PRION is a production trading system built around a live Solana indexer, Rust execution engine and private APIs for market data, transaction construction, automated orders and observable execution. It is built for competitive execution without surrendering wallet control.
Developer workflowSolana first
- 01ReceiveSolana account, transaction and event streams
- 02DecodeProtocol updates into typed state
- 03IndexPools, tokens, vaults and market history
- 04Quote + buildFresh wallet-bound transaction messages
- 05SignLocally at the client boundary
- 06SubmitThrough competitive landing infrastructure
- 07ObserveExact status, failures and recovery
One integration / complete workflow
Easy to adopt. Coherent by default. Built for competitive execution.
Keep state coherent
Move from live indexed state to a wallet-bound transaction and an observable outcome through one system with explicit freshness and failure boundaries.
Compete on execution
Keep latency-sensitive indexing, pricing and execution paths in Rust while treating submission, confirmation and recovery as distinct system concerns.
Private developer surface / selective access
Use one API capability or the whole path.
The production system exposes these capabilities privately today. Public developer access is staged, and exact market availability is confirmed during integration.
Market data
Live pool, token and trading state normalized across supported Solana venues.
OHLCV
Historical and streaming candles derived from the same indexed market activity.
Transaction construction
Fresh, wallet-bound transaction messages for client inspection and authorization.
Spot execution
Quote, build, submit and observe through an explicit asynchronous lifecycle.
Automated orders
Limit, DCA, copy-trading and launch workflows backed by the private execution system.
Transaction status
Separate submitted, processed, confirmed, finalized and failed outcomes with recovery after reconnects.
Architecture / fresh state
From chain state to an observable outcome.
PRION consumes Solana account and transaction streams, decodes protocol state and maintains execution-ready local indexes. Freshness is part of the contract: stale or incomplete inputs are rejected instead of silently becoming a transaction.
Receive
Solana account, transaction and event streams
Decode
Protocol updates into typed state
Index
Pools, tokens, vaults and market history
Quote + build
Fresh wallet-bound transaction messages
Sign
Locally at the client boundary
Submit
Through competitive landing infrastructure
Observe
Exact status, failures and recovery
Explicit custody boundary
Non-custodial.
Transactions are signed locally by the client.
Spot transactions require client authorization. Automated orders are constrained by explicit spending, expiry and revocation controls, while submission and confirmation remain distinct observable states.
Open source / hackathon contribution
The MIT-licensed PRION Devkit is the public submission. It makes selected boundaries executable without publishing the private production engine.
A public devkit you can run, inspect and challenge.
Replay real programs
Run reviewed, frozen mainnet state without RPC credentials or wallet secrets. Eleven narrow Solana variants have exact quote, build and runtime evidence.
Inspect the interface
Use versioned contracts, a strict TypeScript SDK, transaction inspector, loopback transport and runnable local-sign example.
Test stateful behavior
Exercise a fork-aware OHLCV reference core and a bounded, wallet-signed single-fill order lifecycle with deterministic evidence.
Current boundary / MVP gaps
Useful now. Deliberately incomplete.
The devkit proves bounded local behavior. It does not claim that a public hosted trading service or complete market integration ships with the hackathon repository.
Inspect the repository ↗- Gap 01Every public market remains disabled until complete conformance evidence exists.
- Gap 02The loopback server is deterministic local transport, not a hosted live API.
- Gap 03Live ingestion, hosted persistence, landing and full market variants remain outside the proven MVP.
- Gap 04Comparable, reproducible provider benchmarks are coming soon.
Solana depth / controlled release
Eleven market integrations in the private engine.
Private production coverage and public availability are different claims. The devkit contains bounded evidence for the same named inventory, while every public market remains disabled until its complete conformance gate passes.
Raydium AMM V4
Raydium CPMM
Raydium CLMM
Raydium LaunchLab
Orca Whirlpool
Meteora DAMM V1
Meteora DAMM V2
Meteora DLMM
Meteora DBC
Pump.fun
PumpSwap
EVM runtime in development
Performance evidence / coming soon
Reproducible benchmarks are coming soon.
PRION is built for competitive execution, but comparative numbers will not be published as product claims until the workloads, raw attempts, failures and environments can be reproduced.
Market-data freshness
Comparable assets, fields, completeness rules, regions and cache states.
Quote + build
Equivalent inputs, transaction semantics, wallet boundaries and failure accounting.
Send + land
Submission latency, inclusion, confirmation and cost reported as separate stages.
No public ranking until the evidence package ships
Review the benchmark plan ↗Private APIs / open source proof
Build against the complete trading path.
Tell us what your product needs from the private API surface, or run the separate public devkit and inspect the current MVP boundary today.