Developers
Build on Smart Engines once the testnet opens to developers.
Smart Engines follows a methodical approach to multi-chain expansion, ensuring security, stability, and community alignment at every phase. This roadmap separates what is done, what is in progress and what is planned. It carries no dates.
The testnet is live on validators operated by HSuite. It opens to developers once the security audit is complete. Mainnet has no date yet.
| Chain | Status | Key Features |
|---|---|---|
| Hedera | Live | HCS topics for consensus, rule publication, governance and audit; mirror node reads |
| XRPL | Live | The HSUITE token, trust lines, native NFTs (subscriptions and memberships), SignerList multisig |
| Chain | Status | Expected Features |
|---|---|---|
| Stellar | Coming next | Accounts, issued assets, native multisig |
| Polkadot | Coming next | Assets pallet, native multisig |
| Solana | Coming next | SPL tokens, Metaplex NFTs, SPL multisig |
| Bitcoin | Coming next | Transfers from native multisig (P2WSH) |
| Ethereum, Polygon | Postponed | EVM support is postponed |
Stellar, Polkadot, Solana and Bitcoin will land in Smart Engines and HSuite Wallet together.
hsuite CLI, both published on npmThe next chains are Stellar, Polkadot, Solana and Bitcoin. Each has an adapter library; none is enabled on the testnet yet.
Technical Milestones:
Technical Milestones:
| Tool | Status | Description |
|---|---|---|
| CLI | Available | Command-line interface for devs (@hsuite/smart-engines-cli on npm) |
| Dashboard | Planned | Web-based validator management |
| Playground | Planned | Interactive API testing |
| Templates | Planned | Starter templates for common apps |
Priority evaluation based on:
No chain is committed beyond the ones listed as coming next.
Each new chain goes through the same stages, in order:
flowchart TB
M12["Assessment and Planning<br/>Technical analysis<br/>Resource allocation<br/>Community engagement"]
M36["Core Development<br/>Chain adapter implementation<br/>Account management<br/>Token operations"]
M79["Feature Completion<br/>NFT support<br/>Chain-specific features<br/>Testing infrastructure"]
M1012["Security and Testing<br/>Internal testing<br/>Security audit<br/>Community beta"]
M1315["Deployment<br/>Testnet launch<br/>Mainnet launch"]
M1618["Optimization<br/>Performance tuning<br/>Feature additions<br/>Community feedback"]
M12 --> M36 --> M79 --> M1012 --> M1315 --> M1618
The technical measures we track:
The ecosystem measures we track:
| Risk | Mitigation |
|---|---|
| Chain protocol changes | Modular adapter architecture |
| Performance bottlenecks | Separate tiers, caching |
| Security vulnerabilities | Security audit before the testnet opens to developers |
| Risk | Mitigation |
|---|---|
| Key personnel | Knowledge documentation, team expansion |
| Regulatory changes | Legal counsel, compliance monitoring |
| Market conditions | Treasury spending caps and a minimum balance |
| Risk | Mitigation |
|---|---|
| Chain compatibility | Thorough assessment phase |
| Community adoption | Early engagement, developer incentives |
| Resource constraints | Phased rollout, community contributions |
Developers
Build on Smart Engines once the testnet opens to developers.
Validators
Run validator nodes once the network opens to node runners.
Token Holders
Vote on protocol DAO proposals.
Community
Provide feedback, report issues.