False positive review — terraclassic-bridge.xyz (governance-approved Hyperlane bridge for Terra Classic)

[igorv43]

Hi Phantom team,

I'm the developer and operator of https://terraclassic-bridge.xyz. Phantom currently
blocks signing requests from this domain ("Request Blocked — This dApp could be
malicious"). I'm requesting a review — this is a false positive, and below is the
full evidence of legitimacy.

WHAT THE DAPP IS
A Hyperlane Warp Route bridge UI to transfer LUNC and USTC between Terra Classic,
Solana, BNB Chain and Ethereum. It is a fork of Hyperlane's official open-source
UI template, maintained in a public organization repository (README includes a
screenshot of the live deployment on this exact domain):

• Source code: https://github.com/terra-classic-hyperlane/UI
• Upstream template: https://github.com/hyperlane-xyz/hyperlane-warp-ui-template

PROOF 1 — APPROVED BY TERRA CLASSIC ON-CHAIN GOVERNANCE
The Hyperlane integration and this deployment were approved by the Terra Classic
network's governance (both proposals PASSED on-chain):

• Proposal #12200 — "Hyperlane Integration on Terra Classic — Multichain
  Connectivity with Ethereum, BSC, and Solana"
  https://validator.info/terra-classic/governance/12200
• Proposal #12222 — "Hyperlane Warp Routes - Solana Mainnet Deployment Funding
  (LUNC/USTC/CW20)"
  https://validator.info/terra-classic/governance/12222

PROOF 2 — LISTED IN THE OFFICIAL HYPERLANE REGISTRY
The warp routes this UI uses are published in the official hyperlane-xyz registry,
reviewed and MERGED by Hyperlane maintainers, who independently verified the
on-chain state (owners, ISMs, enrolled routers) before merging:

• Merged PR #1559: feat: add Terra Classic and Terra Classic Testnet (cosmos) + warp routes hyperlane-xyz/hyperlane-registry#1559
  (Terra Classic chain metadata + deployments)
• Merged PR #1687: feat: add Terra Classic LUNC and USTC warp routes hyperlane-xyz/hyperlane-registry#1687
  (LUNC and USTC warp routes)
• Registry entries:
  https://github.com/hyperlane-xyz/hyperlane-registry/tree/main/deployments/warp_routes/LUNC
  https://github.com/hyperlane-xyz/hyperlane-registry/tree/main/deployments/warp_routes/USTC

PROOF 3 — ON-CHAIN PROGRAMS THE DAPP CALLS ON SOLANA
All transactions interact only with Hyperlane deployments:

• Hyperlane Mailbox (official solanamainnet deployment):
  E588QtVUvresuXq2KoNEwAmoifCzYGpRBdHByN9KQMbi
• LUNC warp route program: Dd3ajD8WbEyx7z3HqPnDyvUgFqEBzvF1VePjYd1NGnbr
  (synthetic mint: 8dxTo5reLtvRDx3Q8WEP33Uj2C5u6372EygJdNbsLFKG)
• USTC warp route program: 7CUdBt1Qn2R2StE7MDPhQW2EhmnGg8zKK8oJXwAGEoyf
  (synthetic mint: GNUbsF5mrurtDzNc65HipN5Fyzzzqbj5UonLNhj9frjF)

SECURITY POSTURE
The dApp never asks for seed phrases, never requests token approvals beyond the
transfer being made, and only interacts with the Hyperlane programs listed above.
It charges a small, clearly disclosed flat service fee (a plain
SystemProgram.transfer appended to the same transaction), shown to the user in the
UI before signing.

I suspect the flag came from a name-similarity heuristic (project name + .xyz on a
recently registered domain). The domain does not appear in your public
phantom/blocklist repository, so it seems to be an internal/heuristic flag. Happy
to provide anything else — DNS/domain ownership proof, a video walkthrough, or a
test transaction.

Domain: terraclassic-bridge.xyz
GitHub: https://github.com/terra-classic-hyperlane/UI

Thank you!
Igor

[Th3Ya0vi]

Please follow our domain and transaction warnings guide, including the linked review form if you need further assistance. Thanks!