Add a `tx auth` command

Open
#1,493 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
blockchain, cli

Research direction

Start by reviewing the existing tx sign command and the auth-related work referenced in PR #1406 and issue #1493. Clarify the scope of tx auth, including signing, dry-run behavior, and auth show output, then define acceptance checks for each proposed subcommand and its signed or unsigned results.

Written by the indexing model from the issue text.

Description

There are some functionalities related to auths that we were considering adding to different commands, but IMO it could get a bit clunky to find those subcommands or flags, instead adding a new command sounds like a more clear user story.
Currently, I can see 2 primarily functionalities that we wanted to add, related to auths:

  1. Signing auths (originally part of https://github.com/stellar/stellar-cli/pull/1406)
    While it makes sense to add a new flag (--auth-only) to sign, moving it to a new command makes more sense it we want tx sign to have the same flags as other transaction signing commands. Moreover, not all transactions may have auth entries inside (in fact, most will not).
    As such, we can add tx auth <xdr> --sign-with-* command that only sings auths.
  2. --dry-run for signing auths (https://github.com/stellar/stellar-cli/issues/1493) nicely follows in line with ^
  3. auth show <xdr> would be a great subcommand that lists all auths in this transaction, and shows which one is signed, which are not signed

cc @janewang @willemneal @leighmcculloch

Dominant language
Rust
Stars
123
Forks
141
Avg merge
2d 21h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.