Validators, not custodians.Cryptography, not contracts.Sovereignty, not promises.
Underneath all of this runs Smart Engines V3 — open, permissionless software that no person controls. Three genesis clusters started the network; anyone meeting the validator threshold can join. The engines hold the keys, not humans. The math is the contract — and the contract is the same for all of us.
- YouYou choose how you signSign on your own, co-sign with the network, or let the network sign for you under rules it cannot break.written
- The rulesRules the engines obeyValidator rules live on HCS with consensus timestamps. What the Assembly passes is recorded — nothing executes itself.written
- The enginesPieces of a key, never the keyEach engine holds one piece and signs with only that piece. The whole key is never put together — not in a person, not in one machine.running code
- The chainsSigners in publicWho may sign for an account, and how many must agree, is recorded on a public blockchain for anyone to check.running code
Post-quantum, stated exactly Validators also vouch for one another with post-quantum signatures. That is an attestation layer; the custody cryptography itself is not post-quantum.
Four layers, top to bottom. You: sign on your own, co-sign with the network, or let the network sign for you under rules it cannot break. The rules: validator rules live on HCS with consensus timestamps; what the Assembly passes is recorded, and nothing executes itself. The engines: each engine holds one piece of a key and signs with only that piece; the pieces sign together, and the whole key is never put together anywhere. The chains: who may sign for each account is public on the blockchain. Beside the engines: post-quantum signatures are an attestation layer between validators, not the custody cryptography.
Humans never hold the key running code
The key to every account is never put together — not by us, not by any single machine, not even for a split second. It's created as separate pieces held on different computers that sign together using only their own pieces. There is no whole key anywhere to steal, leak, or seize.
Visible multi-member signers running code
Every account records, right on the public blockchain, exactly who is allowed to sign and how many of them must agree — and anyone can look it up and check for themselves. There is no hidden 'one key behind the curtain.' The shared control is the product.
Per-entity keys, never reused running code
Every account gets its own separate keys — nothing is shared between them, so there is no master key and no single wallet that, if broken, would open everything. Who may sign is fixed the moment the account is created and can never be quietly changed afterward.
Three sovereignty modes written
For each account you decide how much help you want: sign entirely on your own, co-sign together with the network, or let the network sign for you under rules it cannot break. It can never quietly step in to pay or act in your place. Sovereignty is structural, not a setting.
What the network actually guarantees
- Humans never hold the key. The key is split into shares held by separate engines and is never assembled anywhere — not in a person, not in one machine, not even for an instant. Each engine signs with its own share; no whole key is ever put together for anyone to steal.running code
- Per-entity DKG is deterministic from the payload. Same payload → same keys, even after the validator set changes. The on-chain pubkey is invariant.written
- On-chain authorization is permanent. No upgrade proxy. No admin function. No way to change who signs for an entity once it's created.written
- Validators never silently pay. The payer chokepoint enforces explicit payer on every prepare endpoint. HTTP 400 otherwise.written
- Anyone can run a node. Permissionless participation: stake 10M HSUITE for a validator, 5M for a host, 2M for a gateway. Built to slash on misbehavior and to score reputation. No gatekeeper. No application form. HSUITE is Smart Engines' own infrastructure-staking token, acquired on the open market — a separate token from HPP's, and never a route into it.written
- The engines obey rules and record the Assembly's will. Validator rules live on HCS with consensus timestamps, addressable by (topicId, timestamp), SHA-256 integrity. Governance proposals are HCS-stored and threshold-voted, and what passes is recorded — but nothing executes itself: a passed deliberation is ratified by the entity's board within a fixed window before any effect, because the Assembly commands through its instrument and the board carries the duty to execute or the duty to refuse. The override is not manual — it is fiduciary.written
Why this is fundamentally different
| Concern | Conventional approach | Smart Engines V3 |
|---|---|---|
| Custody | Held by people — admin keys and recovery phrases that can leak or be seized | No whole key exists anywhere: each computer signs with its own piece, so there is nothing to steal or seize |
| Participation | Gatekept by an admin | Open — stake to run a node, no allow-list, no application |
| Chains | One blockchain at a time | Many blockchains natively — Hedera, XRPL, Stellar, Polkadot, Solana, and more |
| Visibility | The real signers can be hidden behind one key | Every required signer is public on the blockchain, by design |
| Quantum | Breaks when today's cryptography is broken | Validators also vouch for one another with post-quantum signatures — an attestation layer; the custody cryptography itself is not post-quantum |
| Upgrade | An admin can quietly swap the code behind the scenes | Who may sign is set at creation and can never be silently rewritten |
| Coordination | Relies on a single system staying up | Runs across independent clusters that keep working if some fail |
Conventional protocols ask you to trust an admin not to use the upgrade key. Smart Engines V3 don't remove the keys — they take the keys out of human hands. The engines hold them. The engines obey immutable HCS-anchored rules and the DAO's vote. The keys cannot be misused. The rules cannot be silently rewritten. The cryptography cannot lie.