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.

Sign up for GitHub

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

Jump to bottom

Dealing with mesh reorgs #78

Open
lrettig opened this issue Apr 6, 2020 · 2 comments
Open

Dealing with mesh reorgs #78

lrettig opened this issue Apr 6, 2020 · 2 comments

Comments

@lrettig
Copy link
Member

lrettig commented Apr 6, 2020

It's not an issue on a per-node basis but how do we handle this at the top level in the explorer (#68) and dashboard (#64)?
@avive
Copy link
Contributor

avive commented May 25, 2020

I think this is addressed with our proposed layer-based stream - after reorg, updated layers will be streamed to clients. Can I close?

@lrettig
Copy link
Member Author

lrettig commented May 25, 2020

Are there any UIUX implications for the user? Is a reorg really 100% transparent to the user, or does a user (of the dashboard or explorer) need to know when a reorg has happened? Are there issues around tx finality - e.g., where finality might be delayed because of a fork or reorg?

What about, e.g., after a network upgrade hard fork? This is probably when a fork/reorg is most likely to occur.

Just trying to think through all of the possibilities...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@avive @lrettig