# Starknet v0.14.2

- Space: [Starknet](https://snapshot.box/sn:0x009fedaf0d7a480d21a27683b0965c0f8ded35b3f1cac39827a25a06a8a682a4.md)
- Author: 0x0557a9c5f4248a1a06a20180ccf5afc49212143d572bdbea45da7028047a4680
- State: Passed
- Voting type: Basic
- Start: 2026-04-09 16:00 UTC
- End: 2026-04-16 16:00 UTC
- Votes: 451
- Discussion: https://community.starknet.io/t/0-14-2-pre-release-notes/116146
- Open in Snapshot: https://snapshot.box/#/sn:0x009fedaf0d7a480d21a27683b0965c0f8ded35b3f1cac39827a25a06a8a682a4/proposal/11

## Results

- For: 100.0%
- Against: 0.0%
- Abstain: 0.0%

## Proposal

**Introduction**  
This proposal outlines the planned upgrade to Starknet `v0.14.2`, as detailed in the pre-release notes and accompanying SNIPs. The upgrade includes `SNIP-36`, `SNIP-37`, and `SNIP-13`, alongside transparent internal changes that prepare the network for the decentralized validation phase described in `SNIP-33`, planned for completion later this year.

Starknet `v0.14.2` addresses three primary goals:

- **Enabling in-protocol proof verification:** Introduce support for in-protocol S-Two proof verification, reducing calldata and cost constraints for privacy-focused and zk-thread applications.
- **Revising storage economics:** Align storage access costs more closely with the actual resources consumed by the sequencer and the network, while preserving cost-effectiveness for developers.
- **Upgrading StarkGate token contracts:** Standardize ERC-20 event behavior and introduce additional contract improvements to support better indexing, verification, and token handling.

This vote concerns the full `v0.14.2` release package, rather than the individual SNIPs separately.

**Vote Details**  
A vote will be conducted to determine the approval or rejection of the Starknet `v0.14.2` upgrade, which includes the following changes:

- In-protocol S-Two proof verification (`SNIP-36`)
- Revised storage access costs (`SNIP-37`)
- StarkGate token contract upgrade to `v3.0.0` (`SNIP-13`)
- Transparent internal preparations for decentralized validation (`SNIP-33`)

**Key Features**

**1. In-Protocol Proof Verification (`SNIP-36`)**  
Starknet `v0.14.2` enables in-protocol S-Two proof verification, supporting privacy-focused and zk-thread applications by allowing transactions to reference offchain execution. New optional `proof` and `proof_facts` fields are introduced in the `Invoke V3` transaction structure, and a new version of the `get_execution_info` syscall (`v3`) is available for contracts to retrieve these facts.

While verification is currently handled by Starknet consensus, this significantly reduces the cost and calldata constraints previously associated with submitting large proofs. See `SNIP-36` for full details.

**2. Revised Storage Access Costs (`SNIP-37`)**  
This version significantly increases storage pricing while reducing the base L2 gas price to offset this change. The update aims to align storage costs more closely with the actual resources consumed by the sequencer and the network, ensuring Starknet remains cost-effective for state-intensive applications while maintaining network sustainability. See `SNIP-37` for full details.

**3. Changes to StarkGate Token Contracts (`SNIP-13`)**  
The StarkGate contracts will be upgraded to `v3.0.0`. The standard ERC-20 `Transfer` and `Approval` events are updated to include indexed parameters, allowing offchain indexers and frontend applications to query and filter token movements more efficiently by specific addresses. This is a breaking change, and dApps relying on the previous event format should prepare in advance.

Several non-breaking changes are also included:

- Contracts are migrated to a Scarb project, enabling code verification on Voyager
- An L1 handler function allows Starknet L1 addresses to call `approve`, enabling the release of tokens mistakenly sent to an active L1 address
- The bridged StarkGate USDC contract symbol changes from `USDC` to `USDC.e` following the launch of Circle’s native USDC on Starknet

**4. Further Transparent Changes**  
Version `0.14.2` includes changes that are fully transparent to external users and do not affect network behavior. These changes prepare the network for the decentralized validation phase described in `SNIP-33`, planned for completion later this year. These changes include improvements to the p2p protocol between nodes, weighted sampling of the next proposer, and the creation of the internal notion of a `virtual proposer`.

**Benefits**

- **Expanded privacy infrastructure:** Enables lower-friction support for privacy-focused and zk-thread applications through in-protocol proof verification.
- **Improved economic alignment:** Brings storage pricing closer to real network costs while maintaining a more balanced fee structure.
- **Better token standard consistency:** Improves ERC-20 event indexing and unifies StarkGate token behavior across the ecosystem.
- **Progress toward decentralization:** Introduces internal preparations needed for the next stage of decentralized validation.

**Breaking Changes**  
This upgrade includes breaking changes. In particular:

- `SNIP-36` changes block hash calculations
- `SNIP-37` may affect whether some transactions remain executable under the new storage pricing model
- `SNIP-13` changes ERC-20 event indexing, so indexers and integrations relying on the previous format should update

For full details, see the linked SNIPs and pre-release notes.

**Links**  
-  Pre-release notes: [link](https://community.starknet.io/t/0-14-2-pre-release-notes/116146)
- `SNIP-36`: [link](https://community.starknet.io/t/snip-36-in-protocol-proof-verification/116123)
- `SNIP-37`: [link](https://community.starknet.io/t/snip-37-revisit-storage-access-cost/116143)
- `SNIP-13`:  [link](https://github.com/starknet-io/SNIPs/blob/main/SNIPS/snip-13.md)
- `SNIP-33`:  [link](https://community.starknet.io/t/snip-33-proposal-for-starknet-decentralized-validation/115811)

**Conclusion**  
Starknet `v0.14.2` expands the network’s privacy infrastructure, improves the alignment of storage economics with actual resource usage, and advances token standard consistency across the ecosystem. It also introduces transparent internal changes that prepare Starknet for the next stage of decentralized validation.

We encourage all community members to participate in this vote.  
Please vote **For**, **Against**, or **Abstain**.

---

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

