lazer/iota: Mainnet deploy

[matej-douro]

Summary

Rationale

How has this been tested?

• Current tests cover my changes
• Added new tests
• Manually tested the code

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api-reference	Ready	Preview, Comment	Jul 22, 2026 12:30pm
component-library	Ready	Preview, Comment	Jul 22, 2026 12:30pm
developer-hub	Ready	Preview, Comment	Jul 22, 2026 12:30pm

4 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
entropy-explorer	Skipped		Jul 22, 2026 12:30pm
insights	Skipped		Jul 22, 2026 12:30pm
proposals	Skipped		Jul 22, 2026 12:30pm
staking	Skipped		Jul 22, 2026 12:30pm

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔍 Second iota_mainnet wormhole entry does not collide with existing one

The PR adds a second iota_mainnet IotaWormholeContract entry (contract_manager/src/store/contracts/IotaWormholeContracts.json:17-21) alongside the existing one. The store keys contracts by getId() which combines chain and stateId (contract_manager/src/core/contracts/iota.ts:411-413), so the two entries have distinct IDs and won't trigger the Multiple contracts with id error in contract_manager/src/node/utils/store.ts:246-251. This mirrors the pre-existing pattern where iota_testnet already has two entries. No collision, but reviewers should confirm that consumers looking up a wormhole contract by chain (rather than by full id) handle multiple iota_mainnet entries as intended.

---

Was this helpful? React with 👍 or 👎 to provide feedback.