Conversation
Greptile SummaryThis PR adds support for the Boba network (chain ID 288) across the request-network monorepo, deploying ERC20Proxy, ERC20FeeProxy, EthProxy, EthFeeProxy, BatchConversionPayments, and RequestDeployer contracts. The integration follows the exact same pattern as recently added networks (e.g., Confidence Score: 5/5This PR is safe to merge — it is a straightforward network integration with no logic changes, only additive configuration and contract address registrations. All changes follow the exact established pattern for previously added networks (e.g., sonic). The defensive try/catch in setupBatchConversionPayments.ts is a clean improvement that gracefully handles the known absence of conversion proxies on Boba. No existing behaviour is modified, only new entries are added across config and artifact files. No P0 or P1 issues found. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Boba Network\nchainId: 288] --> B[Currency Layer]
A --> C[Smart Contracts]
A --> D[Payment Detection]
A --> E[Utils / Providers]
B --> B1[boba.ts\nchainId = 288]
B --> B2[native.ts\nETH-boba]
B --> B3[currency-types.ts\nEvmChainName union]
C --> C1[RequestDeployer\n0xE99A...24B2]
C --> C2[ERC20Proxy\n0x5079...d72]
C --> C3[ERC20FeeProxy\n0x8881...BeE7]
C --> C4[EthereumProxy\n0xba25...dfBA]
C --> C5[EthereumFeeProxy\n0xe456...a6eF]
C --> C6[BatchConversionPayments\n0xD830...7C76\nno conversion proxies]
D --> D1[multichainExplorerApiProvider\nroutescan.io API]
E --> E1[providers.ts\nhttps://mainnet.boba.network]
Reviews (1): Last reviewed commit: "update all packages" | Re-trigger Greptile |
Description
Support for the boba network.
The following contracts were deployed:
All verified on https://bobascan.com/
Comments to reviewers:
Contracts' addresses are different from the previous deployment due to a different compiler configuration.
Also mocked the
getLogscalls in integration tests. They were hitting pubic RPC causing flakiness.