fix: address #918, #919, #920, #921 - #953
Merged
Merged
Conversation
|
@james2177 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fix: address #918, #919, #920, #921
What was solved
#918 — Implement custody account management helpers
Implement custody account management helpers in the Stellar SDK codebase, providing core helper functionality for managing custody accounts, with proper event handling and comprehensive tests. The issue is broad and lacks specific API details, so the contribution should introduce a focused, well-typed helper module (plus tests) that fits existing patterns in src/accounts/ and src/account/, exposing custody account operations such as creation, signer/weight management, and state queries, while emitting events consistent with the repo's existing event-handling conventions.
Addressed:
#919 — Add SDK fee estimation with historical analysis
Implement SDK fee estimation with historical analysis: add a fee estimation module that computes fee estimates from current network conditions and historical fee data, expose it through the SDK surface, and cover it with tests. The issue is broad and generic, so scope is limited to a focused fee-estimation utility plus tests, without touching unrelated modules.
Addressed:
#920 — Implement payment pathway optimization
The issue asks to implement a generic 'payment pathway optimization' feature with core functionality, event handling, and comprehensive tests, but provides no concrete specification of what optimization means, which payment pathways are involved, or what events should be emitted. The repository is a Stellar SDK-style TypeScript library with existing modules like ammCalculator, broadcaster, builder/OperationBuilder, and adapters. Without a defined API surface, algorithm, or integration point, any implementation would be speculative and risk inventing scope beyond the issue text.
Addressed:
#921 — Add SDK audit trail logging for compliance
Implement SDK audit trail logging for compliance by adding a dedicated audit trail logger module that records SDK operations as structured, tamper-evident audit events, with event handling hooks and comprehensive unit tests.
Addressed:
Changes
src/accounts/AccountSignerWeightCalculator.ts(modify)src/accounts/AccountMergeDetector.ts(modify)src/broadcaster.ts(modify)src/auditLogger.ts(modify)src/audit/AuditTrailHasher.ts(modify)Approach
Issues
Closes #918
Closes #919
Closes #920
Closes #921