Skip to content

feat: add Tempo testnet support#38

Draft
mejango wants to merge 1 commit intomainfrom
add-tempo-support
Draft

feat: add Tempo testnet support#38
mejango wants to merge 1 commit intomainfrom
add-tempo-support

Conversation

@mejango
Copy link

@mejango mejango commented Mar 3, 2026

Summary

  • Add Tempo to Sphinx testnets configuration
  • Add Tempo sucker deployer config in fee project setup (chain ID 42429)
  • Add security tests (REVTempoSecurity.t.sol — 7 tests)
  • Add Tempo testnet RPC endpoint to foundry.toml

Context

Tempo is an L1 blockchain where the native token is USD (not ETH). The revnet deployer needs to handle Tempo-specific sucker configuration:

  • On L1 (ETH), if tempoDeployer is available, add a 4th sucker config for Tempo
  • On Tempo (chain ID 42429), deploy a single sucker back to ETH
  • Token mappings use NATIVE_TOKEN <-> NATIVE_TOKEN for now (TODO: update to WETH when deployed on Tempo)

Key findings

  • Auto-issuance entries are filtered by block.chainid at deploy time (REVDeployer.sol:1209), not at read time
  • Non-CCIP suckers (e.g., Arbitrum) reject mixed NATIVE_TOKEN <-> ERC20 mappings — only CCIP supports this

Test plan

  • All 7 REVTempoSecurity tests pass
  • All 19 existing tests pass (no regressions)
  • Verify sucker deployer configuration works with Tempo testnet

🤖 Generated with Claude Code

- Add Tempo to Sphinx testnets configuration
- Add Tempo sucker deployer config in fee project setup
- Add Tempo chain ID handling for cross-chain sucker deployment
- Add Tempo security tests (REVTempoSecurity.t.sol)
- Add Tempo testnet RPC endpoint to foundry.toml

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant