feat: add SwapFlowInitialized event #443
Open
Conversation
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
- Add ArbitraryActionsExecuted entity and database migration - Implement event decoding and indexing in CCTPIndexerDataHandler - Add integration test for ArbitraryActionsExecuted event processing - Configure ARBITRARY_EVM_FLOW_EXECUTOR_ADDRESS for HyperEVM mainnet - Update CI workflow with RPC provider URL for chain 999
- Add FallbackHyperEVMFlowCompleted entity with database migration - Implement event decoding and indexing in CCTPIndexerDataHandler - Add repository methods for saving fallback flow events - Include integration test for event processing
…d utility Move SimpleTransferFlowCompleted event processing logic from CctpRepository to a shared hyperEvmExecutor utility module. Add support for tracking these events in OFT indexer by fetching ComposeDelivered events and extracting SimpleTransferFlowCompleted events from transaction receipts. Update method signatures to use block
…leTransferCompleted-OFT
…leTransferCompleted-OFT
…leTransferCompleted-OFT
…backHyperEVMFlowCompleted
…as/track-SimpleTransferCompleted-OFT
…HyperEVMFlowCompleted tracking - Extract `getEventsFromTransactionReceipts` and `formatAndSaveEvents` into reusable generic utilities in `eventProcessing.ts` - Refactor `hyperEvmExecutor.ts` to export formatting functions instead of processing logic - Add `FallbackHyperEVMFlowCompleted` event tracking to OFT indexer alongside existing `SimpleTransferFlowCompleted` events - Replace duplicate event extraction methods in `CCTPIndexerDataHandler` with generic utilities - Update `EventDecoder` methods to use static references for consistency - Add integration test coverage for `FallbackHyperEVMFlowCompleted` event processing
…/track-FallbackHyperEVMFlowCompleted-Oft
…exer data handlers
…backHyperEVMFlowCompleted
…backHyperEVMFlowCompleted
…as/track-SimpleTransferCompleted-OFT
…/track-FallbackHyperEVMFlowCompleted-Oft
…ikolas/track-ArbitraryActionsExecuted-OFT
…/track-FallbackHyperEVMFlowCompleted-Oft
…ikolas/track-ArbitraryActionsExecuted-OFT
NikolasHaimerl
requested review from
amateima,
ashwinrava,
dohaki,
melisaguevara,
mrice32 and
nicholaspai
as code owners
NikolasHaimerl
changed the base branch from
nikolas/track-SponsoredAccountActivation
to
stage
- Upgrade @across-protocol/constants from 3.1.82 to 3.1.90 - Upgrade @across-protocol/contracts from 4.1.11 to 4.1.14 - Upgrade @across-protocol/sdk from 4.3.75 to 4.3.97 - Add support for CCTP and OFT deposit types in deposits API - Implement unified deposit querying with UNION ALL for multiple deposit types - Add deposit status lookup by transaction hash for all deposit types - Add Monad chain support with OFT configuration - Fix CCTP finalizer service and improve address formatting - Add comprehensive test coverage for new deposit types
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.
Adds SwapFlowInitialized events to the CCTP and OFTindexers.
This event has not yet appeared on the HyperEVM blockchain but according to this conversation, it is supposed to be emitted in the
receiveMessage/lzComposefunction, which means it is emitted alongsideMessageReceived/ComposeDeliveredevents.