The universal verification layer for the autonomous economy
Powering verifiable services with trustless execution at internet scale.
Blocksense is a zkRollup-based oracle network for verifiable data and compute. It lets developers deploy programmable oracle scripts that bring real-world data on-chain without gatekeeping or centralized curation.
From DeFi price feeds to prediction markets, gaming oracles, and verifiable AI agent workflows. You define the logic, sources, and frequency to support both traditional and next-gen oracle use cases.
Blocksense offers programmable feeds, SDK-based deployment (with full self-serve coming soon), and ZK-powered batching that reduces on-chain publishing costs by up to an order of magnitude. Unlike curated oracle networks, Blocksense enables custom, long-tail, and vertical-specific data feeds.
Zero-knowledge proofs validate feed execution and voting correctness without revealing votes or identities. Blocksense batches thousands of updates into a single zkRollup block for gas-efficient publishing. ZK is also used for compression, consensus, and upcoming zkTLS interactions with the internet. And last but surely not least, ZK enables the SchellingCoin consensus mechanism, pioneered in other protocols, to become truly collusion-proof and bribery-resistant in Blocksense.
You can start by integrating existing feeds or building your own using the Blocksense SDK. The SDK lets you define oracle scripts with specific data sources, logic, and update conditions. The network handles execution, reporting, and delivery across EVM chains, rollups, and ZK-based systems.
Blocksense is live with programmable oracle feeds on a trusted validator set of industry-leading node operators. Upcoming milestones include permissionless deployment, zkTLS-powered read/write, request/response models, and general-purpose compute. zkSchellingCoin launches in late 2025 alongside expansions into risk modeling, AI inference, and appchain integrations.
Blocksense uses randomized, secret committees and concealed votes. Reporters are incentivized to vote honestly using SchellingCoin game theory. ZK proofs verify vote integrity without revealing voter identities.
Committees are chosen randomly and secretly. Reporters cannot prove how they voted, making bribery and collusion irrational and unprofitable.
zkSchellingCoin is our upcoming consensus upgrade. It verifies reporter voting off-chain and proves correctness on-chain. Mainnet integration is expected in late 2025.
Anyone can run a reporter node by staking and connecting to the network. Nodes automatically fetch scripts, execute them, and submit secret votes. Public node participation is supported today with minimal coordination.
Learn more about running a node with Blocksense.
The SDK lets you define your own feeds by specifying sources, thresholds, aggregation logic, and more. Scripts are written in JavaScript or any language that compiles to WebAssembly (WASM), enabling high-performance, portable logic.
Not yet. While the SDK is permissionless in design, current deployments require coordination with our team. Full self-service deployment is in progress.
Scripts can query APIs, websites, and custom endpoints. zkTLS (on the roadmap) will allow smart contracts to read from and write to HTTPS endpoints in a verifiable, privacy-preserving way.
The SDK supports smoothing, source weighting, failovers, and custom aggregation strategies. It’s ideal for stables, LRTs, LP tokens, or emerging assets.
We support fully customizable feed logic. While the SDK allows granular config, most feeds today are deployed with our assistance. If you need something specific, our team can create a custom feed with your preferred settings.
Reach out to learn more at hi@blocksense.network or submit a ticket on Discord.
Yes. Any chain that supports ZK proof verification — whether EVM, rollup, or appchain — can use Blocksense. We’re compatible with Chainlink and RedStone interfaces for easy migration.
Most likely. Blocksense is built for rapid integration with new chains. If the chain can verify proofs (e.g. Halo2, Kimchi, Plonky2), we can onboard quickly.
Reach out to learn more at hi@blocksense.network or submit a ticket on Discord.
By batching updates in a zkRollup architecture, Blocksense reduces gas usage significantly—often 10 to 50 times lower than legacy oracles. This makes frequent updates affordable even for long-tail assets.
Costs vary by feed frequency, size, and destination chain. There are no licensing or setup fees. Builders only pay for what they use. Contact us for a pricing estimate.
Yes, it's on the roadmap. Pull-model feeds and on-demand queries will complement current push-based feeds and allow even more flexible integrations.
Feeds are updated based on configurable logic — by time (heartbeat), price deviation, or a combination of both. You can tune update frequency to match gas efficiency and latency needs.
Latency depends on your feed configuration. Updates can occur within seconds to minutes, depending on thresholds and batching. High-frequency feeds are supported via optimized rollup cycles.
Yes. Our oracle model uses Schelling-point consensus to resolve real-world events like elections or sports. Only the majority outcome is revealed, while individual votes remain secret.
Blocksense supports verifiable AI inference using a ZK consensus model. Instead of reproducing the entire LLM execution on-chain, reporters prove that the output came from top-K token rankings. This method is already live in testnet.
Yes. Our peg-aware feeds adjust behavior based on asset conditions. They return smoothed values when in-peg and switch to live market pricing when depegged, protecting lenders and minimizing bad debt risk.
Soon. zkTLS will allow smart contracts to read from and write to HTTPS endpoints. This opens up use cases like KYC verification, proof of off-chain actions, and real-world data sync.
Yes, coming soon. The next SDK upgrade supports general-purpose outputs like strings, booleans, and JSON objects. Ideal for AI results, document verification, or conditional logic.
Most likely, yes. If your use case involves verifiable external data and deterministic logic, you can build it with the SDK. We're actively supporting everything from proof-of-reserves to exotic metrics.
