feat(snos): migrate to Starknet 0.14.2 with semantic parity#503
Draft
feat(snos): migrate to Starknet 0.14.2 with semantic parity#503
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This draft migrates SNOS to Starknet
0.14.2dependency/API surface with semantic parity for OS input assembly.Scope
initial_readsand computedblock_hash_commitments.rstest) around state-diff conversion and hashing-data assembly.Sequence Diagram
sequenceDiagram participant RPC as RPC State Source participant Exec as Tx Executor participant Build as Input Builder participant OS as Starknet OS RPC->>Exec: Load block context + txs Exec->>Exec: Execute txs in canonical order Exec->>Build: Execution outputs Exec->>Build: Initial reads snapshot RPC->>Build: State update Build->>Build: Convert to thin state diff Build->>Build: Compute block hash commitments Build->>OS: Assemble OsBlockInput (0.14.2)Flow Diagram
flowchart TD A[Block + Transactions] --> B[Execute Transactions] B --> C[Capture Initial Reads] B --> D[Collect Outputs For Hashing] A --> E[Fetch State Update] E --> F[Convert To ThinStateDiff] D --> G[Compute Block Header Commitments] F --> G C --> H[Assemble OsBlockInput] G --> H H --> I[Serialize Debug Output]Notes
Validation Status