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

Tracking output state #140

Open
pgebal opened this issue Sep 28, 2020 · 1 comment
Open

Tracking output state #140

pgebal opened this issue Sep 28, 2020 · 1 comment
Labels
Childchain Related to the Childchain question Further information is requested

Comments

@pgebal
Copy link
Contributor

pgebal commented Sep 28, 2020

How precise do we want to be in tracking output state?
Currently output can be:

- "pending": the default state when creating an output
- "confirmed": the output is confirmed on the rootchain
- "exiting": the output is being exited
- "piggybacked": the output is a part of an IFE and has been piggybacked

If we want to be really precise why not mark output as challenged or exited?

I don't see benefits for tracking state in greater detail than, pending, confirmed or spent (general name for exited or used as an input for other transaction). What are those benefits?

@pgebal pgebal added question Further information is requested Childchain Related to the Childchain labels Sep 28, 2020
@pgebal
Copy link
Contributor Author

pgebal commented Dec 13, 2020

To sum up:

  1. Marking as challenged or exited introduces additional complexity and is not necessary, we spent output when standard exit is started or ife is piggybacked. We'll still get this info from watcher, which has to track state more precisely than childchain.
  2. When it comes to having outputs "exiting" and "piggybacked" I think that was a product requirement but I don't remember why/ @Pongch @mederic-p do you guys remember why?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Childchain Related to the Childchain question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant