soroban-cli
soroban-cli copied to clipboard
stellar
CLI for Soroban contracts.
### What version are you using? soroban --version soroban 20.0.0-rc4 (bce5e56ba16ba977200b022c91f3eaf6282f47eb) soroban-env 20.0.0-rc2 (8c63bff68a15d79aca3a705ee6916a68db57b7e6) soroban-env interface version 85899345977 stellar-xdr 20.0.0-rc1 (d5ce0c9e7aa83461773a6e81662067f35d39e4c1) xdr curr (9ac02641139e6717924fdad716f6e958d0168491) Rust soroban-sdk = { version =...
### Could not install Soroban with cargo version 1.74.1? error: failed to run custom build command for `prettyplease v0.2.15` Caused by: could not execute process `C:\Users\dy.cio\AppData\Local\Temp\cargo-installuDAHrA\release\build\prettyplease-d20c13f0a15424e5\build-script-build` (never executed) Caused by:...
We need to be able to invoke contracts in readonly mode, where we expect no affect to take place. We should add an option to the invoke command to allow...
It would be helpful at times if the CLI could output additional information about what it's doing and what it is sending and receiving to the network. This would be...
Would be great for consistency (and usefulness) to add `--output xdr-base64` to other commands with a `--output` flag, like `contract read`, `events`, (and eventually `invoke`?) _Originally posted by @paulbellamy in...
See: https://github.com/stellar/soroban-tools/actions/runs/5293392154/jobs/9581464840?pr=702#step:10:375 And: https://github.com/stellar/soroban-tools/pull/702
Relying on state expiration defaults for these commands is likely not the play. Being able to optionally request an install, deploy or restore bump would be a big win imo
### What version are you using? 0.9.1 ### What did you do? Any command that currently _consumes_ configs adds `locator::Args` to its `Cmd` struct. This means that `--global` shows up...
### What problem does your feature solve? Makes it clearer to the user what the options are when using the commands. ### What would you like to see? soroban contract...