Finalize EVM contract linkage
Hyperliquid node API
Finalize EVM contract | Hyperliquid exchange
Finalize the link between a HyperCore token and its HyperEVM contract. On Hyperliquid exchange.
POST
Finalize EVM contract linkage
You can only use this endpoint on the official Hyperliquid public API. It is not available through Chainstack, as the open-source node implementation does not support it yet. See Hyperliquid methods for the full availability breakdown.
This endpoint requires signature authentication. See our comprehensive Authentication via Signatures guide for implementation details.
finalizeEvmContract action finalizes the link between a HyperCore token and its HyperEVM contract, using a verification method that matches how the contract was deployed.
Get your own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
Parameters
Required parameters
action(object, required) — The finalize-EVM-contract action:type(string) — Must be"finalizeEvmContract".token(number) — The token identifier to link.input— The verification method, one of:{ "create": { "nonce": <number> } }— for a contract deployed from an EOA; uses the EVM deployment nonce."firstStorageSlot"— the finalizer address is stored at the contract’s first storage slot."customStorageSlot"— the finalizer address is stored at slotkeccak256("HyperCore deployer").
nonce(number, required) — Current timestamp in milliseconds.signature(object, required) — EIP-712 signature of the action.
Optional parameters
expiresAfter(number, optional) — Timestamp in milliseconds after which the request is rejected.
Returns
Returns an object with the action status:status—"ok"if the request was processed.response— Contains operation details, withtype"default".
Example request
Response example
Use cases
- Link a token to its EVM contract — Complete HyperCore/HyperEVM token linkage
- Token deployment tooling — Finalize contracts as part of a deploy pipeline
- Verify deployment ownership — Prove control via deploy nonce or storage slot
Body
application/json
Last modified on June 24, 2026