Horizon (or RPC) transaction submission service

[greatest0fallt1me]

Description

Service to build/sign/submit transactions where backend holds signing key OR passes XDR to signer — document trust model.

Requirements and context

• Keys in KMS or env only for dev.
• Never log seed phrases.

Suggested execution

• Fork the repository and create a branch (example below).
• Implement changes in StreamPay-Backend (TypeScript / Express per package.json).
• Keep the service secure, tested, and documented; prefer small, reviewable PRs.

git checkout -b feature/tx-submission-service

Implementation targets

• src/services/transactionService.ts.
• Config for signer mode.

Tests and validation

• Tests: mock Stellar network; failure paths.

• Run npm test and npm run lint in StreamPay-Backend.

• Cover edge cases; include test output and brief security notes in the PR description.

Guidelines

• Target minimum 95% test coverage on new or changed backend code (or justify gaps).
• Clear documentation (OpenAPI / README / inline docs as specified).
• Timeframe: 96 hours from assignment.

Example commit message

feat(backend): transaction submission abstraction

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Oluwaseyi89]

@Oluwaseyi89 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi! I'd like to implement a transaction submission service that builds, signs, and submits Stellar transactions, with a clear trust model supporting both backend signing (via KMS or env for dev) and XDR generation for external signing, ensuring seed phrases are never logged and keys are properly secured. The service will include configurable signer modes, comprehensive error handling, and tests achieving 95%+ coverage with mocked Stellar network interactions, covering success paths, network failures, and security-sensitive edge cases.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwaseyi89 to this issue.

[drips-wave]

Congratulations, @Oluwaseyi89! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Oluwaseyi89: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Oluwaseyi89 as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] PR #73 directly implements the transaction submission service described in Issue #18, including support for different signer modes and security features like seed redaction. The PR was successfully merged and the corresponding issue closed by the maintainers.

😎 @Oluwaseyi89: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.