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.

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

UX: Return epoch where fund/release happened #431

Closed
adlrocha opened this issue Apr 25, 2023 · 1 comment
Closed

UX: Return epoch where fund/release happened #431

adlrocha opened this issue Apr 25, 2023 · 1 comment
Assignees
Labels

Comments

@adlrocha
Copy link
Contributor

Returning the epoch where a fund or a release happened can be really helpful to improve the UX of cross-net messages. That way users can have a sense of the next checkpoint in which their cross-net message will be included, so they can monitor the commitment of checkpoints and know when to expect their message to be committed. This can also help us debug a lot.

Additionally, this may become a requirement for the implementation of https://github.com/consensus-shipyard/ipc-agent/issues/151

@cryptoAtwill
Copy link
Contributor

See #191

@cryptoAtwill cryptoAtwill self-assigned this May 8, 2023
@adlrocha adlrocha closed this as completed May 8, 2023
@jsoares jsoares transferred this issue from consensus-shipyard/ipc-libs Dec 19, 2023
@jsoares jsoares added the s:ipc label Dec 19, 2023
@jsoares jsoares closed this as not planned Won't fix, can't repro, duplicate, stale Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants