feat(tap-aggregator): add v2 endpoint #316
Merged
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
This PR introduces the
aggregate_receipts_v2JSON-RPC endpoint, enabling collection-based receipt aggregation for the Horizon protocol. It maintains full backward compatibility with existing V1 endpoints while supporting a new V2 receipt structure.What’s New
✨ V2 Aggregation Endpoint
aggregate_receipts_v2collection_id(replacesallocation_id)payer,data_service,service_provider(new fields)v2feature flag (enabled by default)Architecture Improvements
ProtocolModeenum (LegacyvsHorizon)receipt_classifier.rscollection_id,payer,data_service,service_providerCompatibility & Migration
--no-default-featuresSigned off by Joseph Livesey [email protected]