`stellar-tx-pipeline` crate

Open
#2,632 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

Start by tracing tx::sim_sign_and_send_tx and its dependency on config::Args to understand the current transaction pipeline. Review how a Sign trait and optional keystore dependency could expose only selected steps for plugins. Done means a separate stellar-tx-pipeline crate exists without requiring the entire CLI and supports flexible plugin use.

Written by the indexing model from the issue text.

Description

What problem does your feature solve?

Plugins may want to take advantage of the transaction pipeline but today it is coupled the config::Args. Plugins have to import the entire cli in order in order to call tx::sim_sign_and_send_tx and have no way to use the transaction pipeline more flexibly, like to execute only a subset of the steps.

What would you like to see?

a stellar-tx-pipeline crate that is a minimal version of the transaction pipeline that can be used behind a Sign trait, with the keystore as a separate optional dependency.

What alternatives are there?

Reimplement parts of the transaction pipeline in every plugin or import the entire CLI.

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.