Releases: AvaProtocol/EigenLayer-AVS
Releases · AvaProtocol/EigenLayer-AVS
Release v1.9.6
What's Changed
- Updated the output data of loop and fixed broken tests (#352)
- Fixed when decimals call returns error, valueRaw is null problem (#351)
- Created a no-op implementation of the sdklogging.Logger interface that safely handles all logger method calls without panicking
- Updated core/taskengine/vm.go
- Removed fallback logic of matching output data of previous nodes
- Removed BlockTimestamps from enriched data of Transfer event (#348)
- Updated EventTrigger to preserve type of contract ABI (#347)
- Updated task_id to id in Cancel and Delete Task (#346)
- Replaced simple boolean return of Cancel and Delete operations (#345)
- Used int64 for blockTimestamp in core/testutil/utils.go
Full Changelog: v1.9.5...v1.9.6
v1.9.5
1.9.5 (2025-06-25)
Bug Fixes
Documentation
What's Changed
- fix: added conditions to EventTrigger; renovated ContractRead and ContractWrite by @chrisli30 in #344
Full Changelog: v1.9.4...v1.9.5
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
1.9.0 (2025-06-09)
Feature
Bug Fixes
- runTrigger with transfer and use oneOf for transfer_log and evm_log (#310) (428cebc)
- Token metadata API whitelist loading and source tracking - Fix engine initialization to properly load token whitelist at startup - Add source field to TokenMetadata struct to track data origin - Update GetTokenMetadata to return nil for not-found tokens without RPC - Fix gRPC handler to use metadata.Source instead of guessing - Improve error handling for invalid addresses - Add comprehensive unit tests for TokenEnrichmentService - Add integration tests for engine GetTokenMetadata endpoint (f44acf6)
- add enhanced logging to RPC endpoint validation for better debugging (2d47177)
- use JSON-RPC POST request for RPC endpoint validation instead of GET (484f70d)
v1.8.3
v1.8.2
What's Changed
- Fixed ETHtransfer task trigger and re-organized list tasks by @chrisli30 in #297
- feat!: implement API message renaming and flexible field control by @chrisli30 in #298
- fix: implement API message renaming and flexible field control by @chrisli30 in #299
Full Changelog: v1.8.1...v1.8.2