JimJim retweeted
We're incredibly honored to announce that #CrimsonDesert has won the Grand Prize and 7 additional awards at the 2026 #KoreaGameAwards! 🏆⚔️
🏆 Grand Prize
🏆 Global Game Award
🏆 Technology Creation Award (Graphics, Character, Game Design/Scenario, Sound)
🏆 Best Developer Award
🏆 Popular Voice Actor Award
From the bottom of our hearts, thank you, Greymanes. None of this would be possible without your continued love and support!
JimJim retweeted
GTA 6 IS FINALLY HERE
And on the day of its release, you can now gain exposure to its parent company, Take-Two Interactive ($TTWO), through Silk Suite
We've just created the first-ever Take-Two liquidity pool on @hedera:
🔸️ $SILK / $TTWO 💧
But this is about more than just making $TTWO tradable.
For the first time, projects and community members in $HBAR, can provide liquidity to tokenised stock pools using their favourite HTS tokens and trade natively on the Hashgraph with 0% slippage
We've seeded the $SILK/$TTWO pool with initial liquidity, laying the foundation for a new trading pair and expanding liquidity opportunities across the Hedera ecosystem
Here's where it gets interesting:
Silk Suite's APY is dynamic. The more liquidity provided and the more trading activity generated around a pool, the greater the potential monthly LP rewards
More participation. More activity. More rewards for liquidity providers and communities
We're opening up a new liquidity opportunity for the entire Hedera ecosystem
(Lets hope Lucia approves 🤫)
JimJim retweeted
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.

ALT "Eight scam checks. On your device." Transactions from apps inside HSuite Wallet, and the transaction history, are screened locally; high-risk items need an explicit acknowledgement. Checklist of detectors: address poisoning, dust delivery, impersonation, Unicode obfuscation, credential solicitation, embedded URLs, reward bait, unknown counterparty.
JimJim retweeted
A major upgrade to the Silk Suite DEX! 🚀
You can now create liquidity pools pairing $HBAR with ANY token, or pair ANY token with ANY token of your choice within the @hedera DeFi ecosystem
🔸️ $HBAR/HTS
🔸️ HTS/HTS
Our latest update unlocks more routing possibilities, removing the previous limitations and giving users greater freedom to create pools across the Silk ecosystem
Building. Never. Stops. 🪜
THE BONZO HACK: HEDERA, WE NEED TO TALK.
Millions of dollars in community funds were lost during the Bonzo exploit. But what happened afterward may have done just as much damage to the trust people had in the Hedera ecosystem.
I want to lay out why so many of us are disappointed, frustrated, and ultimately walking away.
1. From FULL RECOVERY to a fraction of what we lost.
Initially, affected users were given the expectation that a full recovery was the objective.
That expectation eventually became a proposed USDC recovery based on exploit-time prices.
Then came the loan netting calculations, deductions, and further reductions. Some affected users were left facing recovery figures as low as approximately 56% of their USDC-calculated value.
We went from expecting to be made whole to potentially absorbing a loss of up to 44%.
2. HBARX and other assets sold off for USDC.
Our HBARX and other assets were sold off and converted into USDC as part of the recovery process.
For HBAR holders, this is especially painful.
We didn’t enter the Hedera ecosystem because we wanted to eventually cash out into USDC. We wanted to own HBAR, participate in the ecosystem, lend, borrow, stake, and build wealth within Hedera.
There have been no meaningful repayment options offered to bridge the losses or give affected users a path to recover over time.
Why couldn’t there be a structured repayment option? Why couldn’t there be a path that allowed users to remain invested in Hedera?
3. The white-hat recovery situation.
The handling of the white-hat recovery has also raised serious concerns.
From the perspective of affected users, the white hat was put in a position where giving up their recovery amount in exchange for a 10% fee became part of the arrangement for recovering approximately $1 million worth of tokens.
The circumstances surrounding that arrangement deserve transparency.
A recovery effort that saves significant community assets should not leave questions about whether the people involved were treated fairly or whether the terms were reasonable.
4. The Hedera Foundation and the missing Phase 2.
This is where I believe the bigger picture has been overlooked.
The Hedera Foundation has billions of HBAR in its treasury.
We weren’t asking the Foundation to buy us out or make us millionaires.
We wanted our HBAR back.
We wanted to remain in the ecosystem. We wanted Bonzo to survive. We wanted the only lending protocol on Hedera to have a future.
Instead, our understanding is that Foundation-related funds were settled separately, while affected users were left with no firm guarantee of a Phase 2 to address the remaining deficit of up to 44%.
We are now looking at an approximately $1.1 million USDC shortfall just to complete the proposed net recovery amount.
And the capital that could have helped Bonzo survive and rebuild is no longer there.
What happens to Bonzo now?
What happens to Hedera DeFi when the community that supported it no longer has the capital or confidence to participate?
5. The damage to Hedera goes beyond Bonzo.
A significant portion of the community has already left, and many who remain have been left with a bitter taste.
There isn’t another comparable lending protocol on Hedera for users to simply move to.
Hedera has positioned itself as the trust layer of the internet.
But how can we continue trusting an ecosystem when the people who took the risk, supplied liquidity, and helped build its DeFi infrastructure feel abandoned when things went wrong?
Trust isn’t built through marketing. It’s built through actions when things get difficult.
6. There is STILL time to make this right.
JimJim retweeted
The sea has always ruled us. For centuries we've been slaves on a ship, registered at birth like cargo, following a current we call currency, and today that ship has to sink so we'll beg to board the next one. The old financial system goes under while the only thing they launch is a rocket, the symbol of the digital money that will own you instead of the other way around. Nothing is organic, nothing is random, every sinking is a ritual planned long before us. Learn to read the code. Watch my series See in the Dark at realityrevolt.com
JimJim retweeted
🚨 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.
PSA @bonzo_finance on @hedera isn't treating the white hat who saved $1M+ fairly. They advertised a 10% bounty, yet with redemptions open, they’ve blacklisted the white hat's wallet from redeeming ~$20k of their own funds, citing a poorly worded rescue agreement. Not a good look.
JimJim retweeted
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 👇
docs.hsuite.network/start-he…
Testnet is live too, but it isn’t open to developers yet. It stays closed until the security audit is complete.
JimJim retweeted
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.

ALT "Multisig is a channel type." hsc:party channels coordinate M-of-N signing across devices on Hedera threshold keys and XRPL multi-signing; every signer approves on their own device. Diagram: three phones connected to an hsc:party hub; signers A and B have approved, signer C is pending; the hub shows 2 of 3 reached.


















