You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## tl;dr
- Defines structs for the off chain representation of Payer Reports
- Actually generates Payer Reports
- Alters the `unsettled_usage` table to keep track of the last known sequence ID for each originator/payer combo in a given minute. This makes it cheap to look up when generating a Payer Report
## Notes
### Minimum Report Size
- To generate a Payer Report you need a minimum of two messages, originated in two distinct minutes. This resolves#645
## Tickets
Implements part of #514
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit
- **New Features**
- Introduced new queries to aggregate spending data and retrieve envelope details, enhancing data reporting.
- Added a comprehensive mechanism for generating and verifying payer reports, improving overall reporting accuracy.
- Improved envelope creation by integrating timestamp support for more precise data handling.
- Added new queries for enhanced data retrieval capabilities, including payer reports and gateway envelope details.
- Introduced a new field for tracking last sequence IDs in unsettled usage records, enhancing data integrity.
- **Bug Fixes**
- Adjusted existing queries to return additional data fields, ensuring accurate reporting.
- **Tests**
- Expanded test coverage to validate various report generation scenarios, ensuring reliable performance.
- Added tests for handling out-of-order sequence IDs during database operations, improving robustness.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Each node in the system publishes a
PayerReport
to theRewards
, containing the messages originated in it.The text was updated successfully, but these errors were encountered: