feat: tron + layerzero prover support

[nknavkal]

No description provided.

[aromanoEco]

🔍 Claude Code Test Coverage Analysis

Spec Analysis: Tron + LayerZero Prover Support

Verdict

APPROVE WITH SUGGESTIONS

All core requirements have implementation coverage, but lack test coverage for configuration validation and integration verification.

---

Action Items

Tests that MUST be added before this PR can safely merge.

P0 — Required Before Merge

No P0 items. The changes are purely additive configuration without financial logic.

P1 — Recommended

Requirement	Missing Test	Why Recommended
Tron chain configuration is correctly exported	Unit test verifying tron export structure	Prevents configuration errors in consuming code
TronShasta testnet configuration is correctly exported	Unit test verifying tronShasta export structure	Prevents testnet integration failures
LayerZero EndpointV2 addresses are valid	Integration test validating contract addresses	Catches misconfigured addresses before production
USDT stable token configuration on Tron	Unit test verifying USDT address and decimals	Prevents token interaction errors
Chain registry includes new Tron chains	Test verifying EcoRoutesChains array includes both chains	Ensures chains are discoverable by routing logic

Details:

P1-1: Tron chain configuration validation

Requirement: "Tron mainnet must be correctly configured with LayerZero EndpointV2 and USDT stable token"

GIVEN: The tron chain configuration from definitions
WHEN: Accessing chain properties
THEN: 
  - chainId matches viem's tron.id
  - layerZeroEndpointV2.address is '0x0Af59750D5dB5460E5d89E268C474d5F7407c061'
  - USDT.address is '0xa614f803B6FD780986A42c78Ec9c7f77e6DeD13C'
  - USDT.decimals is 6
  - isCalderaChain is false

Risk if missing: Configuration errors could cause routing failures or incorrect token handling

P1-2: TronShasta testnet configuration validation

Requirement: "Tron Shasta testnet must be correctly configured with LayerZero EndpointV2"

GIVEN: The tronShasta chain configuration from definitions
WHEN: Accessing chain properties
THEN:
  - chainId matches viem's tronShasta.id
  - layerZeroEndpointV2.address is '0x1b356f3030CE0c1eF9D3e1E250Bf0BB11D81b2d1'
  - isCalderaChain is false

Risk if missing: Testnet integration could fail with misconfigured addresses

P1-3: Chain registry inclusion

Requirement: "Both Tron chains must be included in the EcoRoutesChains array for routing discovery"

GIVEN: The EcoRoutesChains array from index.ts
WHEN: Filtering for Tron chains
THEN:
  - Array includes a chain with tron's chainId
  - Array includes a chain with tronShasta's chainId
  - Both chains have layerZeroEndpointV2 contracts defined

Risk if missing: Chains won't be available for cross-chain routing operations

P1-4: LayerZero EndpointV2 consistency across chains

Requirement: "All EVM chains should have LayerZero EndpointV2 configured where applicable"

GIVEN: Chain configurations for arbitrum, base, ethereum, optimism, polygon
WHEN: Checking layerZeroEndpointV2 contract addresses
THEN:
  - All mainnet EVM chains have address '0x1a44076050125825900e736c501f859c50fE728c'
  - Tron mainnet has address '0x0Af59750D5dB5460E5d89E268C474d5F7407c061'
  - No undefined or null addresses

Risk if missing: Incorrect LayerZero endpoint could break cross-chain messaging

---

Coverage Status

Requirement	Status	Notes
Add Tron chain definition	Implemented	src/definitions/tron.ts
Add TronShasta testnet definition	Implemented	src/definitions/tron.ts
Export Tron chains from definitions	Implemented	src/definitions/index.ts
Include Tron chains in EcoRoutesChains	Implemented	src/index.ts
Configure LayerZero EndpointV2 on Tron	Implemented	Contract address added
Configure LayerZero EndpointV2 on existing chains	Implemented	Added to 5 chains
Configure USDT stable on Tron	Implemented	Address and decimals defined
Unit tests for chain configurations	Gap	P1 — recommended
Integration tests for LayerZero addresses	Gap	P1 — recommended
Registry inclusion tests	Gap	P1 — recommended

---

Context (Informational)

Spec Summary

• What's being implemented: Addition of Tron blockchain support and LayerZero V2 endpoint configuration across multiple chains
• Key requirements:
  • Add Tron mainnet and Shasta testnet chain definitions
  • Configure LayerZero EndpointV2 addresses for cross-chain messaging
  • Add USDT stable token configuration for Tron
  • Export chains through the registry for routing discovery
• Risk Level: LOW — Pure configuration changes without financial logic; addresses are read-only metadata

Files Changed

• src/definitions/tron.ts — New chain definitions for Tron mainnet and testnet
• src/definitions/arbitrum.ts — Added LayerZero EndpointV2 address
• src/definitions/base.ts — Added LayerZero EndpointV2 address
• src/definitions/ethereum.ts — Added LayerZero EndpointV2 address
• src/definitions/optimism.ts — Added LayerZero EndpointV2 address
• src/definitions/polygon.ts — Added LayerZero EndpointV2 address
• src/definitions/index.ts — Export Tron chain definitions
• src/index.ts — Add Tron chains to EcoRoutesChains array

Implementation Notes

Testing Recommendations:

1. Chain Configuration Tests — Verify each chain object has required properties:

   • Mock viem chain imports or use actual exports
   • Assert contract addresses are properly formatted
   • Verify stable token configurations

2. Integration Tests — If contract address validation is feasible:

   • Test that LayerZero endpoints are reachable (optional, may require network access)
   • Verify USDT contract exists at specified Tron address (optional)

3. Registry Tests — Verify chain discovery:

   • Assert all exported chains are in EcoRoutesChains
   • Filter chains by property (e.g., has layerZeroEndpointV2) and verify expected count
   • Test that chain IDs are unique

Mock Requirements:

• No complex mocking needed for configuration tests
• Use actual viem chain objects if available in test environment

Special Considerations:

• Tron uses different address format (base58 in documentation, but code shows hex)
• LayerZero V2 endpoint addresses are critical for cross-chain messaging
• No financial operations in this PR, only configuration metadata

---

Generated by QA Command Center • View Service

[dirkpage]

Looks good overall, the thing that we need to make sure of with tron (the first non-EVM chain added here) is that it's clearly typed or marked as a non-EVM chain and ideally doesn't break existing functions for users who are not expecting a non-EVM chain to be in the list without asking for it.

[linear-code]

ECO-793