Implement bulk account operations with partial-failure recovery

[Just-Bamford]

Description

Problem

Applications managing large numbers of Stellar accounts currently need to execute account operations individually. This increases network overhead and makes error handling difficult when only part of a batch succeeds.

There is no unified batch execution model for trustline creation, payments, or account key rotation.

Solution

Implement batch account operation utilities with bounded concurrency, operation grouping, progress tracking, and partial-failure handling.

The batch executor should distinguish successful, failed, skipped, and retried operations. A failure in one account should not automatically invalidate unrelated operations.

Acceptance Criteria

• bulkCreateTrustlines(accounts, assets) is implemented.
• bulkSendPayments(transactions) is implemented.
• bulkRotateKeys(accounts, newKeys) is implemented where supported by existing account APIs.
• Batch size and concurrency limits are configurable.
• Individual operation results are tracked independently.
• Partial failures do not discard successful operations.
• Retryable failures can be retried without duplicating completed operations.
• Batch execution exposes progress information.
• Tests cover successful batches, partial failures, retries, and concurrency limits.
• Performance is benchmarked against sequential execution.
• Exported through src/account/index.ts and src/index.ts.

Note for Contributors

The implementation must be idempotency-aware. Never blindly retry an operation that may already have been submitted successfully.

[ogaziedaniel80-droid]

@ogaziedaniel80-droid has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[Purity-Euphemia]

@Purity-Euphemia has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Please I can work on this 🙏😭Thank you

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

[connelevalsam]

@connelevalsam has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I will like to work on this issue

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

[drips-wave]

Congratulations, @connelevalsam! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @connelevalsam: 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 🌊