Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design of Starknet IBC light client protocol #202

Open
31 tasks
Farhad-Shabani opened this issue Jan 17, 2025 · 1 comment
Open
31 tasks

Design of Starknet IBC light client protocol #202

Farhad-Shabani opened this issue Jan 17, 2025 · 1 comment

Comments

@Farhad-Shabani
Copy link
Member

Farhad-Shabani commented Jan 17, 2025

Overview

This ticket aims to track the design of the Starknet light client protocol and draft its specifications in English (and potentially Quint). The first phase involves studying the Starknet architecture in depth and engaging with Starknet experts to address key design and implementation questions outlined below. Insights from this research will inform the design of an initial light client architecture, which will serve as the foundation for the final specification. It would be great if findings be documented as ADRs or concise markdown docs, providing valuable references for the later implementation phase.

Phases

  1. Research Starknet architecture
  2. Design protocol, and draft initial architecture
  3. Write specifications

Tasks List

1. Research

Research (L2 Security Model)

Preview Give feedback

Research (ZK Prover)

Preview Give feedback

Research (Membership Proofs)

Preview Give feedback

Research (Beerus light client)

Preview Give feedback

2. Protocol Design

Protocol (Properties and Core Logic)

Preview Give feedback

Protocol (Threat Modeling)

Preview Give feedback

Protocol (Compatibility)

Preview Give feedback

3. Specifications

Specs (English)

Preview Give feedback

Deliverables

  • Research documentation (markdown files)
  • Draft protocol architecture (ADRs)
  • Preliminary English specification
@mpoke mpoke changed the title Development of Starknet IBC light client protocol Design of Starknet IBC light client protocol Jan 17, 2025
@adizere
Copy link
Member

adizere commented Jan 17, 2025

nice overview! dropping here some opinions --

Should go with centralized or decentralized sequencer?

centralized

Does IBC need some kind of Ethereum light client?
How can we address long (~12h) confirmation times on L1?

finalization would be too long, so I would say no Eth client; verify Starknet L2 in first phase only, at least until sequencer becomes decentralized

Is sequencer signature verification sufficient?

I suspect we cannot verify execution, so in first phase we may need to work with this as sufficient safety condition

Research (Membership Proofs)
Research (ZK Prover)

(same as sig verification)

Research (Beerus light client)

very interesting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants