# Notice of Deprectation For RPC 0.6 and 0.7

**URL:** <https://community.starknet.io/t/notice-of-deprectation-for-rpc-0-6-and-0-7/116074>\
**Category:** 🆙 Versions Upgrade\
**Created:** [November 24, 2025, 4:05pm UTC](https://community.starknet.io/t/notice-of-deprectation-for-rpc-0-6-and-0-7/116074 "2025-11-24T16:05:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![eitanm-starkware](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eitanm-starkware](https://community.starknet.io/u/eitanm-starkware)\
**Post date:** [November 24, 2025, 4:05pm UTC](https://community.starknet.io/t/notice-of-deprectation-for-rpc-0-6-and-0-7/116074/1 "2025-11-24T16:05:12Z")

</div>

# **Starknet RPC Deprecation Notice: RPC 0.6 and 0.7**

As part of Starknet’s ongoing effort to modernize and standardize the JSON-RPC interface, we are announcing the deprecation of **RPC versions 0.6 and 0.7**. These versions will be phased out in accordance with the timeline below.

This deprecation ensures that all ecosystem participants transition toward the newer, fully spec-compliant RPC versions that offer improved correctness, consistency, and long-term support for Cairo and future protocol upgrades.

* * *

## **Deprecation Timeline**

### **RPC 0.6**

- **Deprecation date:**  **December 10, 2025**

### **RPC 0.7**

- **Deprecation date:**  **January 1, 2026**

**After these dates:**

- RPC 0.6 and 0.7 will not be updated to support new Starknet versions (as was de-facto the situation starting v0.14)
- Providers and node clients may remove support for these versions entirely.
- Users must migrate to RPC **0.8+** to ensure continued compatibility.

* * *

## **Recommended Migration Path**

To ensure continuity of service, developers and node operators should transition to RPC 0.8 (introduced May 2025), RPC 0.9 (introduced Sep 2025) or RPC 0.10 (introduced Dec 2025). RPCs will be supported for at least one year after their introduction, to keep update schedule predictable

These versions include:

- Consistent type definitions across all endpoints
- Standardized contract class handling
- More robust error codes and execution metadata
- Alignment with the direction of the Starknet RPC spec going forward

* * *

## **Required Action**

If your application, indexer, SDK, or infrastructure provider currently uses endpoints in **RPC 0.6 or 0.7**

**Begin upgrading immediately** to avoid additional service interruptions.

Please verify your tooling (clients, bindings, ABIs, indexers, block explorers, wallets) for any hardcoded RPC version assumptions.

—

## **Support**

If you need guidance migrating to newer RPC versions, the Starknet team is available to assist.  
Feel free to reach out to us on Telegram or Discord