Core Concepts

What you’ll get here

the mental model behind Smart Engines — read these pages in order and the rest of the docs (chains, SDK, operations) will click into place.

Smart Engines is a multi-chain backend where no single machine and no single operator can sign on your behalf. Every on-chain account it controls is a native multisig, and the keys it creates for those accounts are generated in pieces and kept only as pieces. That design decision ripples through every other concept on this page. The fastest way to understand the platform is to follow that thread from the bottom up: first why we don’t trust any single party, then how the cryptography makes that real, then what you actually build on top.

Smart Engines runs on Hedera and XRPL today. Hedera carries consensus: rule publication, governance and audit topics. XRPL carries accounts and tokens, including the HSUITE token and the subscription and membership NFTs. Stellar, Polkadot, Solana and Bitcoin come next.

🧠 For Normies

A “concept” page explains an idea, not a button. By the end of this section you’ll understand how Smart Engines can sign blockchain transactions for you without any single computer being able to forge your signature — and why that matters more than it sounds.

---

The learning path

Read these in order. Each builds on the one before it.

1. Trustless CoreThe starting axiom: verify everything, trust nothing — including us.

2. DKG & TSSHow a key can be born already split across machines and signed with by a quorum.

3. Zero Single-SigEvery on-chain authority the network creates is a native multisig — and you can see that on explorers.

4. Network & TiersThe three apps — validator, host, gateway — and how they talk.

5. Three-Cluster GenesisHow the testnet bootstrapped itself from three independent clusters.

6. Entities & SovereigntyWhat an “entity” is, and the partial vs full control modes.

7. Rules EnginePolicy is published publicly on Hedera HCS, mandatory, enforced per transaction.

8. Decentralization ModelThe trust model in one place: what no single party can do.

9. Personhood & Web of TrustA personhood layer for Sybil resistance: built, not yet enabled.

10. Post-Quantum SecurityWhere ML-DSA signatures and ML-KEM encryption are used today, and what is not quantum-safe yet.

🧠 For Normies

Pages 1–3 are the “why and how it’s safe” foundation. Pages 4–6 are the “what’s running and what you create.” Pages 7–10 are the “rules, trust, and future-proofing.” If you only read three, read Trustless Core, Network & Tiers, and Entities & Sovereignty.

---

The one idea to hold onto

Everything here is downstream of a single sentence:

No single machine and no single operator can sign on your behalf. The validators must mathematically agree.

If a claim in any of these pages seems to contradict that sentence, the sentence wins — that’s the invariant the whole platform is built to protect.

---

Next steps

Start the path:

Trustless Core

Network & TiersPrefer the architecture-first route.

GlossaryWant the precise term definitions.