You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Get rid of syncing concept - it makes no sense completely in a stateless setup. Instead each request must be resolved to the currently latest block (queried from L1 or L2, according to the selected trust mode: #657). Then all processing and proof validation must happen respectful of this current block.
Using properly extracted Ethereum (#668) and Starknet (#669) clients, such implementation should be rather straightforward:
Lookup if there is a cached latest block that is still fresh enough (timeout).
If not: lookup latest block & state root according to the selected trust mode.
Make the updated block & state root available for state proofs validation.
The text was updated successfully, but these errors were encountered:
Get rid of
sync
ing concept - it makes no sense completely in a stateless setup. Instead each request must be resolved to the currentlylatest
block (queried from L1 or L2, according to the selected trust mode: #657). Then all processing and proof validation must happen respectful of this current block.Using properly extracted Ethereum (#668) and Starknet (#669) clients, such implementation should be rather straightforward:
The text was updated successfully, but these errors were encountered: