Bridge Indexing: Multichain support L1<>L2 sync data #98
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
- Added BridgeL2 ABI definition for deposit and withdrawal events. - Introduced new GraphQL schema types for bridge deposits and withdrawals. - Implemented event handlers for DepositFinalized and WithdrawalInitiated in the bridge mapping. - Updated mainnet-complete.ts to include the new BridgeL2 datasource. - Exported bridge mapping functions in the index file.
- Changed startBlock to 65260492 for the L2Bridge deployment. - Updated L2Bridge address to 0x2c1B65dA72d5Cf19b41dE6eDcCFB7DD83d1B529E.
- Added support for Ethereum L1 and zkSync L2 in a new multi-chain project. - Created Docker configuration for PostgreSQL and services. - Implemented event handling for bridge deposits and withdrawals across both chains. - Introduced GraphQL schema for querying bridge activities. - Updated .gitignore to include new project files and directories. - Added README with setup instructions and project overview.
- Updated Docker Compose to ensure services are healthy before starting. - Introduced Jest configuration for unit testing with TypeScript support. - Added unit tests for bridge mapping handlers to validate deposit and withdrawal processes. - Implemented utility functions for zkSync RPC interactions with comprehensive test coverage. - Updated package dependencies to include Jest and TypeScript testing utilities.
- Removed redundant cache update functions for block numbers in the bridge mapping. - Simplified the retrieval of initiated withdrawals by querying the database directly. - Improved error handling for missing withdrawals during finalization. - Updated tests to reflect changes in withdrawal handling and added comments for clarity.
- Modified Docker Compose to ensure "subquery-node-zksync" service is healthy before starting. - Updated GraphQL schema to simplify bridge withdrawal and deposit fields, improving clarity and consistency. - Refactored bridge mapping functions to use unified sender and receiver fields for deposits and withdrawals. - Adjusted transaction handling to align with new schema definitions, ensuring accurate data mapping. - Enhanced unit tests to reflect schema changes and validate new mapping logic.
…nused options - Replaced all instances of 'docker-compose' with 'docker compose' for consistency with the latest Docker CLI. - Removed the '--allow-schema-migration' option from the Docker Compose configuration to streamline service startup.
… for improved reliability
- Removed the Event entity from the GraphQL schema to streamline data representation. - Updated BridgeWithdrawal, BridgeDeposit, and BridgeFailedDepositClaim entities to eliminate unnecessary fields. - Refactored bridge mapping functions to remove dependencies on the Transaction entity, enhancing clarity and performance. - Improved error handling and logging in the bridge mapping logic for better traceability.
…URL fallback - Introduced a new function to check for rate limit errors in RPC responses. - Refactored the RPC request logic to include automatic URL switching to a fallback URL upon detecting rate limit errors. - Updated the `rpcCall` and `rpcBatchCall` functions to utilize the new request handling logic, improving error resilience and reliability. - Enhanced logging for better traceability during retries and URL switches.
- Updated the GraphQL schema to make l1TransactionHash and status fields mandatory, and added finalizedAt for better tracking. - Refactored bridge mapping functions to improve error handling and streamline deposit creation and updates, ensuring clarity in deposit status management. - Simplified the logic for handling deposits and failed deposit claims, enhancing overall code readability and maintainability.
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.
No description provided.