60 update network connectors

[MatiasOS]

Summary

This PR introduces the network connectors architecture - a major refactoring that extracts blockchain data fetching logic into a modular adapter system with the new explorer-network-connectors package. This enables better maintainability, easier network additions, and cleaner separation of concerns.

Key Changes

Network Connectors Architecture

• New Package: explorer-network-connectors@0.0.2 - Modular network adapter system
• Adapters Implemented:
  • EVMAdapter - Generic EVM chains (Ethereum, Sepolia)
  • ArbitrumAdapter - Arbitrum-specific fields (l1BlockNumber, sendCount)
  • OptimismAdapter - OP Stack chains (Optimism)
  • BaseAdapter - Base L2
  • BNBAdapter - BSC and BSC Testnet
  • PolygonAdapter - Polygon PoS
• Factory Pattern: adaptersFactory.ts provides clean adapter instantiation
• Base Class: NetworkAdapter.ts - Abstract base with shared functionality

Code Removal (Replaced by network connectors)

• Deleted src/services/EVM/L1/ - L1 fetchers & adapters (648 lines)
• Deleted src/services/EVM/Arbitrum/ - Arbitrum fetchers & adapters (417 lines)
• Deleted src/services/EVM/Optimism/ - Optimism fetchers & adapters (419 lines)
• Deleted src/services/EVM/common/RPCClient.ts - Moved to explorer-network-connectors (346 lines)
• Deleted src/services/EVM/common/TraceService.ts - Moved to explorer-network-connectors (175 lines)
• Deleted src/services/RPCMetadataService.ts - Moved to explorer-network-connectors (65 lines)
• Deleted src/services/adapters/transaction.ts - Legacy adapter (50 lines)

Total Removed: ~2,120 lines of legacy fetcher/adapter code

🔧 Service Layer Updates

• DataService.ts: Simplified from ~1,500 to ~780 lines (-48%)
  • Removed network-specific fetcher instantiation logic
  • Integrated adapter factory pattern
  • Cleaner method implementations delegating to adapters
• useDataService.ts: Updated to initialize adapters via factory
• NetworkBlockIndicator.tsx: Now uses RpcClient from explorer-network-connectors

⚙️ Configuration

• biome.json: Disabled automatic import sorting (prevents conflicts with manual organization)
• tsconfig.json: Updated module resolution for new package structure

Architecture Benefits

Advantages:

• ✅ Single Responsibility: Each adapter handles one network type
• ✅ DRY Principle: Shared logic in NetworkAdapter base class
• ✅ Easy Extensions: Add new networks by creating new adapter
• ✅ Reusability: Connectors package can be used in other projects
• ✅ Type Safety: Consistent interfaces across all networks

Technical Details

Adapter Structure:
Each adapter extends NetworkAdapter and implements:

• getBlock(blockNumber) - Fetch block data
• getTransaction(txHash) - Fetch transaction with receipt
• getAddress(address) - Fetch address data, balance, code
• getNetworkStats() - Gas price, latest block, sync status

Network-Specific Customizations:

• Arbitrum: Adds l1BlockNumber, sendCount, requestId fields
• OP Stack (Optimism, Base): Adds L1 fee breakdown (l1Fee, l1GasPrice, l1GasUsed)
• Generic EVM: Standard Ethereum fields only

RPC Strategy Support:

• Both fallback and parallel RPC strategies work with new connectors
• Metadata generation and provider comparison maintained
• Inconsistency detection preserved

Breaking Changes

None - this is an internal refactoring that maintains full API compatibility.

File Statistics

• 59 files changed
• +2,892 insertions
• -2,958 deletions
• Net: -66 lines (code consolidation)

[github-actions]

🚀 Preview: https://pr-85--openscan.netlify.app
📝 Commit: 8e606843699e0df53bf7f41f9a8b16026c5d7a89

[AugustoL]

🍻