• © Goverland Inc. 2026
  • Privacy Policy
  • Terms of Use
 Starknet Starknetby0xdBdF0A42Ee6809E4C4350F99539e91B91b4ae4b00xdBdF…e4b0

What features are you missing on SN?

Voting ended 4 months agoSucceeded

This question is about which technical upgrades or protocol changes would most improve Starknet (SN).

  • Reduce preconfirmations from 500ms to <300ms – Faster transaction confirmations, improving UX for users and dApps.
  • Improve L1 finality from 6 hours to under 3 hours – Shorter time for transactions to be considered irreversible on Ethereum, lowering risk and improving usability.
  • Reduce blocktime from 6 seconds to <2 seconds (on average) – Speeds up transaction inclusion and makes the network feel more responsive.
  • Reduce costs by 2x – Lowers fees, making Starknet more attractive for smaller users and frequent activity.
  • Add STRK burn mechanism – Introduces token burning, potentially creating deflationary pressure on STRK and aligning incentives.
  • Add timeboost-like mechanism – Allows users to pay more for prioritized transaction ordering, useful for arbitrage or time-sensitive trades.
  • Add in-protocol transaction scheduling service – Lets users or apps schedule transactions in advance directly at the protocol level.
  • Enable zkLogin through stateful validate – Further improving user onboarding.
  • Add transient storage – Provides temporary storage in transactions, reducing costs and complexity for developers.
  • Add support for post-quantum signature schemes (e.g., Falcon) – Further future-proofs Starknet security against quantum computing threats.

Off-Chain Vote

Reduce preconfirmations
12.92M STRK2.3%
Improve L1 finality
118.96M STRK20.8%
Reduce blocktime
38.01M STRK6.7%
Reduce costs by 2x
124.91K STRK0%
Add STRK burn mechanism
344.21M STRK60.3%
Add timeboost-like mechanism
43.07M STRK7.5%
Add transaction scheduling servi
70.63K STRK0%
Enable stateful validate
494.04K STRK0.1%
Add transient storage
83.08K STRK0%
Post-quantum signatures
12.65M STRK2.2%
Download mobile app to vote

Timeline

Sep 23, 2025Proposal created
Sep 23, 2025Proposal vote started
Sep 30, 2025Proposal vote ended
Sep 30, 2025Proposal updated