JimJim retweeted
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.
ALT "Wallet connections, no vendor account." Native Connect's hsc: protocol needs no Project ID and no developer dashboard, just an encrypted channel between the dApp and the wallet.
ALT "Two protocols. Different trade-offs." WalletConnect v2: Project ID required, always via the WalletConnect relay, 7-day default sessions. Native Connect hsc:: no Project ID or account, Nostr relay upgraded to WebRTC peer-to-peer, sessions hard-capped at 24 hours, M-of-N party channels built in. HSuite's Angular button supports both.
ALT "Less to configure. Less to trust." No project key to register or rotate; messages go peer-to-peer over WebRTC when the network allows; every hsc: session ends within 24 hours.
ALT "Use both. One button." The wallet-connect-button component speaks hsc: and WalletConnect v2. npm i @hsuite/native-connect-angular
JimJim retweeted
To celebrate our new WoW Forever site, we're giving away some goodies✨
To enter, RT this tweet and reply telling us what class/race combo you're most excited to play in Forever.
3 winners will receive:
♾️ WoW Forever Epic Edition (kindly provided by Blizzard)
🎁 $25 Battle.net Gift Card
💜 3 months of Archon Platinum
...and 10 more players will receive 1 month of Archon Platinum!
#Warcraft #WoWForever
I dont think ive ever been this keen for anything in my life
JimJim retweeted
Now buy tokenized stocks with $SILK and other HTS tokens, utilizing our DEX:
Classic automatically picks the better route✅
EXAMPLE:
SILK → USDC → $AAPL / $TSLA / $AMC (and more)
Zero-slippage, non-custodial, on Hedera ✅
Trade now → silksuite.app/#/tabs/silkdex…
JimJim retweeted
$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 hsuite.app/migration 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.
JimJim retweeted
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
ALT "The rules are public." Every policy is published on Hedera HCS; before a key share is released the sign gate evaluates the rule and fails closed. Conceptual panel: the rule comes from a public HCS topic, the check uses the same evaluator as the simulate endpoint; pass releases a share and the quorum signs, fail or error means no share leaves the validator.
JimJim retweeted
Giving away 3 WoW forever codes for the launch in 2 days. Like and comment to enter. Winners will be announced in 24 hours from right now.
JimJim retweeted
🚨 Major Announcement 🚨
@HSuiteNetwork has been building for the future of interconnected chains.
This marks a major milestone in the roadmap for $HSUITE.
Thanks to all of supporters of HSUITE, who have made it possible & the teams persistence to fulfil a vision.
📢HSuite XRPL Migration Announcement
Read all about what going Canonical on the XRPL means in our news post linked below👇
hsuite.app/news/hsuite-is-go…
JimJim retweeted
📢HSuite XRPL Migration Announcement
Read all about what going Canonical on the XRPL means in our news post linked below👇
hsuite.app/news/hsuite-is-go…
JimJim retweeted
Le come back historique de Youssef Boughanem face à Mohamed Soumah ! 🤯
#ARES44
JimJim retweeted
10 years ago, these legends of the sport stood on different podiums at 3 different weight classes in the 2016 Rio Olympics.
Today they stood together on one.
JimJim retweeted
🚨 JUST IN: Binance Says It Will Pay Everyone Back... XRP Holders, Here’s The CATCH (BREAKING CRYPTO NEWS)?
JimJim retweeted
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.
hsuite.app/governance
JimJim retweeted
$6.3B. Largest crypto theft ever. The cryptography never broke.
No key "leaked." A DevOps laptop got compromised, the attacker reached an internal signing pipeline, and had it produce valid authorizations. The math held. The boundary around *what can make the system sign* didn't.
"But multi-sig?" An exchange signs thousands of withdrawals a minute — no human clicks approve. The signers are automated. If one process can reach them, it doesn't steal keys; it asks, and the infra signs, because that's its job. m-of-n means nothing when one actor can summon all n. WazirX was multi-sig. Bybit was multi-sig. Both drained.
Signatures don't protect you when a single point can make the system produce them. On Ethereum this ran through EIP-7702 — one authorization was all it took. Both are real flaws: the signing path reachable by one human is what let them get a valid authorization at all, and 7702 made it permanent — one auth turns the wallet into attacker code that keeps draining every future deposit. One let them in, the other made it catastrophic.
When I was younger I studied Mitnick obsessively — not to break anything, but to understand hacking on a human level. His whole point: you don't beat the crypto, you beat the person, the process, the one endpoint with access. Thirty years later, $6.3B, same lesson.
And that's the whole thing. Every one of these traces back to a human or a known endpoint sitting in the control path. The fix isn't better humans — it's removing the human-shaped single point entirely. No one person who can sign. No one machine you can phish. No named party you can subpoena. The tech enforces the rules; nobody can override it; the operators are anonymous and distributed, so there's no "guy with access" to compromise and no one to lean on. You can't social-engineer a system that gave no human unilateral power.
The "recovery" this week? ~$3B frozen — by centralized issuers, USDC, USDT, a chain's security council. Not a decentralization win. Centralization doing what it's good at.
But decentralized isn't inherently helpless. A truly decentralized network could freeze on a permissionless trigger, even revert only the malicious txs and nothing else. That system doesn't exist yet — or some of us are quietly building it.
Security is the product. Anonymous, decentralized, with the tech holding the rules and no single point to break — that's not an ideology. It's the only architecture this hack couldn't have touched.
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
