SYS to HyperEVM
A direct Hyperlane lane from Syscoin to Hyperliquid’s EVM, so SYS has somewhere to be traded that is not zkSYS. It does not exist yet. This page is where it will live, and meanwhile it is an honest account of what is built and what is not.
Nothing is deployed. There is no warp route between Syscoin and Hyperliquid EVM Testnet, so there is nothing to move money along and no button here that would do it.
The work to change that is written down rather than planned: the runbook is docs/WARP-ROUTE.md in the repository, with npm run warp:discover, warp:verify and warp:watch beside it.
- Withdraw from zkSYSThe money masstart holds is on zkSYS, and this lane starts on Syscoin Tanenbaum. Getting there is the first half of the withdrawal that already exists — withdraw, wait for zkSYS to settle it, claim on Tanenbaum. Hours, and you pay the claim.
- One Hyperlane hopNative SYS into the collateral router on Syscoin, a message to domain 998, and the same amount appears as a synthetic on Hyperliquid EVM Testnet. This is the part that does not exist.
- Trade it thereWhich needs somebody to have put liquidity beside it. A synthetic with no pool is a token nobody can sell, and the lane working changes nothing about that.
Hyperliquid balances mostly live on HyperCore, not HyperEVM, so a fourth step moves it across there. That is Hyperliquid’s own transfer, not a bridge.
- Permission, possibly. Extending the warp route Syscoin already has is signed by whoever owns its routers. If that is not us, this is a conversation before it is a deployment.
npm run warp:discoverprints that address. - A validator set for Syscoin. Hyperlane’s own validators do not cover a chain that is not in its registry, and Syscoin is in it nowhere. Who runs them, how many, and what quorum is the bridge. Everything else is plumbing.
- A relayer that never stops. Funded on both chains, watched, restarted. When it stops, messages stop — which is very likely what the existing six-hour transit already is.
- Liquidity. Capital, not code, and nobody has offered any.
- The route itself.
hyperlane warp deploy, thennpm run warp:verify.
Syscoin’s own position is bridge security. A SYS lane secured by a multisig validator set is a weaker trust model than Syscoin’s own bridge design. That may be an acceptable trade — but it is a trade, and it should be made on purpose. None of this is audited.