-
Notifications
You must be signed in to change notification settings - Fork 37
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
[v0.2.0] Major CLI Refactor / Cleanup #127
Conversation
Usage: "Print the calldata for all associated transactions, but do not execute them. Note that some transactions have an order dependency (you cannot submit checkpoint proofs if you haven't started a checkpoint) so this may require you to get your pod into the correct state before usage.", | ||
Required: false, | ||
Destination: &simulateTransaction, | ||
} |
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.
this is now just the default state of the tool.
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.
if !args.NoPrompt && !args.SimulateTransaction { | ||
core.PanicIfNoConsent(core.StartCheckpointProofConsent()) | ||
} |
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.
Can we do the inverse of this boolean statement?
if args.NoPrompt || args.SimulateTransaction
The current version is making my head hurt :(
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.
dam this is what i get for coding past 11
/command
package--proof
and--output
-- we now just output calldata to stdout as JSON by default. If you want to save to a file, pipe the JSON output to a file, and later use a tool like foundry's cast to submit :)main.go
isn't a mess.Workflows:
--sender <privateKey>
.--sender
and instead just parse the JSON output from the command -- we provideto
andcalldata
, sign this with whatever tool you want and submit to network.--verbose
.--sender
, If you want to submit any of this in CI without user prompts, pass--no-prompt
.Hopefully this simplifies everyone's workflows!
Examples
credential proofs
checkpoint start