Skip to content

feat: support --rpc-url for local/standalone network testing #49

Description

@wagmiiii

Description

Currently, cargo-budget-report relies heavily on public networks (testnet or futurenet). For teams running a local standalone Soroban RPC node (via Docker) to avoid network rate limits or to test custom network fee settings, the tool currently blocks them because the RPC URL cannot be overridden manually.

What "done" looks like

  • Add a --rpc-url <URL> argument to the cargo-budget-report CLI.
  • Add a --network-passphrase <PASSPHRASE> argument (required if --rpc-url is used).
  • If these flags are provided, bypass the testnet/futurenet defaults and simulate transactions against the provided local RPC endpoint.
  • Update the crate README.md with documentation for these flags.

Implementation guidelines

  • Create a branch: git checkout -b feat/cli-custom-rpc-url
  • Update the clap parser in cargo-budget-report/src/main.rs to accept the two new arguments.
  • Pipe the custom URL and passphrase into the simulation configuration (whether that's via the native HTTP client or subprocess, depending on the current merged state).
  • Add a unit test verifying that the CLI correctly parses the arguments and overrides the network selection.

PR guidelines

  • Get assigned before starting.
  • PR description must include: Closes #[this issue].

Contact & Support


📋 Before you start

Please read our Code Quality Standards in CONTRIBUTING.md. Before submitting a PR, ensure you run:

  • cargo fmt --all -- --check
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test --workspace

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programcomplexity: mediumWave: standard features or involved bug fixes (150 pts)enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions