Currently, governance on Starknet is addressing something far more tangible than regular updates. In two current proposals, STRK stakeholders are asked to make explicit decisions about how Bitcoin should be included in the network, not just in principle, but also in terms of its structure and application.

Everything is up for debate, from approving stakBTC's precise architecture and the signers behind its bridge to determining whether or not staking is permitted. Voting is only accessible until May 7, but these choices will have a significant impact on how Bitcoin functions within Starknet.

• SNIP-38: The Structural Blueprint of strkBTC
• From Design to Trust: What Approval Really Means
• SNIP-39: Extending strkBTC into the Staking Layer
• A Combined Decision Shaping Starknet’s Next Phase

SNIP-38: The Structural Blueprint of strkBTC

The first proposal, SNIP-38 (strkBTC—Bitcoin on Starknet), is only concerned with the structure and security of strkBTC. It establishes the precise architecture that governs how Bitcoin enters and exists within Starknet; it is not merely a symbolic idea.

The bridge mechanism and its designated signers are at the heart of this design. These signers are in charge of verifying Bitcoin deposits and making sure strkBTC is appropriately coined on Starknet. The proposal makes governance directly accountable for the trust model underlying the asset by specifically requesting STRK stakeholders to approve this signer set.

At this point, the structure starts to become precise. Because strkBTC is established by a controlled minting and verification process, the dependability of these signers determines the cryptocurrency's legitimacy. Stakers that approve SNIP-38 are validating the precise operational layer that supports strkBTC, not just allowing it to exist.

Additionally, the proposal designates strkBTC as the official Bitcoin representation for Starknet. It is intended to operate smoothly within Starknet's ecosystem while preserving parity with Bitcoin. This is clear; SNIP-38 decides whether or not this particular version of Bitcoin, with this particular configuration, joins the network.

SNIP38: strkBTC, Bitcoin on Starknethttps://t.co/cL4V4YLVbT

— StarkWare 🥷 (@StarkWareLtd) May 1, 2026

From Design to Trust: What Approval Really Means

The consequences of approving SNIP-38 follow logically once the structure is understood. The plan successfully incorporates a certain trust premise into Starknet's design.

STRK stakeholders define who protects Bitcoin as it enters the network by choosing and approving the bridge signers. This presents a multi-party responsibility paradigm in which the cooperation and honesty of these signers directly affect strkBTC's dependability.

This is a purposeful governance decision rather than a background technicality. Risk is not being subtly transferred or abstracted away by the network. Rather, it is giving its staking community complete control over that decision.

Consequently, the vote becomes more than just a technical support. It expresses how Starknet decides to strike a balance between the practicality of bridge-based verification and the availability of Bitcoin liquidity. This is a time-bound choice that determines whether this trust model is approved or rejected, and the May 7 deadline adds urgency.

NEWS: Two proposals are now live on Starknet governance.$STRK stakers can now vote on:
- Whether to approve the design of strkBTC and the signers behind the bridge
- Whether to make strkBTC eligible as a staking asset on Starknet

Both votes end on May 7.

— StarkWare 🥷 (@StarkWareLtd) May 1, 2026

SNIP-39: Extending strkBTC into the Staking Layer

SNIP-38's basis is directly expanded upon by SNIP-39 (strkBTC as a Stakable Token on Starknet), the second proposal. SNIP-39 establishes the extent of strkBTC's network integration, whereas the initial proposal establishes its existence.

It specifically queries whether strkBTC ought to be accepted as a staking asset. As a result, strkBTC becomes an active part of Starknet's security mechanism rather than merely a bridging image of Bitcoin.

StrkBTC would take part in staking alongside STRK if authorised. As a result, the network's economic structure takes on a new dimension in which the value gained from Bitcoin supports validator incentives and network security in general. Using strkBTC to strengthen the protocol is more important than simply storing or sending it.

The proposal's scope is very specific. It concentrates on strkBTC's eligibility and does not generalise staking adjustments. This keeps the conversation focused on a single question, i.e., Should Bitcoin liquidity directly contribute to Starknet security once it has been bridged?

SNIP39: strkBTC as a Stakable Token on Starknethttps://t.co/qks0RCnYOS

— StarkWare 🥷 (@StarkWareLtd) May 1, 2026

A Combined Decision Shaping Starknet’s Next Phase

Rather than being separate votes, SNIP-38 and SNIP-39 work together to provide a continuous decision flow.

SNIP-38 determines the existence of strkBTC under a particular signer and bridge design. Then, SNIP-39 decides if the same asset is integrated into the staking layer. Function is defined by one, and structure by the other.

If both ideas are approved, Starknet will get closer to a model in which Bitcoin is actively incorporated into its fundamental operations rather than merely being present. In order to balance external liquidity with internal incentives, strkBTC would move from being a bridged asset to a network security participant.

The decision for STRK stakers is simple but multi-layered. They are choosing who safeguards Bitcoin, how it enters Starknet, and whether or not it should contribute to network security in exchange. The results of both polls, which are scheduled to conclude on May 7, will have an instant impact on the degree to which Starknet incorporates Bitcoin into its design.

If you find any issues in this article or notice missing information, please feel free to reach out at team@etherworld.co for clarifications or updates.

To promote your Web3 articles, events, and projects, you may reach out anytime via EtherWorld PR for submissions and collaboration.

Related Articles

1. Starknet Targets April Launch for STRK20 Privacy Layer
2. Starknet is Making L2 Decentralization Cool Again
3. Starknet Can Now Make Secure App Development Smoother with Garaga SDK
4. Starknet and zkSync Thrive Amidst Crypto Developer Downturn
5. Privy Launches on Starknet

To follow blockchain news, track Ethereum protocol progress, and read our latest stories, subscribe to our weekly today.