Summary

Enables two new Wormhole NTT routes between NEAR and Hydration:

• ZEC: zec.omft.near ↔ Hydration (asset id 1001357, "Zcash")
• NEAR: wrap.near ↔ Hydration (asset id 1001358, "NEAR")

NEAR is the hub. Tokens are locked in a native NTT contract on NEAR and minted/burned on Hydration. Both sides are already deployed, peered, rate-limited, source-verified and handed over to their final owners. This referendum turns the routes on.

The routes launch with canary limits (10 ZEC and 1,000 NEAR per 24 h, each direction), to be raised later in a separate proposal.

What it executes

Dispatches the call whitelisted by the Technical Committee (hash 0x8c6f980a1c690bd89dca7dec663e74454c2d04730bc1d43999e1d8c3b6b303ec): one utility.batch_all with 8 calls.

Asset	Call	Effect
ZEC 1001357	CircuitBreaker.set_asset_category(1001357, External)	global withdraw-limit accounting, like all other NTT assets
	AssetRegistry.update(1001357, name: "Zcash", xcm_rate_limit: 10 ZEC)	mint fuse = canary limit; drops the "(Wormhole)" suffix
	MultiTransactionPayment.add_currency(1001357, 6.267e-10)	fallback price (1 ZEC ≈ 159,566 HDX), so outbound transfers can be valued before pools exist
	EVMAccounts.set_ntt_minter(1001357, 0xe20cED5f5798cD4FeBc7aE182309b9f51345e0cC)	lets the Hydration NTT manager mint/burn ZEC
NEAR 1001358	CircuitBreaker.set_asset_category(1001358, External)	global withdraw-limit accounting
	AssetRegistry.update(1001358, name: "NEAR", xcm_rate_limit: 1,000 NEAR)	mint fuse = canary limit; drops the "(Wormhole)" suffix
	MultiTransactionPayment.add_currency(1001358, 1.443e9)	fallback price (1 NEAR ≈ 693 HDX) until pools exist
	EVMAccounts.set_ntt_minter(1001358, 0x374E5239a2342Be6Bf31B410EC03984D03A8b7dE)	lets the Hydration NTT manager mint/burn NEAR

Routes

Token	NEAR hub (locks)	Hydration (mints/burns)	Daily limit (each way)
ZEC	ntt-zec.hydration-whm.near locking zec.omft.near	manager 0xe20c…e0cC, transceiver 0x0dd4…DE85	10 ZEC
NEAR	ntt-near.hydration-whm.near locking wrap.near	manager 0x374E…b7dE, transceiver 0xc74B…81d1	1,000 NEAR

On NEAR, one contract acts as both NTT manager and Wormhole transceiver. Its Wormhole address is sha256(<account id>):

• ZEC: 0xca4092420316d55cfbb9a479ca23fdf0f5a0864a80c755b46e071c834fbf3976
• NEAR: 0xd473056b88c2062503ea1425bdea8e87609e3d499b3b4d1809e440df2d7cb9e3

The Hydration contracts are peered to exactly these addresses.

Safety

• Ownership
  • Hydration legs: emergency admin 0xAA7e0000000000000000000000000000000AA7E1.
  • NEAR contracts: owned by hydration.sputnik-dao.near. The deployer access keys have been deleted, so only the DAO can upgrade the code (owner-gated upgrade).
• Canary limits on both sides (NTT rate limits), matched by the Hydration mint fuses (xcm_rate_limit), plus the global withdraw circuit breaker.
• Source-verified (exact match): Hydration contracts on the Hydration explorer.
• Emergency off-switch: EVMAccounts.clear_ntt_minter(id) stops minting and burning on Hydration without touching any contract. Each side can also be paused by its owner.
• Dry-run: the full call was dry-run against live state as WhitelistedCaller and succeeded, emitting all eight expected events.
• The NEAR NTT contract is new and launches at canary limits. The limits will be raised in a follow-up proposal after the first transfers have settled in both directions.

Verify

• Preimage hash: 0x10dad20ba0b30327f5968cb0e95dc08fe3a857fc95cb23bd2593837ab38e6ddd (188 bytes, whitelist.dispatch_whitelisted_call_with_preimage)
• Inner call (decode it, and check its blake2_256 equals the whitelisted hash above):

0x0d0220410b8d470f00010033018d470f0001145a6361736800000100ca9a3b00000000000000000000000000000000cb018d470f00e0ae5a250000000000000000000000005d078d470f00e20ced5f5798cd4febc7ae182309b9f51345e0cc410b8e470f00010033018e470f0001104e454152000001000000e83c80d09f3c2e3b030000000000000000cb018e470f0000000083721fadbe229fa904000000005d078e470f00374e5239a2342be6bf31b410ec03984d03a8b7de