Hyperlane is back on Kat Bridge, and so is KAS ↔ iKAS. katbridge.com The kaspa:native route now uses the same Igra incident registry. Before a withdrawal is paid, we check the account against that list. Listed addresses are blocked. We also set a fresh cutoff on Kaspa and Igra so nothing from before this reopen can be paid again. KRC-20 routes stay closed. Those contracts remain paused. Migration tooling onto the KCC20 standard is being finalized, and that is the path forward for those tokens. If a transfer is flagged or a listing looks wrong, open a Support Ticket in KAT Discord and/or reach out to the @Igra_Labs team as described below.

Update on the KRC20 incident: The full revert and verification processes are proceeding smoothly; based on current progress, completion will still take several days. Once finished, the public API will be reopened, and further investigations will be conducted into the chains of transactions linked to the exploit.

KAT Bridge KRC20, KAS/iKAS, Hyperlane Bridging has been paused and taken offline while investigation proceeds. @KastleWallet @KaspagentAI and any other integrated products, Please disable your integrations as well

@KastleWallet When are you going to start supporting @KronTechnology ? Here is the SDK's to make it super easy!! github.com/ShawnPearce/kns-s… github.com/KronSDK/kron-sdk We even have had a 3rd party security audit by @Hashlock_ Can you explain why this has not happened yet?

1/12 Introducing dotk 🥳, a name service built different - unique, trustless, decentralized - enforced by covenants. Names are a binding of name (supertypo.k) to an address (kaspa:...). dotk names are cheap, and I have a whole page dedicated to the *why* it exists. Highlights 👇

🏰 Kastle v1.28.0/v1.28.1 is rolling out Earlier this month, some of you experienced delays bridging iKAS back to KAS. We know exactly how stressful it is when a transfer doesn't arrive when you expect it to — we're sorry for that experience, and genuinely grateful for your patience while we got to the bottom of it. The important part, confirmed: transfers were delayed, never lost. What's in v1.28.1: 🛡️ A new safety check on bridge transfers. Kastle now verifies the bridge can actually pay out your transfer before it goes through. If capacity is too low, the transfer is stopped with a clear message — instead of ending up in a queue you can't see. ✅ Honest status messages. Your transfer now says "Bridge submitted. Processing…" until funds actually move — and if something goes wrong, you get a specific reason, not a generic error. ✅ Accurate fee preview. The fee you see is exactly the fee that settles. ✅ Fixed the bridge tab icon. Yes, we saw it too 👀 Behind the scenes: we now monitor bridge liquidity 24/7. Our systems track the bridge's payout capacity in real time and alert the team within minutes if it runs low — so we act before you're affected, not after. A huge thank-you to the @Kaspa_KAT team for working side by side with us through the investigation — their openness about how the bridge works under the hood is what made these fixes possible. This is what building an ecosystem together looks like. What's next: a detailed Activity page is in the works. You'll follow your bridge transfers live — submitted, confirmed, completed — and in the rare case a transfer can't be processed in time, you'll withdraw your full amount, fee included, straight back to your wallet. No support tickets, no waiting in the dark. We ship infrastructure before hype. Thanks for riding with us, The Kastle Team. 🛡️