-
Notifications
You must be signed in to change notification settings - Fork 56
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
Refactor challenger to be in main folder #689
Conversation
Similar to user inside test file or user as wallet, challenger/proposer apps are not core nightfall and are part of and only used for testing. So challenger/proposer app should go under Usually, developers of nightfall would build their own version of challenger/proposer app using nightfall SDK and use it with the core nightfall (nightfall-client/wallet, nightfall-optimist). |
Answering @ChaitanyaKonda, current proposer/challenger location makes it extremely difficult to guide an external party on how to build one proposer/challenger. I understand these are not core roles, but certainly cannot be left within a test subfolder. I am fine creating a new folder named apps or roles where we create these roles (proposer, challenger, liquitidy provider, synchronizer,....). I am open to suggestions |
I 200% agree with @druiz0992 , even if we don't consider proposer/challenger as core parties, a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Without a proposer you can't make blocks. So it's not the core but very important for the users to understand how to build a proposer and |
Change Challenger to an independent folder in the root of the solution. Expecting to release scripts to help external parties deploy their own version of challengers. Remove it from cli folder.
There is no change in functionality.