Hyperliquid

Dinari dShares™ are available in the Hyperliquid ecosystem and are supported in both HyperEVM and HyperCore, with special considerations for tokens deployed in each environment.

HyperEVM

HyperEVM is Hyperliquid’s EVM-compatible execution layer. HyperEVM is the primary environment where Dinari deploys the underlying tokenized asset representation for Hyperliquid-related flows. For each supported asset on HyperEVM, Dinari deploys a dShare and its corresponding wrapped dShare.

HyperEVM limitations and considerations

Before integrating with dShares on HyperEVM, keep the following in mind:

• Both token types exist on HyperEVM, but they are used differently.
• Wrapped dShares are primarily used for HyperCore-linked flows.
• Availability is asset-specific; not every asset will necessarily be deployed at the same time.

HyperCore

HyperCore is Hyperliquid's order book layer. Tokens on HyperCore are explicitly linked to their corresponding wrapped dShare on HyperEVM; they are not separate or independently wrapped tokens.

This means:

• HyperCore support is not automatic when an asset exists on HyperEVM.
• Wrapped dShares are the asset form used for HyperCore connectivity.

Special considerations for HyperCore

• On HyperCore, users interact with a wrapped representation of a dShare rather than the base HyperEVM dShare itself.
• HyperCore support depends on an additional deployment and linking process beyond deploying a dShare on HyperEVM.

HyperCore limitations and considerations

The main limitations on HyperCore are structural:

• Each asset requires explicit registration and linkage,
• HyperCore and only bridge to HyperEVM. To bridge to any other chain you need to bridge to HyperEVM and then to your target chain.

Key takeaways

When interacting with dShares on Hyperliquid, the most important points are:

• dShares are the primary bridgeable asset form.
• Wrapped dShares are required for HyperCore-linked usage.