Skip to content
blastDocs

SDK installation

The published on-chain SDK release is 0.1.0. Its bundled mainnet constants refer to the earlier 28 October publication, which the MVR deployment superseded. Use the current packages and shared objects with explicit deployment configuration, as shown below.

The updated MVR bindings are prepared in SDK PR #78 as 0.1.1 for the deployments and compatibility packages. They are not published on npm as of 28 October 2026. Do not install an unpublished version or use 0.1.0 defaults for the current stack.

Install

Section titled “Install”

For a new integration, install the product SDKs you use plus the deployment bindings:

Terminal window
npm install @interest-protocol/blast-presale-sdk@0.1.0 @interest-protocol/blast-launchpad-sdk@0.1.0 @interest-protocol/blast-migrators-sdk@0.1.0 @interest-protocol/blast-deployments-sdk@0.1.0 @mysten/sui@2.26.2 @mysten/move-bytecode-template@0.4.1

You can omit product SDKs you do not use. Keep the on-chain Blast packages on the same release. The Sui and Move bytecode template versions above are the peer versions verified for this release. For Node.js integrations, use Node 22.18 or later. The on-chain SDKs also support browsers and other runtimes with ES2023, BigInt and TextEncoder.

Existing integrations can use the combined compatibility package:

Terminal window
npm install @interest-protocol/blast-sdk@0.1.0 @mysten/sui@2.26.2 @mysten/move-bytecode-template@0.4.1

It preserves the root import and subpaths such as @interest-protocol/blast-sdk/presale, /launchpad, /migrators and /deployments. The standalone and compatible imports resolve to the same implementations.

Configure the current deployment

Section titled “Configure the current deployment”

SDK 0.1.0 call builders accept explicit deployment objects. This presale example uses the current MVR package, its own policy/version objects, and the matching admin ACL:

import { PresaleCalls } from "@interest-protocol/blast-presale-sdk";


const presale = new PresaleCalls({
  "packageId": "0xb0279fbe54bfd1d920e985a4dba0916b2b73a5218514edeecb7b9dd30cf2863b",
  "originalPackageId": "0xb0279fbe54bfd1d920e985a4dba0916b2b73a5218514edeecb7b9dd30cf2863b",
  "packageVersion": {
    "objectId": "0xbf285882f2c2e0eec1afd3dc869e6d25fad70bccd30059ec1a7b7ceb95c3b42f",
    "initialSharedVersion": "2"
  },
  "venueConfig": {
    "objectId": "0xaa4c53cfc143a4548f8ce0b9f6c9e6e2a30be000d496efc53d8763b1bf577eef",
    "initialSharedVersion": "1"
  },
  "creationPolicy": {
    "objectId": "0xac28eb90fea57e13a8c4807f37746811c046508cf46e390fd2ec07a6d7925b31",
    "initialSharedVersion": "1"
  },
  "feePolicy": {
    "objectId": "0x7eee3154e7235f172a3f19c0c7fc3c0721008f22a4cbcd61dc8a4ab0614ef9e0",
    "initialSharedVersion": "1"
  },
  "admin": {
    "packageId": "0x4a27d816998b2ff015cf897a249c069c34859a09e789e56ad3a38992cf00d7ac",
    "acl": {
      "objectId": "0xbda4af615d93435145012eaaeb540bad2fe09ec0cbe6cb99fb0dae7637643a1d",
      "initialSharedVersion": "1"
    }
  }
});

The example constructs a call builder and submits no transaction. Supply the equivalent reviewed deployment configuration to LaunchpadCalls and MigratorCalls; migrations also require the matching launchpad configuration. The address tables list all identities.

In 0.1.0, CANONICAL_MAINNET_*, MAINNET_*_DEPLOYMENT, and getPresaleDeployment("mainnet") still select the superseded stack. A shared object’s initialSharedVersion is its original sharing version, not its latest object version or operational generation.

Package selection

Section titled “Package selection”

All packages below are published at 0.1.0.

npm package Use
@interest-protocol/blast-presale-sdk Presale calls, reads, previews and events
@interest-protocol/blast-launchpad-sdk Bonding-curve creation, trading, reads and events
@interest-protocol/blast-migrators-sdk Venue migration, LP vaults and collection
@interest-protocol/blast-deployments-sdk Canonical identities, access checks and venue readers
@interest-protocol/blast-admin-sdk ACL reads and administrator calls
@interest-protocol/blast-partners-sdk On-chain partner administration and payment previews
@interest-protocol/blast-holder-rewards-sdk Holder-reward accounting and operator workflows
@interest-protocol/blast-core Shared math, transaction and reward primitives
@interest-protocol/blast-coin-sdk Standalone coin creation
@interest-protocol/blast-cctp-sdk EVM USDC deposit parameters and ABIs
@interest-protocol/blast-sui-sdk blastSUI reads, previews and transactions
@interest-protocol/blast-boosts-sdk Boosts reads and transactions
@interest-protocol/blast-sdk Combined root and compatible product subpaths

The separate @interest-protocol/blast-partner-client is an authenticated REST read client, not the on-chain partners SDK. See the Partner API guide. A package being published does not establish deployment or route availability for every product it exposes.

Release scope

Section titled “Release scope”

The 0.1.0 package release and its source predate the MVR redeployment. The current contract source is 52effbc.

BLAST_DEPLOYMENTS remains empty in the published SDK; evaluateProtocolAccess rejects production signing until a verified production deployment is registered. Explicit bindings identify calls; treasury configuration, quote and adapter admission, and venue readiness must still be checked on chain. Package publication does not establish product rollout readiness.