# Blocksize RPC-NCN: Verifiable High-Assurance Infrastructure for the Jito Ecosystem

**URL:** <https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928>\
**Category:** JIP - Drafts\
**Created:** [February 6, 2026, 10:14pm UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928 "2026-02-06T22:14:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Blocksize\_JF](https://avatars.discourse-cdn.com/v4/letter/b/848f3c/32.png) [@Blocksize\_JF](https://forum.jito.network/u/Blocksize_JF)\
**Post date:** [February 6, 2026, 10:14pm UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/1 "2026-02-06T22:14:35Z")

</div>

**1. Title and Category  
Title:** Draft JIP: Blocksize RPC-NCN: Verifiable High-Assurance Infrastructure for the Jito Ecosystem

**Category:** Treasury (NCN Grant)

**2. Abstract**

Blocksize RPC-NCN is a verifiable infrastructure layer that transforms Solana RPC from a commodity service into a cryptographically enforced financial product. By utilizing multi-operator BLS signing and threshold agreements, we provide Proof-of-Latency and Proof-of-Correctness. This enables high-value actors (Solvers, DeFi Keepers) to automate risk management with measurable economic guarantees backed by JTO restaking, creating a sustainable, non-inflationary yield source for the Jito DAO.

**3. Motivation**

Currently, Solana RPC infrastructure operates on “blind trust.” High-stakes users have no economic recourse if a provider delivers stale data or suffers from hidden latency. By launching a Jito-secured NCN, we allow the DAO to capture a share of the premium RPC market. This proposal aligns with JIP-24 and JIP-29 by diversifying JTO yield beyond MEV tips and establishing a professionalized “Verified Tier” for Solana infrastructure.

**4. Key Terms**

- **NCN:** Node Consensus Network.

- **Proof-of-Latency:** A cryptographic attestation proving a response was delivered within a specific time window.

- **BLS Signing:** Compact signatures allowing multiple nodes to verify a single piece of data efficiently.

- **SLA Insurance:** JTO-backed collateral used to compensate users if performance targets are missed.

**5. Specification**

The project consists of three core technical pillars:

1. **Operator Node (Rust):** A high-performance proxy for local BLS signing with \<2ms overhead.

2. **Aggregation Gateway (TypeScript):** A router that consolidates signatures and verifies data correctness.

3. **On-Chain Registry (Anchor):** Solana programs managing operator bonds, slashing hooks, and reward distribution. Development Status: Our [PoC is live on GitHub](https://github.com/BSC-aujl/RPC-NCN), with the core program already deployed to Testnet.

**6. Benefits/Risks**

- **Benefits:** Generates non-inflationary yield (USDC fees); provides institutional-grade reliability to Solana; secures JTO utility through slashing/bonding.

- **Risks:** Technical complexity of maintaining sub-5ms p99 overhead; market adoption of new premium tiers. These are mitigated by our partnerships with Fragmetric and Kayros for initial liquidity and operator support.

**7. Outcomes**

The primary outcome is the establishment of a “Verified RPC” market generating $350,000+ in annualized Economic Value (EV). Success will be measured by the volume of “Verified Requests” and a subsequent yield distributed to JTO restaking vaults.

 ![Screenshot 2026-02-06 at 4.12.17 PM](https://us1.discourse-cdn.com/jito/original/1X/240d139990bdb02b0d9c92fbc35d66e5fb09a105.png)

**8. Cost Summary**

**Total Request:** 150,000 JTO (Tier 2) and Delegations

- **Engineering (60%):** Rust/TS development and signature optimization.

- **Economic Security (20%):** Anchor contracts and reward engines.

- **Infrastructure & Security (20%):** Global test node deployment and external code audit.

**9. Performance Milestones delivery approximations**

- **Milestone A (Week 6):** Devnet live; benchmark report proving \<2ms signing overhead.

- **Milestone B (Week 12):** Public Testnet with external operators; Live Economic Value Dashboard.

- **Milestone C (Week 18):** Integration with first Pilot Partner (Solver/Bot); first fee distribution to Jito Vaults.

- **Milestone D (Week 24):** Mainnet RC; Validation of $250k+ EV target for final grant unlock.

---

<div class="post-metadata">

**Author:** ![drnick](https://sea1.discourse-cdn.com/jito/user_avatar/forum.jito.network/drnick/32/187_2.png) [@drnick](https://forum.jito.network/u/drnick)\
**Post date:** [February 10, 2026, 10:41am UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/2 "2026-02-10T10:41:23Z")

</div>

Interesting idea, although approved for spend. We still need to spin up the strategy related to NCN grants. Monitor the forum here and I’ll chase that forward and see where the grant committee is at on it’s decision making on what to do with that programme.

---

<div class="post-metadata">

**Author:** ![Blocksize\_JF](https://avatars.discourse-cdn.com/v4/letter/b/848f3c/32.png) [@Blocksize\_JF](https://forum.jito.network/u/Blocksize_JF)\
**Post date:** [February 18, 2026, 1:54pm UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/3 "2026-02-18T13:54:10Z")

</div>

Sounds great! Would love to learn more as soon as the Grant Committee decides on how to move forward with this. We are eager to move forward with this and continue building.

---

<div class="post-metadata">

**Author:** ![drbsc](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@drbsc](https://forum.jito.network/u/drbsc)\
**Post date:** [February 18, 2026, 2:02pm UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/4 "2026-02-18T14:02:20Z")

</div>

BLS-backed SLAs for RPC is a gap that’s been ignored too long. Full support, hope the committee moves on this.

---

<div class="post-metadata">

**Author:** ![aujl](https://sea1.discourse-cdn.com/jito/user_avatar/forum.jito.network/aujl/32/318_2.png) [@aujl](https://forum.jito.network/u/aujl)\
**Post date:** [March 2, 2026, 2:56pm UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/5 "2026-03-02T14:56:26Z")

</div>

In order to provide some encouragement / help with prototyping said strategy: why not move this proposal ahead from the draft stage or, at least, elaborate which are the requirements to do so?

The RPC-NCN provides real value, as it solves an open trust issue with RPC requests using an NCN.

As such, it presents a good case to flesh out the NCN grants program strategy in a proof-of-concept.

---

<div class="post-metadata">

**Author:** ![sang](https://sea1.discourse-cdn.com/jito/user_avatar/forum.jito.network/sang/32/323_2.png) [@sang](https://forum.jito.network/u/sang)\
**Post date:** [March 4, 2026, 4:08am UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/6 "2026-03-04T04:08:56Z")

</div>

From my perspective, the primary bottlenecks for sophisticated Solana operators are service stability under stress and predictable tail latency, rather than additional endpoint availability. The multi-operator architecture with routing/aggregation outlined here appears well-suited to improving reliability and reducing correlated failures, and the emphasis on clearer accountability and incentives is directionally aligned with what the ecosystem needs.

Fragmetric is open to supporting early adoption (including pilot integrations) and is also open to delegating as a protocol operating the top vault on Jito (Re)staking. If Blocksize can demonstrate strong real-world p99 performance and uptime, particularly during periods of elevated network volatility, we believe there is a credible path for a high-assurance RPC tier to become a default choice for serious onchain operators.

---

<div class="post-metadata">

**Author:** ![aujl](https://sea1.discourse-cdn.com/jito/user_avatar/forum.jito.network/aujl/32/318_2.png) [@aujl](https://forum.jito.network/u/aujl)\
**Post date:** [April 28, 2026, 8:06am UTC](https://forum.jito.network/t/blocksize-rpc-ncn-verifiable-high-assurance-infrastructure-for-the-jito-ecosystem/928/7 "2026-04-28T08:06:51Z")

</div>

The KelpDAO exploit was, at its core, based on tampered unverified RPC responses.  
Verified RPC services like the one that RPC-NCN aims to deliver can prevent such exploits.

Ref.: [https://www.chainalysis.com/blog/kelpdao-bridge-exploit-april-2026/](https://www.chainalysis.com/blog/kelpdao-bridge-exploit-april-2026/)