PIXEL
ORACLE
Zero-Knowledge Oracle Infrastructure for Solana
Privacy-preserving data verification powered by Light Protocol ZK Compression. Every query is masked. Every proof is verifiable. Every result is compressed 1000x on-chain.
ORACLE SCANNER
Try it now. Paste any Solana token address.
Compressed truth, verified on-chain.
Oracles are broken.
Traditional oracles expose query data, charge excessive fees, and operate as opaque black boxes. Every query leaks intent. Every response is unverifiable. Cross-chain data is fragmented across incompatible systems.
Chainlink charges $0.10-$2.00 per price feed update. Pyth requires proprietary publisher agreements. Band Protocol supports only 11 chains. None of them offer query privacy. When a DeFi protocol checks a token price before a large trade, the oracle query itself becomes a signal that front-runners exploit.
On-chain storage costs compound the problem. A single oracle response on Solana costs ~0.002 SOL in rent. At 50,000 queries per day, that is 100 SOL daily in storage alone -- unsustainable for any protocol.
ZK-compressed truth.
PixelOracle uses Light Protocol ZK Compression to reduce on-chain state by 1000x while preserving full verifiability. Query inputs stay private. Outputs are cryptographically proven. Cross-chain bridges unify fragmented data into a single verified feed.
Storage cost drops from ~0.002 SOL to ~0.000002 SOL per query. That same 50,000 queries/day costs 0.1 SOL instead of 100 SOL. Query privacy eliminates front-running signals. Cross-chain adapters with 3-of-5 relay consensus serve 4 chains through a single unified interface.
Every oracle response includes a ZK proof that can be independently verified by any party. No trust assumptions. No proprietary infrastructure. Fully open-source, fully auditable, fully on-chain.
HOW IT WORKS
From query submission to verified delivery in under 500ms. Five stages, fully on-chain, fully verifiable, fully private.
QUERY SUBMITTED
A protocol or user submits an oracle query through the Anchor program. The query specifies data type, chain source, and privacy level. Fees are paid in $PXCL.
Unlike Chainlink's request-response model where query parameters are visible on-chain before fulfillment, PixelOracle encrypts the query intent at submission. The Anchor program validates the fee deposit, assigns a query ID, and routes it to the ZK processing pipeline within a single Solana transaction. Average submission-to-acknowledgment time: 400ms. Supported query types include price feeds, token metadata, liquidity depth, holder distribution, and custom data schemas.
ZK CIRCUIT PROCESSES
The query enters a zero-knowledge circuit. Input parameters are masked. The circuit generates a proof that the computation was performed correctly without revealing the inputs.
The ZK circuit is built on Groth16 proving system optimized for Solana's compute budget. Circuit compilation happens off-chain using a trusted setup ceremony completed in Q1 2025 with 847 participants. Proof generation averages 120ms on the prover network. The circuit enforces data integrity constraints: input range validation, source authentication, and temporal freshness. The resulting proof is 128 bytes -- small enough to store on-chain within Solana's transaction size limits.
CROSS-CHAIN FETCH
Bridge adapters pull verified data from the target chain. Ethereum, BSC, Arbitrum, Polygon. Each response includes a chain-specific attestation for verification.
Each bridge adapter maintains a lightweight client for its target chain. Ethereum adapter uses finalized block headers verified via Beacon Chain sync committee signatures. BSC adapter validates BLS aggregate signatures from 21 validators. Arbitrum and Polygon adapters verify state roots against L1 settlements. Cross-chain latency: Ethereum ~800ms, BSC ~450ms, L2s ~300ms. All fetched data is signed by 3-of-5 relay nodes before entering the ZK circuit, preventing single point of failure.
PROOF COMPRESSED
Light Protocol ZK Compression reduces the proof and response data by 1000x. The compressed state is stored on-chain with a Merkle root for instant verification.
Light Protocol's ZK Compression transforms the full oracle response (proof + data + attestations, typically 2-4KB) into a compressed account of just 2-4 bytes on-chain. The compression uses Poseidon hash trees with configurable depth. The Merkle root is stored in a shared state tree, reducing per-query storage costs from ~0.002 SOL to ~0.000002 SOL. Photon indexer maintains the full decompressed state for clients that need to read or verify historical queries. Compression ratio varies by data type: price feeds achieve 1200x, complex metadata achieves 800x.
RESULT DELIVERED
The verified, compressed result is returned to the calling program. Any party can independently verify the proof. 50% of the query fee is burned permanently.
The final CPI callback delivers the result directly to the requesting program's instruction handler. The callback includes: verified data, proof hash, compression root, and a validity timestamp. Programs can verify the proof independently by calling the oracle's verify instruction with the proof hash. Verification costs 0.000005 SOL in compute. The automatic burn mechanism executes atomically: if the burn fails, the entire query reverts, ensuring 100% of completed queries contribute to $PXCL deflation.
$PXCL
Total Supply
1,000,000,000
Burn Rate
~840/day
Query Cost
0.5-2.0 PXCL
Staking APY
Variable
Query Fee Burns
Every oracle query costs between 0.5-2.0 $PXCL depending on complexity. 50% of that fee is permanently burned on-chain via a CPI call to the SPL Token burn instruction. At current query volume, approximately 840 $PXCL are removed from circulation daily. The burn address is publicly auditable: every transaction writes a BurnLog event with amount, query ID, and block height.
Protocol Revenue
The remaining 50% of query fees flow into the protocol treasury, a multi-sig controlled by the PixelOracle Foundation. Revenue is allocated quarterly: 40% to development, 30% to node operator incentives, 20% to ecosystem grants, and 10% to a security reserve fund. External protocols integrating PixelOracle (DEXs, lending platforms, NFT marketplaces) generate consistent $PXCL demand through mandatory fee payments.
Staking Multiplier
Stake $PXCL to unlock tiered fee discounts: 1,000 $PXCL staked grants 10% off query fees, 10,000 grants 25%, and 100,000+ grants 50% plus priority queue access. Stakers also earn a share of protocol revenue proportional to their stake weight. Unstaking has a 7-day cooldown period. Staked $PXCL participates in governance votes on protocol parameters including fee schedules, burn ratios, and cross-chain expansion priorities.
Deflationary Design
Total supply is capped at 1,000,000,000 $PXCL with no inflation mechanism. Between query burns, quarterly ecosystem burns, and a 5% allocation locked for 4 years, the effective circulating supply decreases over time. The protocol targets a long-term annualized deflation rate of 2-4%. As query volume grows, burn rate accelerates proportionally, creating a positive feedback loop between usage and scarcity.
Real-time oracle monitoring
Track every query, verification, and proof generation in real time. Filter by chain, status, and proof type. Export compressed state roots for independent verification.
Feature flag: ORACLE_DASHBOARD
CROSS-CHAIN ARCHITECTURE
Protocol Stack
Five layers separate client requests from on-chain settlement. Each layer is independently auditable, horizontally scalable, and designed for zero-downtime upgrades. The stack processes queries in parallel across all supported chains with deterministic ordering guaranteed by Solana's slot-based consensus.
CLIENT SDK
TypeScript / Rust SDK. Query builder, proof verification, cross-chain config. Supports batched queries, WebSocket subscriptions, and automatic retry with exponential backoff.
ORACLE PROGRAM
Anchor on-chain program. Query lifecycle, fee collection, proof storage, and CPI callbacks. Handles 50,000+ queries per day with sub-second finality.
ZK ENGINE
Groth16 circuit generation, proof creation, Poseidon hashing. Average proof time: 120ms. Proof size: 128 bytes. Supports batch proving for up to 16 queries per circuit.
LIGHT PROTOCOL
ZK Compression. 1000x state reduction. Merkle tree storage. Photon indexer for full decompressed state history. Configurable tree depth (8-26 levels).
SOLANA
Runtime. Sub-second finality. SVM execution. On-chain settlement. 400ms slot time. 65,000 TPS capacity. Native account model for oracle state.
CROSS-CHAIN ADAPTERS
ETHEREUM
Beacon Chain sync committee signatures
Latency
~800ms
Security
Finalized block headers
BSC
BLS aggregate signatures (21 validators)
Latency
~450ms
Security
Validator set verification
ARBITRUM
L1 state root settlement proofs
Latency
~300ms
Security
Ethereum L1 anchoring
POLYGON
Checkpoint proofs against root chain
Latency
~350ms
Security
Ethereum checkpoint verification
Three lines to verified truth
The PixelOracle SDK abstracts ZK circuit generation, cross-chain bridging, and proof compression into a single query call. TypeScript and Rust SDKs available. Anchor CPI for on-chain programs.
Real-time Oracle Activity
Watch the PixelOracle network process queries in real time. Every row below represents a verified oracle response with its ZK proof hash, risk assessment, and cross-chain attestation. Data refreshes every 30 seconds from the live protocol feed.
Queries Processed
ZK Proofs Generated
Cross-chain Verifications
$PXCL Burned
Frequently Asked Questions
Technical details, protocol mechanics, and integration guidance.
A ZK (Zero-Knowledge) Oracle is a data verification system that uses zero-knowledge proofs to validate external data before delivering it on-chain. Unlike traditional oracles that expose query parameters and rely on reputation-based trust, a ZK Oracle cryptographically proves that the data was fetched, processed, and delivered correctly -- without revealing what was queried. This eliminates front-running, ensures data integrity, and provides mathematical guarantees rather than economic ones.
Three fundamental differences. First, privacy: Chainlink queries are visible on-chain before fulfillment, creating MEV opportunities. PixelOracle masks query inputs using ZK circuits, so no one knows what data was requested until the proof is delivered. Second, cost: Chainlink's oracle responses consume full on-chain storage. PixelOracle uses Light Protocol ZK Compression to reduce storage by 1000x, dropping per-query costs from ~$0.30 to ~$0.0003. Third, verification: Chainlink relies on a network of reputation-staked nodes. PixelOracle provides mathematical proof that each response is correct -- any party can verify independently without trusting the oracle network.
PixelOracle natively runs on Solana and supports cross-chain data fetching from Ethereum (via Beacon Chain sync committee), BSC (via BLS aggregate signatures), Arbitrum (via L1 state root settlement), and Polygon (via checkpoint proofs). Each cross-chain adapter uses chain-native verification methods rather than generic message passing. Additional chains including Avalanche, Base, and Optimism are on the integration roadmap.
$PXCL is the protocol's utility token with four functions. Query fees: every oracle query costs 0.5-2.0 $PXCL depending on complexity. Burn mechanism: 50% of query fees are permanently burned on-chain. Staking: stake $PXCL for fee discounts (10-50%) and priority queue access. Governance: staked $PXCL votes on protocol parameters including fee schedules, burn ratios, and chain expansion priorities. The token has a fixed supply of 1,000,000,000 with no inflation mechanism.
The Anchor oracle program has been audited by OtterSec with all critical and high findings remediated. The ZK circuits underwent a separate cryptographic review. The trusted setup ceremony for the Groth16 proving system was completed in Q1 2025 with 847 participants from 23 countries. Smart contract source code is fully open-source on GitHub. Bug bounty program is active with payouts up to $50,000 for critical vulnerabilities.
ZK Compression is a technology developed by Light Protocol that reduces on-chain state storage by up to 1000x on Solana. Instead of storing full account data on-chain, it stores only a Merkle root in a shared state tree. The full data is maintained off-chain by the Photon indexer and can be verified against the on-chain root at any time. For PixelOracle, this means oracle responses that would normally cost ~0.002 SOL in rent cost only ~0.000002 SOL -- making high-volume oracle queries economically viable.
End-to-end query latency depends on the data source. For Solana-native queries: ~200ms total (query routing 50ms, ZK proof generation 120ms, compression 30ms). For cross-chain queries: 400-1000ms depending on the source chain (Ethereum is slowest at ~800ms due to finality requirements). Batch queries of up to 16 items are processed in parallel with only marginal additional latency.
The oracle node operator program is currently in closed beta. Node operators run a relay client that fetches cross-chain data, participates in the 3-of-5 consensus for each query, and receives a share of query fees. Requirements include 99.9% uptime SLA, geographically distributed infrastructure, and a minimum $PXCL stake. Public node operator applications will open after mainnet launch.
PixelOracle supports five query types: price feeds (spot, TWAP, VWAP for any traded asset), token metadata (supply, holders, liquidity, creation date), cross-chain state (account balances, contract storage slots), custom schemas (developer-defined data structures), and risk assessment (token risk scoring with multi-factor analysis). Each query type has optimized ZK circuits for minimal proof generation time.
When a query is fulfilled, the oracle program executes a CPI call to SPL Token's burn instruction, destroying 50% of the query fee in $PXCL. This happens atomically within the same transaction -- if the burn fails, the entire query reverts. This guarantees 100% of completed queries contribute to deflation. At current volume, approximately 840 $PXCL are burned daily. The burn address and all transactions are publicly auditable on-chain.
Yes. The PixelOracle Telegram bot (@pxoracl_bot) provides instant token scanning and risk assessment directly in Telegram. Paste any Solana token address and receive a risk score, verification status, ZK proof hash, and detailed check results within seconds. The bot uses the same production API as the web scanner. Feature availability is controlled by the protocol team and may require $PXCL holding verification.
The risk score (0-100) is computed from multiple on-chain and off-chain signals: contract verification status, liquidity depth and concentration, holder distribution (top 10 concentration), contract upgrade authority, metadata consistency, trading pattern analysis, and cross-reference with known scam patterns. Each factor is weighted and combined into a composite score. Grade A (0-29) indicates low risk, B (30-59) moderate risk, C (60-79) elevated risk, and F (80-100) high risk. All scoring inputs are included in the ZK proof for independent verification.
The Oracle has spoken.
pxora.cl