
Security News
OWASP 2025 Top 10 Adds Software Supply Chain Failures, Ranked Top Community Concern
OWASP’s 2025 Top 10 introduces Software Supply Chain Failures as a new category, reflecting rising concern over dependency and build system risks.
@layerzerolabs/hyperliquid-composer
Advanced tools
LayerZero Labs reference EVM OmniChain Fungible Token (OFT) implementation for Hyperliquid
This SDK provides a complete toolkit for deploying and managing HyperLiquid HIP-1 tokens and connecting them to LayerZero OFTs. Commands are organized by workflow to guide you through the deployment process.
To view all commands, run:
npx @layerzerolabs/hyperliquid-composer -h
npx @layerzerolabs/hyperliquid-composer set-block \
--size {small | big} \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY \
[--log-level {info | verbose}]
# Create deployment configuration with optional freeze/quote features
npx @layerzerolabs/hyperliquid-composer core-spot \
--action create \
--oapp-config <layerzeroConfigFile> \
--token-index <coreIndex> \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
# Get existing metadata
npx @layerzerolabs/hyperliquid-composer core-spot \
--action get \
--token-index <coreIndex> \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
Complete the following steps in order to deploy your HIP-1 token:
Must be done before genesis if you want freeze capability.
npx @layerzerolabs/hyperliquid-composer enable-freeze-privilege \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer user-genesis \
--token-index <coreIndex> \
[--action {* | userAndWei | existingTokenAndWei | blacklistUsers}] \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer set-genesis \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer register-spot \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer create-spot-deployment \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
Enables your token to be used as a quote asset for trading pairs. Requirements must be met - see: Hyperliquid API requirements
npx @layerzerolabs/hyperliquid-composer enable-quote-token \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
Can be done at any time after deployment:
npx @layerzerolabs/hyperliquid-composer trading-fee \
--token-index <coreIndex> \
--share <[0%,100%]> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
After completing HIP-1 deployment, link your token to a LayerZero OFT:
npx @layerzerolabs/hyperliquid-composer request-evm-contract \
--oapp-config <layerzero.config.ts> \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer finalize-evm-contract \
--oapp-config <layerzero.config.ts> \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
Only available if freeze privilege was enabled before genesis:
# Freeze a user
npx @layerzerolabs/hyperliquid-composer freeze-user \
--token-index <coreIndex> \
--user-address <0x...> \
--freeze true \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
# Unfreeze a user
npx @layerzerolabs/hyperliquid-composer freeze-user \
--token-index <coreIndex> \
--user-address <0x...> \
--freeze false \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
Permanently removes freeze capability (irreversible):
npx @layerzerolabs/hyperliquid-composer revoke-freeze-privilege \
--token-index <coreIndex> \
--network {testnet | mainnet} \
--private-key $PRIVATE_KEY_HYPERLIQUID \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer spot-deploy-state \
--token-index <coreIndex> \
--network {testnet | mainnet} \
[--deployer-address <0x...>] \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer hip-token \
--token-index <coreIndex> \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer is-account-activated \
--user <0x...> \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer get-core-balances \
--user <0x...> \
[--show-zero {false | true}] \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer list-spot-pairs \
--token-index <coreIndex> \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer spot-auction-status \
--network {testnet | mainnet} \
[--log-level {info | verbose}]
npx @layerzerolabs/hyperliquid-composer to-bridge \
--token-index <coreIndex> \
[--log-level {info | verbose}]
FAQs
LayerZero Labs reference EVM OmniChain Fungible Token (OFT) implementation for Hyperliquid
The npm package @layerzerolabs/hyperliquid-composer receives a total of 202 weekly downloads. As such, @layerzerolabs/hyperliquid-composer popularity was classified as not popular.
We found that @layerzerolabs/hyperliquid-composer demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
OWASP’s 2025 Top 10 introduces Software Supply Chain Failures as a new category, reflecting rising concern over dependency and build system risks.

Research
/Security News
Socket researchers discovered nine malicious NuGet packages that use time-delayed payloads to crash applications and corrupt industrial control systems.

Security News
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.