Smart Engines companion

Wallet and Smart Engines: two products, designed together.

Each is its own product with its own protocol. They're built to work better together, the Wallet is how a user installs, pays for, and operates the smart-apps and smart-agents running on the Smart Engines network.

Mint subscription NFTs

Smart-apps and smart-agents on Smart Engines are gated by subscription NFTs. The Wallet mints them, holds them, and presents the right one to whichever app you launch.

Browse the smart-apps marketplace

The Wallet ships with a marketplace view of every deployed smart-app on the network, install one as a widget, launch the full app, or just preview what it does.

Smart-apps as widgets

Installed smart-apps appear as embeddable widgets inside the Wallet, a portfolio rebalancer card, a treasury status block, an alerts panel, composed into your home screen.

Become a Node Runner

The Wallet is the registration path for permissionless validator onboarding when the program opens, stake, run a node, earn HSUITE for validation work.

You can use the Wallet without using Smart Engines, and Smart Engines without the Wallet, but the combo unlocks the marketplace, widgets, subscriptions, and Node Runner flow.

Multi-chain

One identity. Every chain.

Hedera and XRPL are live today. More chains land as Smart Engines adapters ship. Same Wallet, same keys, same UX, every chain.

Live

Planned

Connect SDK

Drop-in wallet auth for any dApp.

HSuite's native answer to WalletConnect, an open protocol that lets any dApp accept HSuite Wallet logins with a single signature, returning a short-lived JWT and a cross-chain signing primitive.

OAuth-style flow, one signature, short-lived JWT
Multi-chain, auth from whatever chain the user holds
No vendor lock-in, REST endpoints + open spec
No bespoke auth server on your backend
Same identity across the user's installed smart-apps
Drop-in replacement for WalletConnect / MetaMask SDK

Click any tab to see real SDK code.

sign-in.ts

// Drop-in wallet auth, one signature, short-lived JWT.
import { HSuiteConnect } from '@hsuite/native-connect-sdk';

const connect = new HSuiteConnect({
  appId: 'your-app-id',
  chains: ['hedera', 'xrpl'],
});

// 1. Open the wallet picker, user signs ONCE
const session = await connect.signIn();
// → { token, address, chain, expiresAt }

// 2. Use the JWT on every subsequent API call
const res = await fetch('/api/whoami', {
  headers: { Authorization: `Bearer ${session.token}` },
});

// 3. Sign out when done (revokes the session server-side)
await connect.signOut();

MultiSig, native to the protocol

Threshold signing. Shared custody.

N-of-M approval baked into the Connect protocol, no smart contract, no Solidity, no Gnosis-Safe-style deployment. The Wallet's quorum logic is part of the protocol itself, so multisig works out of the box on every chain the Wallet supports.

Threshold signing, N-of-M approval at the protocol level
No smart contract deployment, no audit, no gas overhead
Per-asset and per-recipient spending policies
On-chain audit trail for every approval
Works across all chains the Wallet supports
Mobile push notifications for co-signer approvals

multisig.ts

// Native multisig, N-of-M approval at the Connect protocol level.
// No smart contract deployment. No bespoke quorum infra. Just the SDK.
import { HSuiteConnect } from '@hsuite/native-connect-sdk';

const connect = new HSuiteConnect({ appId, chains: ['hedera'] });
await connect.signIn();

// 1. Create a multisig vault, protocol holds the threshold + policy
const vault = await connect.multisig.create({
  threshold: 2,             // signatures required to move funds
  signers: [alice, bob, carol],
  policy: {
    perRecipient: 1000,     // max per-tx spend in USD-equivalent
    allowedTokens: ['USDC', 'HBAR'],
    timelock: '24h',        // optional cooldown after proposal
  },
});

// 2. Propose a transaction, wallet routes to all co-signers
const proposal = await connect.multisig.propose({
  vault: vault.address,
  tx: { to: recipientAddr, amount: 500, token: 'USDC' },
});

// 3. Co-signers approve via push, protocol enforces the threshold
const result = await proposal.waitForExecution();
// → { txId, signatures: [alice, bob], blockHeight }

Security & custody

Your keys. Your call.

The Wallet is non-custodial. Keys live on the device, signing happens on the device, recovery happens on the device. No server-side custody anywhere in the loop.

Non-custodial by design

Private keys live on the device. The Wallet never sees them, never holds a backup, never has the option to spend on your behalf.

Encrypted backup + restore

Optional encrypted vault backup with user-held passphrase. Recovery is local, no server to compromise, no support ticket to social-engineer.

Biometric unlock

Face / Touch ID for daily use; full passphrase only on first install and explicit restore. Signing prompts always require local confirmation.

Build with the Wallet. Ship a real app.

Wire the Connect SDK into your dApp for drop-in auth + cross-chain signing + native multisig. Or go a step deeper and run on Smart Engines so the wallet, app, and on-chain proofs all live in one stack.

Build a Smart-App Build a Smart-Agent Smart Engines deep dive

Your gateway to Smart Engines.