Some forge tests may generate fixtures in the [fixtures](./fixtures/) directory. This allows [SDK](../typescript/sdk) tests to leverage forge fuzzing. These are git ignored and should not be committed.
Some forge tests may generate fixtures. This allows the [SDK](https://github.com/hyperlane-xyz/hyperlane-monorepo/tree/main/typescript/sdk) tests to leverage forge fuzzing. These are git ignored and should not be committed.
@ -18,12 +18,6 @@ Note, this package uses [ESM Modules](https://gist.github.com/sindresorhus/a3978
## Contents
### Constants
The names and relevant metadata for all Hyperlane-supported chains are included in this SDK, including public RPC and Explorer urls. It also includes the addresses for all Hyperlane core contracts and middleware.
### Classes for development, deployment, and testing
The SDK includes various classes for building, deploying, and testing multi-chain applications. Different abstractions serve different use cases. A few common utilities include:
- `MultiProvider` / `MultiProtocolProvider`: A utility for managing chain metadata, and RPC providers.
@ -32,15 +26,6 @@ The SDK includes various classes for building, deploying, and testing multi-chai
- `HyperlaneDeployer`: The base class for executing multi-chain contract deployments.
- `Token`&`WarpCore`: Utilities for interacting with Warp Route deployments.
### Chain Logos
The SDK contains SVG files for all Hyperlane-supported chains. They can be imported from the `/logos` folder.
```js
import ArbitrumBlack from '@hyperlane-xyz/sdk/logos/black/arbitrum.svg';
import ArbitrumColor from '@hyperlane-xyz/sdk/logos/color/arbitrum.svg';
J M Rossy
6 months ago
committed by
GitHub