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
Updated numeric field types to strings for better precision and updated openapi schema
### What changed?
- Generated openapi for a new API endpoint `/{chainId}/transfers` for retrieving token transfers with various filtering options
- Added a new `TransferModel` definition to support the token transfers endpoint
- Changed several numeric field types from `integer` to `string` in API models to better handle large numbers:
- In `BlockModel`: `gas_limit` and `gas_used`
- In `TransactionModel`: `value`, `gas_price`, `max_fee_per_gas`, `max_priority_fee_per_gas`, `effective_gas_price`, and `blob_gas_price`
### How to test?
1. Make a GET request to the new endpoint `/{chainId}/transfers` with appropriate filters
2. Verify the response contains token transfer data in the expected format
3. Check that numeric values are properly returned as strings without precision loss
4. Test various filter combinations (token type, address, block range, etc.)
### Why make this change?
- The new transfers endpoint provides a dedicated way to query token transfer events, making it easier for clients to track token movements
- Converting numeric fields to strings prevents precision loss when dealing with large numbers (like gas prices and token values) that can exceed JavaScript's safe integer limits
GitHub Copilot: I'll help you create a pull request description for this change.
0 commit comments