Add `stellar tx send-via-core` command
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- rust
- Domain
- cli, networking
Research direction
Locate the implementation and tests for the existing stellar tx send command, then trace its transaction-input handling and network configuration. Compare that flow with stellar-core's /tx endpoint and verify the new command accepts argument, file, and stdin inputs, submits to the configured core URL, and prints the response.
Written by the indexing model from the issue text.
Description
What problem does your feature solve?
The existing stellar tx send command submits transactions exclusively through Soroban RPC's sendTransaction endpoint. There is no way to submit a transaction directly to stellar-core, or horizon.
Submitting directly to stellar-core is useful when:
- Ops work setting up new networks where an RPC isn't running but a classic tx needs sending.
- Debugging transaction submission issues where you want to isolate whether the problem is in RPC or core.
- Operating in environments where Soroban RPC is unavailable but stellar-core is accessible.
- Testing core directly during development or network upgrades.
What would you like to see?
A new stellar tx send-via-core subcommand that submits a transaction envelope directly to a stellar-core instance, bypassing Soroban RPC.
The command would follow the same pattern as stellar tx send:
stellar tx send-via-core [TX_XDR] --core-url <url>
- Accept a base-64 encoded transaction envelope XDR from a positional argument, file, or stdin (same as
stellar tx send). - Accept a
--core-urlflag (or resolve it from network configuration) pointing to a stellar-core HTTP endpoint. - Submit the transaction to stellar-core's
txHTTP endpoint. - Print the response from core.
What alternatives are there?
- Use
curlto manually POST the transaction XDR to a stellar-core instance's/txendpoint. - Submit via
stellar tx sendthrough RPC, which internally forwards to core anyway.
- Dominant language
- Rust
- Stars
- 123
- Forks
- 141
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stellar/stellar-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stellar/stellar-cli#2384 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stellar/stellar-cli#2347 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
stellar/stellar-cli#2723 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
stellar/stellar-cli#2722 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stellar/stellar-cli#2703 ·
All issues in stellar/stellar-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100