StarkNet roundup #51

Weekly summary of all things StarkNet

This newsletter is made possible thanks to Braavos Wallet! With Braavos' new Hardware Signer capability, you can get the piece of mind of a Hardware Wallet while enjoying a frictionless smooth UX. Braavos Wallet on StarkNet is made for an intuitive and safe start in crypto. It is available on Android, iOS, Chrome and Firefox.

To see how it works, download the app now.

Following Braavos $10M fundraising announcement, we are recruiting in all departments, especially our tech team. If you are a strong developer with a keen interest in making crypto accessible to everyday users, apply now via: [email protected]

Welcome to the 51th edition of my weekly comprehensive StarkNet summary. The previous update can be found here. 👇🏻

Would you like to sponsor this newsletter? Reach out to me.

If you enjoy this newsletter, don’t forget to subscribe. It’s free!

Let’s get into this week’s news! 💪

Protocol & dev tool updates

Media highlights

Ecosystem Highlights

Ecosystem stats

StarkNet Community & Shamans Highlights

Starknet’s current architecture can be summarized as follows:

There is usually a latency of several hours between creation and propagation of a Starknet block on L2 by the sequencer, and the block’s L1 finalization (inclusion in an L1 state update).

While the sequencer and prover are operated by the same entity, users can trust the operator’s reputation that every Starknet block published on L2 will eventually be proven and updated on L1. In other words, users trust the operator not to fork. Assuming such trust, the latency between L2 propagation and L1 finality is significant only for L1/L2 operations e.g withdrawals.

An obvious step toward decentralization would involve replacing the single sequencer with a Sybil resistant consensus protocol. In such a scenario, we assume confidence in L2 consensus to be much smaller than confidence in L1 security, which is Starknet’s eventual security. Without trust, latency between L2 consensus and L1 finality is significant to user experience because it marks the latency of L1 security and L1/L2 interaction. This justifies a fast finality gadget which has a latency of several minutes at most and also inspires greater user confidence than the L2 consensus by itself.

Heavily discussed StarkNet Improvement Proposals

Useful links & articles

Developer resources

Dates and Events

You can check out all of the past updates here.

None of the content of this newsletter is financial advice. Always do your own research.

Thank you for reading, and see you next week. ⏳

Would you like to sponsor this newsletter? Reach out to me.

Reply

or to participate.