-
Notifications
You must be signed in to change notification settings - Fork 20
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
Double-check the consistency of STF execution status #1223
Comments
❗ This issue is stale because it has been open for 60 days with no activity. |
🔐 This issue was closed because there has been no activity for 7 days since it became stale. |
Still relevant |
@coax1d is now working on implementing a generic parentchain event checker. integritee-network/worker#1272 In this PR, we will add a handling that is very similar to how we approach indirect calls. We will introduce a impl HandleParentchainEvent for ParentchainEvent {
fn handle(self, executor: &IndirectExecutor) -> Result {
match self {
ExtrinsicSuccess(event) => event.handle(executor)
ExtrinsicFailed(event) => event.handle(executor)
}
}
} This is where I would handle failures of parentchain callbacks, essentially and roll-back, unreserve, unlock some sidechain stuff. Note: some details are still being worked out on our end. |
Practically this is not a case for us, because our callback logic is limited to depositing an event (except requesting a VC). Once we remove indirect calls the only output reported back to parachain would be VC generation. I think there is nothing that needs to be solved now. |
Context
It's common that an STF execution will call both parentchain extrinsic and sgx-runtime extrinsic. Ideally we need to make sure the state is synchronised between these: what if one extrinsic succeeds while the other fails? Then we have an inconsistent state.
We seek the long-term solution for it.
✔️ Please set appropriate labels and assignees if applicable.
The text was updated successfully, but these errors were encountered: