Skip to content
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.

Single-step commit #3

Open
GeorgeFlerovsky opened this issue May 28, 2024 · 0 comments
Open

Single-step commit #3

GeorgeFlerovsky opened this issue May 28, 2024 · 0 comments

Comments

@GeorgeFlerovsky
Copy link
Owner

GeorgeFlerovsky commented May 28, 2024

Instead of absorbing pending commits into head state, what if we simply mark the commit utxos with the head ID in the datum?

L2 must recognize such commits on L2 ledger as soon as these are detected on L1 under the native script address. No assurance tx needed because commits are considered part of the head as soon as they are held by the native script.

Problem: how to ensure that these commits don't get stuck in the native script when L2 consensus unexpectedly breaks down?

Replace assurance tx with an assurance certificate (i.e. similar to dissolution cert tree)? If so, then new commits can be recognized on L2 ledger as soon as a multi-signed snapshot contains a trivial dissolution cert to release them.

Problem 2: What about snapshot signing atomicity?

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

No branches or pull requests

1 participant