# Starknet v0.14.3 (Updated)

- Space: [Starknet](https://snapshot.box/sn:0x009fedaf0d7a480d21a27683b0965c0f8ded35b3f1cac39827a25a06a8a682a4.md)
- Author: 0x0557a9c5f4248a1a06a20180ccf5afc49212143d572bdbea45da7028047a4680
- State: Passed
- Voting type: Basic
- Start: 2026-06-19 14:15 UTC
- End: 2026-06-26 14:15 UTC
- Votes: 508
- Discussion: https://community.starknet.io/t/starknet-0-14-3-pre-release-notes/116211
- Open in Snapshot: https://snapshot.box/#/sn:0x009fedaf0d7a480d21a27683b0965c0f8ded35b3f1cac39827a25a06a8a682a4/proposal/15

## Results

- For: 94.6%
- Against: 5.4%
- Abstain: 0.0%

## Proposal

## Summary

The community previously approved Starknet v0.14.3 for Mainnet. Since that vote, the release scope has been expanded with two additional features and one additional breaking change, and the deployment timeline has shifted. This proposal brings the updated v0.14.3 to a vote for Mainnet deployment.

Updated timeline: Testnet (Sepolia) on 22 June 2026, with Mainnet deployment targeted for 6 July 2026.

---

## Changes from the previous vote

The following items are new in this version and were not part of the proposal approved in the previous vote:

**New features**

-   **Keccak support for client-side proving (SNIP-36):** the SNIP-36 verifier within the Starknet gateways will support virtual OS blocks that contain invocations of the keccak builtin, enabling virtual private transactions signed with EVM signatures.
    
-   **Quantum-resistant SNOS hash:** the hash used to calculate the "program hash" and "config hash" in the Starknet core contract moves from the Pedersen hash function to the quantum-secure Blake hash function.
    

**New breaking change**

-   **SNIP-36 breaking changes:** the new keccak-supporting verifier is incompatible with proofs generated under v0.14.2. Prover services integrated with SNIP-36 flows must be upgraded simultaneously with the version upgrade to remain operational.
    

**Updated timeline**

-   Testnet moved from 9 June to **22 June 2026**.
    
-   Mainnet moved from 22 June to **6 July 2026**.
    

Everything else from the previously approved version is unchanged: the dynamic L2 gas base fee (SNIP-35), more frequent blocks (SNIP-40), RPC 0.8 deprecation, the candidate soft deprecation, and the SNIP-40 breaking changes.

---

## What's included

### Dynamic L2 gas base fee (SNIP-35)

v0.14.3 introduces an automatic algorithm that adjusts the minimum base fee in line with the STRK price, per [SNIP-35](https://community.starknet.io/t/snip-35-automatically-adjust-base-fee-to-strk-price/116168). This keeps fees more stable and predictable relative to real-world value rather than nominal STRK amounts.

### More frequent (and on average, smaller) blocks (SNIP-40)

Following [SNIP-40](https://community.starknet.io/t/snip-40-more-frequent-blocks/116203), v0.14.3 reduces block times to lower overall latency. Adjacent changes:

-   Target L2 gas per block reduced by 30% (maximum block size unchanged)
    
-   Read and write L2 gas amounts increased to compensate
    

### Keccak support for client-side proving (SNIP-36) — _new_

The SNIP-36 verifier within the Starknet gateways will support virtual OS blocks that contain invocations of the keccak builtin. The goal is to support virtual private transactions signed with EVM signatures.

### Quantum-resistant SNOS hash — _new_

The hash used to calculate the "program hash" and "config hash" in the Starknet core contract will be the quantum-secure Blake hash function, replacing the Pedersen hash function used so far. This is a forward-looking hardening step against future quantum threats.

---

## Breaking changes

**1. RPC 0.8 deprecation**  
RPC version 0.8 (introduced May 2025) is no longer supported as of v0.14.3. Full nodes and SDKs will not ship new versions supporting it. Applications should migrate to RPC 0.9 or 0.10.1 (recommended).

**2. Candidate status (soft deprecation)**  
v0.14.3 improves communication between the feeder gateway and full nodes. As part of this, the feeder gateway will no longer return executed transactions to full nodes before their execution results are known. This does not break any full-node interface; applications can still request candidate transactions, but latency here will be no better than "preconfirmed."

**3. SNIP-40 breaking changes**

-   Although SNIP-40 increases the maximum transaction size, a transaction that was valid before SNIP-40 could in theory become too large to execute if it makes thousands of writes and sits right at the threshold.
    
-   Full nodes must be upgraded before v0.14.3 to keep gas estimations aligned with SNIP-40 recommendations.
    

**4. SNIP-36 breaking changes — _new_**  
The new keccak-supporting verifier is incompatible with proofs generated under v0.14.2. Prover services integrated with SNIP-36 flows must be upgraded simultaneously with the version upgrade to remain operational.

---

## Conclusion

This updated v0.14.3 carries everything from the previously approved version and adds two features, keccak support for client-side proving (SNIP-36) and a quantum-resistant SNOS hash via the Blake hash function, along with the associated SNIP-36 breaking change. Because these additions expand the scope of what was previously approved, we are bringing the updated release back to a vote.

The upgrade is being deployed on testnet so the community can review it before the vote. We encourage all community members to review the upgrade on testnet and share feedback on the forum. Voters with voting power are invited to vote on whether to approve the updated Starknet v0.14.3 for Mainnet deployment.

---

## Links

-   [v0.14.3 pre-release notes](https://community.starknet.io/t/starknet-0-14-3-pre-release-notes/116211)
    
-   [SNIP-35: Automatically adjust base fee to STRK price](https://community.starknet.io/t/snip-35-automatically-adjust-base-fee-to-strk-price/116168)
    
-   [SNIP-40: More frequent blocks](https://community.starknet.io/t/snip-40-more-frequent-blocks/116203)
    
-   [SNIP-36: In Protocol S-TWO Verification](https://community.starknet.io/t/snip-36-in-protocol-proof-verification/116123)

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

