Eight scam checks, run on your device.
Transactions from apps inside HSuite Wallet — and your history — are screened for address poisoning, dust, impersonation, Unicode tricks and more.
High risk? You have to acknowledge it. The decision stays yours.
Don't guess what a rule will do. Dry-run it.
rules.simulate sends an action and its context through the same evaluator Smart Engines validators use, and returns isValid plus the reason.
A 101 transfer against a 100 cap? isValid: false — before you ever rely on it.
Available to builders when the testnet opens.
🚨 SILK SUITE HAS COMPLETED ANOTHER SECURITY AUDIT WITH @HalbornSecurity
1/ 🔐 Another Security Audit
We've once again partnered with @HalbornSecurity to audit our upgraded DEX infrastructure.
Halborn, which also serves on the Hedera Governing Council, brings extensive blockchain security expertise to the engagement.
Security remains a fundamental priority as we continue to expand the Silk Suite ecosystem.
The Smart Engines docs are live 📚
Everything you need to build on HSuite, in one place: Smart Apps, Smart Agents, Host Functions, the SDK, the API, and the security model behind signing keys that only ever exist as shares.
Start here 👇
https://t.co/ojHaA4Fl5o
Testnet is live too, but it isn’t open to developers yet. It stays closed until the security audit is complete.
Multisig shouldn't need a spreadsheet and a group chat.
In Native Connect it's a channel type: hsc:party coordinates M-of-N signing across devices, on Hedera threshold keys and XRPL multi-signing. Every signer approves on their own device.
Don't trust us. Check the chain.
On Hedera and XRPL, entities Smart Engines creates are controlled by the chain's own multisig: a threshold KeyList on Hedera, a SignerList on XRPL with the master key disabled.
The proof will be on HashScan and Bithomp, not in our docs.
Stellar, Polkadot, Solana and Bitcoin follow the same principle as they come online: weighted signers, pallet_multisig, Squads v4 and P2WSH.
Always the chain's own multisig. Never one opaque key.
hey guys! Due to technical issues with X, we are moving our AMA here right now: https://t.co/rhpeqc0Mtb
If you are not part of our discord yet please join us $XRPL $HSUITE $HBAR
Every chain is a silo. Every single key is a point of failure. A valid transaction is not an authorised one.
HSuite is not another blockchain. It is becoming the layer that governs what happens across blockchains.
Wallet connections without a vendor account.
Native Connect's hsc: protocol needs no Project ID and no dashboard: an encrypted channel over a Nostr relay, direct WebRTC when possible, sessions capped at 24 h.
Need WalletConnect too? One Angular button speaks both.
$HSUITE is going canonical on XRPL. Here is everything holders need to know. 👇
⚡Short version: your tokens are safe, there is nothing to do today, and any migration is always 1:1.
📍 What's happening?
$HSUITE is becoming a canonical token on the XRP Ledger. XRPL becomes the single home where $HSUITE is issued, held, traded and settled. Hedera stays a fully supported network for HSuite builders and apps.
💡 Why?
Powered by the only blockchain featuring a native built-in DEX, XRPL allows payments from any supported chain to settle directly into real $HSUITE. Consolidating into one token instead of many keeps supply, liquidity, and trust in one place, while XRPL typically settles transactions quickly and at a low cost.
🙋 Do I need to do anything today?
No. Your $HSUITE on Hedera is safe, your balance hasn't changed, and migration isn't open yet. It won't open without at least one month of public notice.
🔢 The numbers
✅Always 1:1
✅No fees from HSuite
✅Total supply stays 38.272B
✅Every $HSUITE issued on XRPL = one sent to the Hedera burn wallet
✅Nothing is pre-minted. XRPL supply starts at zero.
⏳ The window
Migration stays open for six months. Nothing is frozen or paused during it, and your tokens stay fully transferable on Hedera.
After the window, the Hedera token is frozen. But your claim never expires. Prove ownership of your Hedera wallet and claim 1:1 on XRPL anytime. Unmigrated tokens are never burned or confiscated.
🔐 Who controls the XRPL issuer?
No one. Not even us. The key is generated jointly by independent HSuite nodes (DKG). Each holds a small piece. The full key never exists in one place.
Every mint must be signed together by a threshold of nodes (TSS). No individual, company or compromised machine can mint, freeze or move $HSUITE alone. Governance is designed to pass to Project X Suite - Wyoming DUNA (the HSuite DAO).
🛠️ How migration will work
1. HSuite Wallet → "Port your token"
2. $HSUITE goes to the burn wallet
3. Smart Engines v3 nodes verify and sign the mint
4. Same amount arrives on XRPL
No XRPL account? The wallet creates one.
🤔 Do I have to migrate?
It's your choice and your timing. We recommend it, because the XRPL market, future settlement and token functions like burn mechanics will live on XRPL. Hedera $HSUITE won't have access to those.
👷 Builders
Keep building on Hedera. Existing smart apps keep running with no disruption. Pay in your chain's native or accepted asset (HBAR, XRP, BTC, ETH, SOL, USDC and more). Settlement into $HSUITE happens behind the scenes.
🤝 Partners like Silk Suite
Nothing changes in how you operate. Silk Suite keeps running on HSuite community nodes on Hedera, paying in HBAR. The only difference is that value bridges through canonical $HSUITE on XRPL at settlement.
🚨 Stay safe
We share details only through official channels. We will NEVER ask for your seed phrase or private keys, or ask you to send $HSUITE to an address not in our official migration instructions.
Be wary of DMs claiming to be HSuite. ⚠️
Please note that members of the HSuite Team will never send links or migration instructions through Discord/X direct messages or chat channels.
📅 Timeline
Mainnet migration is targeted for Q1 2027, after the v3 audit, testnet and published migration instructions. FAQ https://t.co/eLd8nRQ5uk is live to address any community concerns.
🎙️Questions? Join our community AMA on Nov 6, 2026 at 5:00 PM UTC, here on X.
No price or liquidity promises. Official channels only.
Most policy engines are black boxes. Ours is published.
Every Smart Engines rule lives on Hedera HCS, public and ordered. Before any key share is released, the sign gate checks the rule. If the check fails, nothing signs.
Your auditor reads HCS. So can you.
Want to know what a rule will do before you rely on it? Dry-run the request against the same evaluator the validators use:
POST /api/v3/baas/rules/simulate
The HSuite DUNA governance roadmap is live 🏛
9-member Transitional Board · 5-of-9 approvals · strict conflict-of-interest rules · public Decision Log · handover or sunset of existing board by Mar 31, 2027.
Not decentralization by declaration. Accountable governance, by design.
https://t.co/W3kxoz8q7Z
A login signature should never be able to move your funds.
HSuite Wallet binds every signed message to its chain and purpose. The signature that signs you in can't be replayed as a transaction — by design, not by luck.
One key on one machine is one breach away from zero.
In Smart Engines, every entity gets its own key ceremony. On Hedera and XRPL its signing key exists only as shares: a validator quorum signs with FROST, and the chain sees its own native multisig.
Why per entity? Compromise stays contained — no key reuse across tokens, accounts, topics or apps.
And because authority is the chain's own multisig, you won't have to take our word for it — you'll be able to open HashScan or Bithomp and read the signer set yourself.