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

WIP: Dzejkop/bump semaphore #770

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

WIP: Dzejkop/bump semaphore #770

wants to merge 9 commits into from

Conversation

Dzejkop
Copy link
Contributor

@Dzejkop Dzejkop commented Sep 18, 2024

Bumps semaphore to newest with oxide branch merged.

Also adds a small CLI tool to do local proof generation and verification

@Dzejkop Dzejkop self-assigned this Sep 18, 2024
@Dzejkop Dzejkop requested a review from a team as a code owner September 18, 2024 13:54
Comment on lines +16 to +45
struct Args {
#[clap(subcommand)]
subcommand: Command,

#[clap(
short,
long,
env,
default_value = "https://signup-orb-ethereum.crypto.worldcoin.dev"
)]
sequencer_url: String,

#[clap(long, env)]
basic_auth_username: Option<String>,

#[clap(long, env)]
basic_auth_password: Option<String>,

/// The path to the file that will be used to store the identity
#[clap(long, env)]
identity_file: Option<PathBuf>,

/// The path to the file that will be used to store the inclusion proof
#[clap(long, env)]
inclusion_proof_file: Option<PathBuf>,

/// The path to the file that will be used to store the semaphore proof
#[clap(long, env)]
semaphore_proof_file: Option<PathBuf>,
}
Copy link
Contributor

@0xKitsune 0xKitsune Sep 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks specific args are only used for certain commands. Consider using a similar approach to forge where each command has it's own set of args. The cli tool is pretty simple so this is not necessary, just a thought for consideration.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A lot of them are unique, but many are shared between commands. And putting them in the base command means that running ./tool --help displays helpful information, if I put them in each subcommand then a user needs to run ./tool --help followed by ./tool cmd --help for relevant information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants