Welcome to Smart Engines

One API for building on Hedera and XRPL today, with Stellar, Polkadot, Solana and Bitcoin next. Every entity key is created by the validator network and exists only as shares, never assembled, and every account is native multisig, so no single party can move funds alone. Every rule that governs your money is public and enforced before anything is signed. Build apps and autonomous agents that are decentralized by default, not as an afterthought.

🧠 For Normies

Normally, to build on a blockchain you either run your own infrastructure (hard) or hand your private keys to a company (scary). Smart Engines is a third option: a decentralized network does the heavy lifting, the keys are split across many machines so no single one can move your funds, and the rules are posted publicly where everyone can check them.

The three things that make it different

Keys are created split, and never assembled

Every entity key is created by a distributed key generation (DKG) ceremony across the validators. No machine ever holds an entity’s whole key, not even to sign: a threshold of validators each sign with their own share (FROST threshold signing), and only those partial signatures are combined into one.

No single key controls anything, including the operators

Every on-chain action is authorized by native multisig on the destination chain. There is no “admin key” that can move funds alone. Even each cluster’s own operator account is a DKG multisig account. The one bootstrap exception is the wallet that funds genesis once: it controls no entity, and the step that deletes it is built but not yet enabled.

The rules are public

Every policy that governs an entity is published on Hedera’s Consensus Service, and the validators check it before they sign. No hidden backdoors, no “trust us.”

What you can build

Ship a multi-chain app

A Smart App: deployed, rule-governed and multisig-secured, on Hedera and XRPL today.

Run an autonomous AI/automation

A Smart Agent: its own identity, wallets, and a rulebook it cannot break.

Move money without holding keys

Host functions (BaaS): provisioning, auth, token lifecycle, all multisig by default.

Monetize access

Subscriptions & NFT memberships with on-chain gating and metering.

The platform in one picture

flowchart TD
    Dev["Builder / App / Agent"] -->|one API| GW["Smart Gateway<br/>routing · discovery · TLS"]
    GW --> HOST["Smart Host<br/>BaaS runtime · functions · metering"]
    HOST --> VAL["Smart Validator<br/>consensus · DKG/TSS signing · rules"]
    VAL -->|native multisig| LIVE["Live: Hedera · XRPL"]
    VAL -.coming next.-> NEXT["Stellar · Polkadot · Solana · Bitcoin"]

    subgraph Genesis["Validator network · BFT<br/>(genesis seed: 3 clusters)"]
      VAL
    end

Three tiers (Gateway, Host, Validator) make up the platform. The validator network is Byzantine-fault-tolerant; genesis seeds it with three clusters to cold-start, and it is designed to open to permissionless node operators after mainnet. The validator tier creates keys, signs by threshold, enforces the rules, and never lets a single party act alone.

Get the full picture in 5 minutes

Where things stand

Live

Live Hedera and XRPL.

Coming next

Coming next Stellar, Polkadot, Solana and Bitcoin, landing in Smart Engines and HSuite Wallet together.

Testnet

Live The testnet runs on HSuite’s validators. It opens to developers once the security audit is complete.

Postponed

Postponed EVM (Ethereum, Polygon): the adapters exist, but they are not wired into the signing path.

XRPL is the canonical home of the HSUITE token and subscription NFTs. Hedera anchors consensus, governance, and audit via HCS. See Chains for what each chain can do.

Tokenomics in 30 seconds

• HSUITE is the network token, issued on XRPL.
• Every fee follows one split: 40% burned, 40% to node operators, 20% to the protocol treasury.
• The node operators’ 40% is split 50% validators · 30% hosts · 20% gateways.
• The treasury is a DKG multisig account, so no single key can spend it.
• Subscriptions are NFT-based memberships on XRPL, with on-chain gating.

→ Read the full Tokenomics, or the value-flow diagram.

Choose your path

Builder

Build your first Smart App · Install the SDK

AI / automation builder

Deploy a Smart Agent

Capital / enterprise

Why it matters · Tokenomics · Security

Node runner

Run a node

Just curious

The 5-minute mental model

Not sure? Choose your path

Quick start

Testnet access

The testnet is live on HSuite’s validators and opens to developers once the security audit is complete. You can install the SDK and work through the guides now.

1. Install the SDK.

   npm install @hsuite/smart-engines-sdk

2. Discover and connect to a cluster.

   import { BaasClient } from '@hsuite/smart-engines-sdk';
   
   // Zero-config: discover and connect to a cluster
   const baas = await BaasClient.connectToCluster({ network: 'testnet' });

Full guide: Zero-config connect

How this book is organized

Start HereThe pitch, the why, and the 5-minute mental model.

Core ConceptsThe trust model: tiers, clusters, DKG/TSS, zero single-sig, rules.

Smart EnginesThe platform tiers in depth.

Smart AppsA builder track: ship a multi-chain app.

Smart AgentsA builder track: run an autonomous AI/automation.

Host FunctionsAn economic surface: move money without holding keys.

SubscriptionsAn economic surface: NFT-based memberships with on-chain gating.

TokenomicsAn economic surface: HSUITE, the network token.

ChainsWhat's live, what's next, and what each chain can do.

SDKThe reference: build with the SDK.

APIThe reference: a unified, chain-agnostic API.

SecurityFor auditors.

Run a nodeHow the network opens to node runners after mainnet.

ReferenceGlossary, FAQ, and source-level further reading.

Lost on a term anywhere in this book? The Glossary explains every one in plain English.