-
Notifications
You must be signed in to change notification settings - Fork 734
Implement byron vote creation and submission #804
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
Conversation
68196de
to
fffdb16
Compare
fffdb16
to
e9e70a9
Compare
I will update how the bryon commands are grouped and structured in a follow up PR so that QA and DevOps can begin to try out creation/submission of update proposals and votes. |
@@ -333,7 +335,9 @@ You can also check your proposal's validity using the [`validate-cbor`](#validat | |||
|
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.
Just a suggestion:
If we are giving examples for creating and submitting proposal vote then maybe we can also add similar examples for update proposals with mandatory arguments:
cardano-cli -- byron create-byron-update-proposal --config configuration/defaults/liveview/config-0.yaml --signing-key configuration/defaults/liveview/genesis/delegate-keys.000.key --protocol-version-major 1 --protocol-version-minor 0 --protocol-version-alt 0 --application-name app --software-version-num 1 --system-tag linux --installer-hash da39a3ee5e6b4b0d3255bfef95601890afd80701 --filepath ProtocolUpdateProposalFile
and
cardano-cli -- byron submit-byron-update-proposal --config configuration/defaults/liveview/config-0.yaml --filepath ProtocolUpdateProposalFile --socket-path socket/node-0-socket
with example output that user should expect
Update proposal TxId: upid:b982f442
e9e70a9
to
00203cd
Compare
bors merge |
Build succeeded |
Issue
Implement byron update proposal vote creation and submission #803
This PR does not result in breaking changes to upstream dependencies.
Checklist
This PR contains all the work required to resolve the linked issue.
The work contained has sufficient documentation to describe what it does and how to do it.
I have committed clear and descriptive commits. Be considerate as somebody else will have to read these.
I have added the appropriate labels to this PR.