Rising Tide Developers
SDK

Installation

Adding the Rising Tide SDK to your Next.js project.

Get the tarball

The SDK is distributed as a tarball. Contact the protocol team to get the latest rising-tide-sdk-<version>.tgz and copy it to your project root. The Changelog records the current version and what each release changed - its newest entry is the version you should be handed.

Add to package.json

{
  "dependencies": {
    "@rising-tide/sdk": "file:./rising-tide-sdk-<version>.tgz"
  }
}

Use the real filename of the tarball you received in place of <version>.

Install

npm install

Version updates

When the SDK is updated, the tarball filename changes (e.g., 0.14.53 -> 0.14.54). Update the package.json reference and run npm install again. npm caches by version - the filename change forces a fresh install.

Tree-shaking

The SDK is headless - it ships three tree-shakeable entry points and carries no React, auth, or wallet UI:

Entry pointWhat it carries
@rising-tide/sdkRoot - RisingTideSDK class, types, errors
@rising-tide/sdk/adminRisingTideAdmin and admin-only operations
@rising-tide/sdk/schemasZod schemas for runtime validation

React hooks, auth providers, the Privy wallet provider, the app shell, design tokens, and the consolidated RisingTideProviders stack live in the companion @rising-tide/ui package (which depends on the SDK):

Entry pointWhat it carries
@rising-tide/ui/reactReact Query provider, data hooks
@rising-tide/ui/authAuth providers, AuthGate, ProtocolUserProvider
@rising-tide/ui/providersRisingTideProviders - the whole provider stack, config-driven
@rising-tide/ui/shellApp shell primitives (AppShell, SubNav, FootBar, TestnetBanner)
@rising-tide/ui/tokensDesign tokens (foundations.css)
@rising-tide/ui/themeThe semantic @theme mapping, imported after the tokens
@rising-tide/ui/primitivesBrand-density Button, Card, Badge, Input, state components and the toast queue
@rising-tide/ui/storageThe owner's Save As surface
@rising-tide/ui/testingTest scaffolding, never product code

@rising-tide/ui/safe-area.css and @rising-tide/ui/shell.css are stylesheet exports. See the UI package page for detail.

// Headless data layer from the SDK
import { RisingTideSDK } from "@rising-tide/sdk";
// React surface from the UI package
import { useSmartProduct } from "@rising-tide/ui/react";