-
Notifications
You must be signed in to change notification settings - Fork 220
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
feat: constitution publishing #4150
feat: constitution publishing #4150
Conversation
4988306
to
a2b908d
Compare
a2b908d
to
8da58a0
Compare
I think it's worth changing all the old "committee definition" terminology for the newer "contract constitution" everywhere, to avoid name inconsistency. Otherwise, LGTM |
c2785d6
to
2f4b8aa
Compare
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.
Looks good.
applications/tari_console_wallet/src/grpc/wallet_grpc_server.rs
Outdated
Show resolved
Hide resolved
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.
I'm happy with it, but waiting for #4162 before merging
c2a4d82
to
6788a6e
Compare
Description
Update the committee proposals into constitution publishing.
Motivation and Context
Meet the new requirements for proposing a committee. Update old code to match new specifications. Refactor the existing functionality instead of introducing net new functionality.
It may have been a better choice to specify a json file as a constitution but I wanted to keep similar functionality to how it was being done. By the end of the PR this was obviously a less ideal choice. We accept 4 arguments to create the constitution at the moment. Where as there are more arguments that can be utilized.
How Has This Been Tested?
cargo run --bin tari_console_wallet -- -b . --command "publish-constitution-definition --json-file ../../integration_tests/fixtures/constitution_definition.json"