# SNIPs

**URL:** https://community.starknet.io/c/development-proposals/snip/7.md

[Latest](https://community.starknet.io/latest.md) · [Categories](https://community.starknet.io/categories.md) · [Tags](https://community.starknet.io/tags.md)

---

## [About the SNIPs category](https://community.starknet.io/t/about-the-snips-category/2780)

<div class="topic-metadata">

**Author:** [@system](https://community.starknet.io/u/system)\
**Replies:** 1\
**Last updated:** [October 12, 2024, 10:43am UTC](https://community.starknet.io/t/about-the-snips-category/2780 "2024-10-12T10:43:10Z")

</div>

Discussions about SNIPs (Starknet Improvement Proposals) SNIPs are managed in the SNIPs repository. The process of suggesting a SNIP (previously known as “SIMP”) is outlined by martriay in this post:

---

## [\[SNIP-40\]- More frequent blocks](https://community.starknet.io/t/snip-40-more-frequent-blocks/116203)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 0\
**Last updated:** [May 19, 2026, 6:00am UTC](https://community.starknet.io/t/snip-40-more-frequent-blocks/116203 "2026-05-19T06:00:42Z")

</div>

snip: SNIP-40 Title: More frequent blocks Description: Change starknet operational parameters for UX and congestion detection author: Ohad Barta, ohad@starkware.co discussions-to: \[SNIP-40\]- More frequent blocks status: …

---

## [SNIP 35 - Automatically adjust base fee to STRK price](https://community.starknet.io/t/snip-35-automatically-adjust-base-fee-to-strk-price/116168)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 1\
**Last updated:** [May 18, 2026, 5:10pm UTC](https://community.starknet.io/t/snip-35-automatically-adjust-base-fee-to-strk-price/116168 "2026-05-18T17:10:01Z")

</div>

snip: SNIP-35 Title: Automatically adjust base fee to STRK price description: Adjust the base fee of Starknet to the STRK price author: Ohad Barta, ohad@starkware.co discussions-to: SNIP 35 - Automatically adjust base f…

---

## [\# \[SNIP\] Pluggable Signer Interface for Smart Accounts](https://community.starknet.io/t/snip-pluggable-signer-interface-for-smart-accounts/116190)

<div class="topic-metadata">

**Author:** [@haycarlitos](https://community.starknet.io/u/haycarlitos)\
**Replies:** 0\
**Last updated:** [May 12, 2026, 12:57pm UTC](https://community.starknet.io/t/snip-pluggable-signer-interface-for-smart-accounts/116190 "2026-05-12T12:57:06Z")

</div>

\[SNIP\] Pluggable Signer Interface for Smart Accounts A standard signer trait, a canonical kind tag registry, and a tagged signature envelope so one Starknet smart account class can authenticate owners signing under any o…

---

## [SNIP 38 - strkBTC: Bitcoin on Starknet](https://community.starknet.io/t/snip-38-strkbtc-bitcoin-on-starknet/116174)

<div class="topic-metadata">

**Author:** [@robertkodra](https://community.starknet.io/u/robertkodra)\
**Replies:** 3\
**Last updated:** [April 27, 2026, 10:31am UTC](https://community.starknet.io/t/snip-38-strkbtc-bitcoin-on-starknet/116174 "2026-04-27T10:31:13Z")

</div>

snip: 38 title: strkBTC — Bitcoin on Starknet description: A federated Bitcoin wrapper on Starknet with a roadmap toward trust-minimized verification author: Henri Lieutaud (henri@starknet.org) discussions-to: SNIP …

---

## [SNIP 39 - strkBTC as a Stakable Token on Starknet](https://community.starknet.io/t/snip-39-strkbtc-as-a-stakable-token-on-starknet/116180)

<div class="topic-metadata">

**Author:** [@robertkodra](https://community.starknet.io/u/robertkodra)\
**Replies:** 0\
**Last updated:** [April 27, 2026, 10:24am UTC](https://community.starknet.io/t/snip-39-strkbtc-as-a-stakable-token-on-starknet/116180 "2026-04-27T10:24:41Z")

</div>

snip: 39 title: strkBTC as a Stakable Token on Starknet description: Approve strkBTC as an eligible BTC wrapper for staking on Starknet under the framework established in SNIP-31 author: Natan Granit (natan@starkware…

---

## [SNIP 50 - Introspection](https://community.starknet.io/t/snip-50-introspection/116111)

<div class="topic-metadata">

**Author:** [@kronosapiens](https://community.starknet.io/u/kronosapiens)\
**Replies:** 4\
**Last updated:** [March 25, 2026, 5:14pm UTC](https://community.starknet.io/t/snip-50-introspection/116111 "2026-03-25T17:14:30Z")

</div>

Abstract This SNIP proposes a standardized collection of types and events for describing onchain data, as well as a compact serialization scheme for wire transmission, enabling the development of generic indexers for eff…

---

## [RFC: Upgradeable Beacon Proxies for Shared Interfaces](https://community.starknet.io/t/rfc-upgradeable-beacon-proxies-for-shared-interfaces/116150)

<div class="topic-metadata">

**Author:** [@ericnordelo](https://community.starknet.io/u/ericnordelo)\
**Replies:** 0\
**Last updated:** [March 25, 2026, 9:02am UTC](https://community.starknet.io/t/rfc-upgradeable-beacon-proxies-for-shared-interfaces/116150 "2026-03-25T09:02:32Z")

</div>

I’ve been looking at whether a beacon proxy pattern makes sense on Starknet. My current view is yes, but only as a narrow, Starknet-specific standard for contracts that share a known interface, with some potential extens…

---

## [Snip 36: in protocol proof verification](https://community.starknet.io/t/snip-36-in-protocol-proof-verification/116123)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 6\
**Last updated:** [March 22, 2026, 8:11am UTC](https://community.starknet.io/t/snip-36-in-protocol-proof-verification/116123 "2026-03-22T08:11:43Z")

</div>

snip: 36 title: In protocol S-Two verification author: Ohad Barta description: Introduce capability of verifying S-Two proofs within Starknet discussions-to: https://community.starknet.io/t/snip-36-in-protocol-proo…

---

## [SNIP 37: revisit storage access cost](https://community.starknet.io/t/snip-37-revisit-storage-access-cost/116143)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 6\
**Last updated:** [March 19, 2026, 6:51pm UTC](https://community.starknet.io/t/snip-37-revisit-storage-access-cost/116143 "2026-03-19T18:51:28Z")

</div>

snip: 37 title: Revisit Storage access cost description: Increase the cost gap between computation and storage in starknet author: Ohad Barta (ohad@starkware.co) discussions-to: https://community.starknet.io/t/snip-…

---

## [SNIP 33 - proposal for Starknet decentralized validation](https://community.starknet.io/t/snip-33-proposal-for-starknet-decentralized-validation/115811)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 18\
**Last updated:** [February 17, 2026, 4:44pm UTC](https://community.starknet.io/t/snip-33-proposal-for-starknet-decentralized-validation/115811 "2026-02-17T16:44:06Z")

</div>

snip: 33 (temporary number) title: Starknet decentralized validation description: Discuss a concrete proposal for Starknet decentralized validation milestone author: Ohad Barta (@ob1337) status: Draft type: Standar…

---

## [SNIP: Access Control for Function Call Delegation](https://community.starknet.io/t/snip-access-control-for-function-call-delegation/114821)

<div class="topic-metadata">

**Author:** [@jbettenc](https://community.starknet.io/u/jbettenc)\
**Replies:** 6\
**Last updated:** [February 17, 2026, 3:02pm UTC](https://community.starknet.io/t/snip-access-control-for-function-call-delegation/114821 "2026-02-17T15:02:45Z")

</div>

title: Access Control for Function Call Delegation description: This SNIP aims to introduce access control standards to allow linking wallets together and performing actions on behalf of another wallet. author: Jordan …

---

## [\[SNIP\] Session Keys for Smart Accounts](https://community.starknet.io/t/snip-session-keys-for-smart-accounts/116132)

<div class="topic-metadata">

**Author:** [@haycarlitos](https://community.starknet.io/u/haycarlitos)\
**Replies:** 0\
**Last updated:** [February 17, 2026, 3:02pm UTC](https://community.starknet.io/t/snip-session-keys-for-smart-accounts/116132 "2026-02-17T15:02:37Z")

</div>

Summary We’re proposing a standard interface for session keys on Starknet smart accounts. Time limits, call limits, selector restrictions, paymaster compatibility. Session keys let users delegate limited authority to a …

---

## [\[SNIP\] Session Keys for Smart Accounts](https://community.starknet.io/t/snip-session-keys-for-smart-accounts/116131)

<div class="topic-metadata">

**Author:** [@haycarlitos](https://community.starknet.io/u/haycarlitos)\
**Replies:** 0\
**Last updated:** [February 17, 2026, 2:51pm UTC](https://community.starknet.io/t/snip-session-keys-for-smart-accounts/116131 "2026-02-17T14:51:14Z")

</div>

Summary We’re proposing a standard interface for session keys on Starknet smart accounts. Time limits, call limits, selector restrictions, paymaster compatibility. Session keys let users delegate limited authority to a …

---

## [\[SNIP\] Starknet Standard Account](https://community.starknet.io/t/snip-starknet-standard-account/95665)

<div class="topic-metadata">

**Author:** [@ericnordelo](https://community.starknet.io/u/ericnordelo)\
**Replies:** 6\
**Last updated:** [February 15, 2026, 1:21pm UTC](https://community.starknet.io/t/snip-starknet-standard-account/95665 "2026-02-15T13:21:41Z")

</div>

With native Account Abstraction, Starknet has a lot of flexibility in the management of accounts rather than having their behavior determined at the protocol level. The potential for innovation is virtually limitless lev…

---

## [Unable to withdraw legacy STRK stake from deprecated Voyager staking contract](https://community.starknet.io/t/unable-to-withdraw-legacy-strk-stake-from-deprecated-voyager-staking-contract/116069)

<div class="topic-metadata">

**Author:** [@Vad](https://community.starknet.io/u/Vad)\
**Replies:** 0\
**Last updated:** [November 17, 2025, 6:12am UTC](https://community.starknet.io/t/unable-to-withdraw-legacy-strk-stake-from-deprecated-voyager-staking-contract/116069 "2025-11-17T06:12:10Z")

</div>

Hello Starknet team, I need help with an old STRK staking position that is now stuck in a deprecated legacy staking pool (Voyager staking). Back in early 2024 I staked 708.7625 STRK from my Braavos wallet using the old…

---

## [SNIP-43 Unified Bech32m Addresses and Viewing Keys for Starknet](https://community.starknet.io/t/snip-43-unified-bech32m-addresses-and-viewing-keys-for-starknet/116001)

<div class="topic-metadata">

**Author:** [@abdel.1559](https://community.starknet.io/u/abdel.1559)\
**Replies:** 1\
**Last updated:** [October 21, 2025, 1:54am UTC](https://community.starknet.io/t/snip-43-unified-bech32m-addresses-and-viewing-keys-for-starknet/116001 "2025-10-21T01:54:19Z")

</div>

SNIP LINK Abstract This SNIP defines Unified Addresses (UA) for Starknet using Bech32m with HRPs: strk — public address receiver (legacy‑compatible, checksummed) strkx — shielded receiver (opaque, versioned) st…

---

## [SNIP 42: Bech32m Address Encoding for Starknet](https://community.starknet.io/t/snip-42-bech32m-address-encoding-for-starknet/116000)

<div class="topic-metadata">

**Author:** [@abdel.1559](https://community.starknet.io/u/abdel.1559)\
**Replies:** 2\
**Last updated:** [October 14, 2025, 9:22am UTC](https://community.starknet.io/t/snip-42-bech32m-address-encoding-for-starknet/116000 "2025-10-14T09:22:09Z")

</div>

Abstract This SNIP specifies a Bech32m address format for Starknet with human‑readable part (HRP) prefixes and typed payloads. It adds checksums and clear network/type scoping for addresses, and defines two initial HRPs: …

---

## [Bitcoin Staking on Starknet](https://community.starknet.io/t/bitcoin-staking-on-starknet/115696)

<div class="topic-metadata">

**Author:** [@NatanSW](https://community.starknet.io/u/NatanSW)\
**Replies:** 12\
**Last updated:** [October 8, 2025, 12:35am UTC](https://community.starknet.io/t/bitcoin-staking-on-starknet/115696 "2025-10-08T00:35:15Z")

</div>

Bitcoin Staking on Starknet snip: 31 Title: Bitcoin Staking on Starknet Author: @NatanSW Status: Draft Type: Standards Track Creation date: June 25rd, 2025 Github link: Add SNIP 31: BTC staking by natan-granit · Pu…

---

## [SNIP 34 - more efficient CASM hashes](https://community.starknet.io/t/snip-34-more-efficient-casm-hashes/115979)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 0\
**Last updated:** [September 30, 2025, 11:23am UTC](https://community.starknet.io/t/snip-34-more-efficient-casm-hashes/115979 "2025-09-30T11:23:06Z")

</div>

Simple Summary With the introduction of S-Two (expected to hit mainnet in mid-October 2025), many calculations embedded in Starknet’s infrastructure that were optimized initially for Stone can be re-optimized. The most …

---

## [SNIP 30: v0.14.0](https://community.starknet.io/t/snip-30-v0-14-0/115756)

<div class="topic-metadata">

**Author:** [@Leo\_L](https://community.starknet.io/u/Leo_L)\
**Replies:** 0\
**Last updated:** [July 10, 2025, 4:36pm UTC](https://community.starknet.io/t/snip-30-v0-14-0/115756 "2025-07-10T16:36:23Z")

</div>

Github link: SNIPs/SNIPS/snip-30.md at main · starknet-io/SNIPs · GitHub snip: 30 title: Starknet v0.14.0 description: Proposed features for v0.14.0 author: Leonardo Lerer (leo@starkware.co) status: Draft type: Sta…

---

## [SNIP 13 - Index \`Transfer\` and \`Approval\` events in ERC20s](https://community.starknet.io/t/snip-13-index-transfer-and-approval-events-in-erc20s/114212)

<div class="topic-metadata">

**Author:** [@NatanSW](https://community.starknet.io/u/NatanSW)\
**Replies:** 6\
**Last updated:** [April 4, 2025, 6:35am UTC](https://community.starknet.io/t/snip-13-index-transfer-and-approval-events-in-erc20s/114212 "2025-04-04T06:35:07Z")

</div>

snip: 13 Title: Index Transfer and Approval events in ERC20s Author: @NatanSW Status: Draft Type: Standards Track Creation date: May 5, 2024 Github link: SNIPs/SNIPS/snip-13.md at main · starknet-io/SNIPs · GitHub …

---

## [SNIP 28: Staking V2 proposal](https://community.starknet.io/t/snip-28-staking-v2-proposal/115250)

<div class="topic-metadata">

**Author:** [@Ohad-StarkWare](https://community.starknet.io/u/Ohad-StarkWare)\
**Replies:** 27\
**Last updated:** [April 3, 2025, 6:12am UTC](https://community.starknet.io/t/snip-28-staking-v2-proposal/115250 "2025-04-03T06:12:57Z")

</div>

snip: 28 (temporary number) Title: Staking v2 proposal Author: @NatanSW and @ob1337 Status: Draft Type: Standards Track Creation date: \*\* Github link: Abstract By the end of 2025, significant progress on the dece…

---

## [SNIP-X: Applicative Paymaster API Standard](https://community.starknet.io/t/snip-x-applicative-paymaster-api-standard/115308)

<div class="topic-metadata">

**Author:** [@Leo\_L](https://community.starknet.io/u/Leo_L)\
**Replies:** 1\
**Last updated:** [March 28, 2025, 12:05am UTC](https://community.starknet.io/t/snip-x-applicative-paymaster-api-standard/115308 "2025-03-28T00:05:06Z")

</div>

Here below is a SNIP proposal around standardizing the API between users and paymaster services. This proposal also affects SNIP-9 (outside execution): changes to SNIP-9 will be proposed and linked here as well when avai…

---

## [SNIP 23: Mixed-case checksum address encoding](https://community.starknet.io/t/snip-23-mixed-case-checksum-address-encoding/114949)

<div class="topic-metadata">

**Author:** [@ClementWalter](https://community.starknet.io/u/ClementWalter)\
**Replies:** 15\
**Last updated:** [January 8, 2025, 1:08am UTC](https://community.starknet.io/t/snip-23-mixed-case-checksum-address-encoding/114949 "2025-01-08T01:08:59Z")

</div>

I’m proposing to enforce the address representation to be 32 bytes long, checksumed as in the Ethereum ecosystem. The checksum mechanism can be the same. See also ERCs/ERCS/erc-55.md at master · ethereum/ERCs · GitHub …

---

## [SNIP 18: Staking’s First Stage on Starknet](https://community.starknet.io/t/snip-18-staking-s-first-stage-on-starknet/114334)

<div class="topic-metadata">

**Author:** [@NatanSW](https://community.starknet.io/u/NatanSW)\
**Replies:** 96\
**Last updated:** [December 19, 2024, 7:12am UTC](https://community.starknet.io/t/snip-18-staking-s-first-stage-on-starknet/114334 "2024-12-19T07:12:07Z")

</div>

snip: 18 title: Staking’s First Stage on Starknet author: Natan Granit natan@starkware.co status: Draft type: Standards Track category: Core created: July 10, 2024 Github link Staking’s First Stage on Starknet Ab…

---

## [SNIP-16: Deprecation of Transaction Versions 0,1,2](https://community.starknet.io/t/snip-16-deprecation-of-transaction-versions-0-1-2/114443)

<div class="topic-metadata">

**Author:** [@ilia](https://community.starknet.io/u/ilia)\
**Replies:** 7\
**Last updated:** [November 24, 2024, 12:24pm UTC](https://community.starknet.io/t/snip-16-deprecation-of-transaction-versions-0-1-2/114443 "2024-11-24T12:24:44Z")

</div>

snip: 16 title: SNIP-16: Deprecation of Transaction Versions 0,1,2 author: Ilia Volokh iliav@starkware.co status: Review type: Standards Track category: Core created: 2024/07/02 Github link Simple Summary In the …

---

## [SNIP14: Non-fungible Tokenbound Accounts](https://community.starknet.io/t/snip14-non-fungible-tokenbound-accounts/112479)

<div class="topic-metadata">

**Author:** [@Darlington02](https://community.starknet.io/u/Darlington02)\
**Replies:** 4\
**Last updated:** [November 24, 2024, 10:17am UTC](https://community.starknet.io/t/snip14-non-fungible-tokenbound-accounts/112479 "2024-11-24T10:17:57Z")

</div>

Simple Summary An interface and registry for smart contract accounts owned by non-fungible tokens Abstract This proposal defines a system that assigns Starknet accounts to all non-fungible tokens (ERC-721). These tokenb…

---

## [SNIP numbering policy and draft SNIPs](https://community.starknet.io/t/snip-numbering-policy-and-draft-snips/115023)

<div class="topic-metadata">

**Author:** [@Leo\_L](https://community.starknet.io/u/Leo_L)\
**Replies:** 2\
**Last updated:** [November 24, 2024, 8:22am UTC](https://community.starknet.io/t/snip-numbering-policy-and-draft-snips/115023 "2024-11-24T08:22:22Z")

</div>

Intro The current policy for numbering SNIPs has been, with rare exceptions, as follows: the final number of a SNIP is the smallest available (= not taken) number at the time of merging the associated PR. Moreover, ther…

---

## [SNIP-19: get\_class\_hash\_at syscall](https://community.starknet.io/t/snip-19-get-class-hash-at-syscall/114325)

<div class="topic-metadata">

**Author:** [@eiki](https://community.starknet.io/u/eiki)\
**Replies:** 5\
**Last updated:** [October 12, 2024, 1:16am UTC](https://community.starknet.io/t/snip-19-get-class-hash-at-syscall/114325 "2024-10-12T01:16:25Z")

</div>

Taking here the conversation about a new syscall for getting the class hash of a deployed contract, from within a contract execution environment. Simple Summary Introduce a new syscall get\_class\_hash\_at, aimed to get a …

[Next page](https://community.starknet.io/c/development-proposals/snip/7.md?page=1)
