feat: add Monad (143), Cronos (25), HyperEVM (999) - #91
Merged
Conversation
- Add MONAD, CRONOS and HYPEREVM to NetworkEnum and SupportedChains - Add escrow factory v1.1 deployment (0x8e6c3c2e2631de0a1d4fd46a15f79a1373486fa4), src/dst implementations and TrueERC20 for the three chains. They share a new deployer, so the addresses are common to the trio but differ from other chains. All addresses verified on-chain via factory getters ESCROW_SRC_IMPLEMENTATION() and ESCROW_DST_IMPLEMENTATION() Co-authored-by: Kirill <krboktv@gmail.com>
…dk to 5.4.2-rc.0 Carries Monad/Cronos/HyperEVM support from the dependency SDKs: - NetworkEnum entries and CHAIN_TO_WRAPPER wrapped-native map (WMON 0x3bd359c1119da7da1d913d1c4d2b7c461115433a, WCRO 0x5c7f8a570d578ed84e63fdfa7b1ee72deae1ae23, WHYPE 0x5555555555555555555555555555555555555555) - HyperEVM-specific LOP v4 verifying contract 0x5281602adc446a94eb48d055f514a6d8d5bee176 (the canonical router has no code on chain 999), returned by getLimitOrderContract(999) pnpm resolves a single limit-order-sdk 5.4.2-rc.0 instance for both the root and fusion-sdk Co-authored-by: Kirill <krboktv@gmail.com>
…or new chains - getTypedData uses the HyperEVM-specific LOP deployment as EIP-712 verifyingContract for chain 999, and the canonical router for Monad, Cronos and Ethereum - EvmCrossChainOrder.fromNative resolves the correct wrapped native token (WMON/WCRO/WHYPE) for each new chain Co-authored-by: Kirill <krboktv@gmail.com>
brace-expansion (GHSA-3jxr-9vmj-r5cp, GHSA-mh99-v99m-4gvg, GHSA-rgw5-rvv9-x895), js-yaml (GHSA-52cp-r559-cp3m, GHSA-5p4m-2wfm-xmqj) and undici 8.x (GHSA-4cwx-7wf7-3272) are pinned to patched versions within their majors. pnpm audit --audit-level high is green again (failures pre-date this branch) Co-authored-by: Kirill <krboktv@gmail.com>
3 tasks
krboktv
marked this pull request as ready for review
August 15, 2026 17:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
MONAD = 143,CRONOS = 25,HYPEREVM = 999toNetworkEnumandSupportedChainsTRUE_ERC20,ESCROW_FACTORY,ESCROW_SRC_IMPLEMENTATION,ESCROW_DST_IMPLEMENTATION. The trio shares a new deployer, so the addresses are common to the three chains but differ from other chains:0x8e6c3c2e2631de0a1d4fd46a15f79a1373486fa40x25fb2e7a56db5a3f04be5e7a728977e889e62a3c, dst impl0x715bb4091abccacef523a6069b4f0e2678a352f2(read on-chain from the factory getters on all three chains)0x175a30f81eade2d75b4d1d5fc750131877355d21@1inch/fusion-sdk2.4.10 → 2.4.13-rc.1 and@1inch/limit-order-sdk5.3.1 → 5.4.2-rc.0 (carry the new-chainCHAIN_TO_WRAPPERentries — WMON0x3bd359c1119da7da1d913d1c4d2b7c461115433a, WCRO0x5c7f8a570d578ed84e63fdfa7b1ee72deae1ae23, WHYPE0x5555555555555555555555555555555555555555— and the HyperEVM-specific LOP v4)Mirrors #86 for the three chains, with the #90 post-merge fix patterns applied up front:
0x5281602adc446a94eb48d055f514a6d8d5bee176; the canonical0x111111125421ca6dc452d289314280a0f8842a65has no code on chain 999 (verified on-chain:eip712Domain()returns("1inch Aggregation Router", "6", 999, 0x5281602aDc446A94eb48D055f514A6d8D5bee176)).getTypedData/getOrderHashpick it up viagetLimitOrderContract(999)from limit-order-sdk 5.4.2-rc.0 — regression test added.EvmCrossChainOrder.fromNativeworks — regression tests added per chain.Also fixes pre-existing
pnpm audit --audit-level highfailures (brace-expansion, js-yaml, undici 8.x) via within-major overrides so the PR security gate is green — same approach as #87.Release
@1inch/cross-chain-sdk@2.2.2-rc.0is published to npm (dist-tagnext) from this branch via the release workflow. Suggested final release after merge: 2.3.0 (wideningSupportedChainsis a minor).On-chain verification (2026-08-15, via
https://api.1inch.com/web3/{chainId})0x1111…2A650x1111…2A650x5281…e176(canonical has no code)0x8e6c…6fa4ESCROW_SRC/DST_IMPLEMENTATION()0x25fb…2a3c/0x715b…52f20x175a…5d21Factory-version mapping cross-checked by bytecode size: the v1.1 factory (11325 bytes) matches this line's canonical factory
0x03a25b…7efaon Ethereum; the v1.0 factory (8342 bytes) matches the v1 line's0xa7bcb4…f99a.Consumer notes
SupportedChainsintentionally breaks downstream exhaustive chain mappings until they add the MONAD/CRONOS/HYPEREVM armsTest plan
pnpm lint(0 errors),pnpm lint:types,pnpm test(23 suites, 137 passed / 1 skipped),pnpm audit --audit-level high,pnpm build— all greenverifyingContractper chain (HyperEVM non-default, Monad/Cronos canonical) andfromNativewrapper resolution for all three chains2.2.2-rc.0verified from a clean consumer install: chain ids, escrow v1.1 addresses,getLimitOrderContract(999), wrappers