Triage retweeted
Finally got around to making the case for my little Kaspa miner. What do you guys think?
13
9
84
2,027
Triage retweeted
JUST IN: Kaspa surpasses Bitcoin in the percentage of supply already mined
Kaspa has reached 96.85% of its maximum supply, compared with Bitcoin’s 95.73%, meaning less than 3.2% of $KAS remains to be mined.
Kaspa has reached 96.85% of its maximum supply, compared with Bitcoin’s 95.73%, meaning less than 3.2% of $KAS remains to be mined.
24
98
514
11,567
Triage retweeted
Five years ago, a small light appeared in the crypto universe. Today, that flame is burning brighter than ever, and the real world is beginning to take notice.
What an incredible five years it’s been. From the first block to the innovations still unfolding, Kaspa continues to pment keeps advancing, adoption is growing, and new applications and opportunities continue to emerge.
This animation captures just a few of the milestones along the way. There’s far more to the story, and so much more still to come.
Congratulations to the Kaspa core team and everyone who has contributed since day one. To the builders, miners, researchers, academics, ambassadors, merchants, enterprises and the wider Kaspa community, this celebration belongs to all of you.
Happy 5th Birthday, Kaspa! 💚
Five years. Still burning. 🔥
Sound on!
#KaspaV #Kaspa5 #BlockDAG #ProofOfWork
@kaspaunchained
@kasmediadotcom
@KasMaporg
@KaspaKii
@KaspaCom
@Kaspa_Commons
“She perceives that her merchandise is profitable. Her lamp does not go out at night.” Proverbs 31:18
What an incredible five years it’s been. From the first block to the innovations still unfolding, Kaspa continues to pment keeps advancing, adoption is growing, and new applications and opportunities continue to emerge.
This animation captures just a few of the milestones along the way. There’s far more to the story, and so much more still to come.
Congratulations to the Kaspa core team and everyone who has contributed since day one. To the builders, miners, researchers, academics, ambassadors, merchants, enterprises and the wider Kaspa community, this celebration belongs to all of you.
Happy 5th Birthday, Kaspa! 💚
Five years. Still burning. 🔥
Sound on!
#KaspaV #Kaspa5 #BlockDAG #ProofOfWork
@kaspaunchained
@kasmediadotcom
@KasMaporg
@KaspaKii
@KaspaCom
@Kaspa_Commons
“She perceives that her merchandise is profitable. Her lamp does not go out at night.” Proverbs 31:18
8
56
188
3,039
Triage retweeted
🫶 Reminder your community that only Covenant ID 2c84784efe50979a5298ef0c2639b604318271053b3aaec009873e7ddc38148b is the Official $BITE KCC20, any other covenant id is a copy. kascov.io/#/mainnet/toke…
2
1
2
173
Triage retweeted
🏁💚BIG RESPECT TO TRIAGE!
@ExTriage turned down €15,000 from Bitcoin maxis to replace the Kaspa Testnet branding on his rally car with the Bitcoin logo! 💪
He chose loyalty to the Kaspa community over money!
Watch the clip below
Let's show him some love and support the Kaspa Coffee & 💸 Revolut donation links below 👇
#Kaspa #KAS kaspa:native
@ExTriage turned down €15,000 from Bitcoin maxis to replace the Kaspa Testnet branding on his rally car with the Bitcoin logo! 💪
He chose loyalty to the Kaspa community over money!
Watch the clip below
Let's show him some love and support the Kaspa Coffee & 💸 Revolut donation links below 👇
#Kaspa #KAS kaspa:native
8
61
258
3,135
Triage retweeted
KASPA Rally Car EXCLUSIVE! 🏁 Triage's Latest Updates & Full Walkaround | EP38 x.com/i/broadcasts/2…
0
8
27
541
Triage retweeted
live now
@Cryptopumpzzzz @ExTriage
#kaspa banter.
give some marketing ideas to help <3
:" we try something to evolve the community".
@Cryptopumpzzzz @ExTriage
#kaspa banter.
give some marketing ideas to help <3
:" we try something to evolve the community".
0
3
6
226
Triage retweeted
🏁🚀 KASPA GOES RALLYING!
🎙️ Blockchain Banter EP38 – LIVE TONIGHT!
Tune into Myself & @qu1ck_crypt0 as we are joined by @ExTriage for the latest updates on the kaspa:native Rally Car! 🏎️💨
🔥 Rally updates, an exclusive car walkaround, and plenty of Rally updates
⏰ 9 PM UK/Ik in the comments! 👇
🎙️ Blockchain Banter EP38 – LIVE TONIGHT!
Tune into Myself & @qu1ck_crypt0 as we are joined by @ExTriage for the latest updates on the kaspa:native Rally Car! 🏎️💨
🔥 Rally updates, an exclusive car walkaround, and plenty of Rally updates
⏰ 9 PM UK/Ik in the comments! 👇
1
9
40
756
Triage retweeted
V2 Dagger 🗡️
Looks and runs amazing
Give your feedback 👇🏻
Looks and runs amazing
Give your feedback 👇🏻
⚔️ SAME DAGGER, JUST SHARPER.
New look. Same blade. We sharpened the brand — cleaner, faster, clearer — but under the hood it’s the same Dagger thousands of you already trade on every day.
If you’re on Kaspa KCC-20, this is your command centre. 🔪
🌐 EVERY VENUE, ONE PLACE
, Braid & KasSeal from a single bot — with KForge, KasForge, KCom & Zealous rolling in. One wallet, every venue, always growing.
🔁 DAGSWAP — swap any token on any venue straight into any other, in one move. First of its kind on KCC-20.
⚡ THE FULL DESK
• 🏹 Sniper with safety filters
• 👥 Copy-trade + trader leaderboard
• 📈 DCA + limit orders
• 🛰 Wallet tracking + whale alerts
• 📊 Live charts + P&L without selling
• 🔎 Paste any CA → instant buy
• 🚀 Launch your own token across venues
• 🔒 DagLock token locks
• 📤 Withdraw KAS or any token, anytime
• 🖥 Mini App + Full trader web terminal with smart-money signals
🔐 YOUR SEED, YOUR EXIT
Your wallet comes with a seed phrase that’s yours — back it up, move it to Kasware or Kastle whenever you like. Keys are stored encrypted with an optional PIN, and you can withdraw everything, any time. You’re never locked in.
🔪 One bot. Every KCC-20 venue. Built for Kaspa, by people who actually use it.
Same Dagger.
Just sharper.
0
4
15
468
Triage retweeted
Welcome to the start of our new "No more Buts" series.
In sales the best salesperson is the one that can understand hesitation and objections and let people keep asking the "but" questions until there are no "buts" left to ask. At that point it becomes a no brainer to try e are dedicating a series to pre-empt all of your "But" questions and answer them for you!
“But it’s crypto, my team doesn’t want to set up wallets, buy tokens, or learn a new system just to chat.”
Fair. That’s exactly why Komms keeps all of that in the background. You sign in with a passkey (like your phone or laptop already does). No wallet knowledge needed. No KAS or TAO to buy. Plans are paid by card like any other software.
The Kaspa/Bittensor side just handles identity, ordering, and incentives so the network stays independent.
Your team uses it like Slack or Discord. The crypto stays out of the way
$TAO $KAS
In sales the best salesperson is the one that can understand hesitation and objections and let people keep asking the "but" questions until there are no "buts" left to ask. At that point it becomes a no brainer to try e are dedicating a series to pre-empt all of your "But" questions and answer them for you!
“But it’s crypto, my team doesn’t want to set up wallets, buy tokens, or learn a new system just to chat.”
Fair. That’s exactly why Komms keeps all of that in the background. You sign in with a passkey (like your phone or laptop already does). No wallet knowledge needed. No KAS or TAO to buy. Plans are paid by card like any other software.
The Kaspa/Bittensor side just handles identity, ordering, and incentives so the network stays independent.
Your team uses it like Slack or Discord. The crypto stays out of the way
$TAO $KAS
0
13
31
963
Triage retweeted
🚨 NACHO MIGRATION IS LIVE 🚨
KRC-20 → KCC-20 on Kaspa L1.
This is it, Nacho Nation.
The move we’ve been preparing for.
🔗 Migrate here:
katbridge.com/migrate
✅ Official KCC-20 Covenant ID:
41d44970ba6307bcec418f677fd253778d0ffa47750d179dff647061aa6c0d40
Verify on Wno8Fqpx
⏰ Migration deadline: January 31, 2027
After this date, unmigrated tokens will not be eligible.
⚠️ BEFORE YOU MIGRATE:
→ Only use katbridge.com/migrate
→ Only this Covenant ID is official
→ Double check everything
→ If unsure, ask in KAT Discord first
→ Nobody official will ever DM you
→ There is no second token, no airdrop, no shortcut
This is the ONLY path.
Verify it. Use it. Protect yourself.
Full migration guide:
nachothekat.xyz/nacho/migration
Why the migration:
nachothekat.xyz/nacho/october-…
$NACHO on $KAS L1.
Home where it belongs 🐾
KRC-20 → KCC-20 on Kaspa L1.
This is it, Nacho Nation.
The move we’ve been preparing for.
🔗 Migrate here:
katbridge.com/migrate
✅ Official KCC-20 Covenant ID:
41d44970ba6307bcec418f677fd253778d0ffa47750d179dff647061aa6c0d40
Verify on Wno8Fqpx
⏰ Migration deadline: January 31, 2027
After this date, unmigrated tokens will not be eligible.
⚠️ BEFORE YOU MIGRATE:
→ Only use katbridge.com/migrate
→ Only this Covenant ID is official
→ Double check everything
→ If unsure, ask in KAT Discord first
→ Nobody official will ever DM you
→ There is no second token, no airdrop, no shortcut
This is the ONLY path.
Verify it. Use it. Protect yourself.
Full migration guide:
nachothekat.xyz/nacho/migration
Why the migration:
nachothekat.xyz/nacho/october-…
$NACHO on $KAS L1.
Home where it belongs 🐾
52
91
259
23,311
GM Kaspians 🏁
lovistin shared my story on Instagram . We’re only just getting started… 📷🏁
instagram.com/stories/lovist…
lovistin shared my story on Instagram . We’re only just getting started… 📷🏁
instagram.com/stories/lovist…
0
12
54
655
Triage retweeted
I really didn’t know that @GoonBoyCrypto is the mastermind behind @daggertradebot that gives me even more trust to use even more and explore all the features 💪
3
3
14
416
Triage retweeted
KRON is now a DEX that can import any KCC-20 token. • Deploy a KCC-20 standard token • Pool & trade KCC-20 tokens launched outside KRON.
$KAS
$KAS
2
15
65
1,472
Triage retweeted
The $6.3 billion Binance hack exposes a fundamental weakness in cryptocurrency custody: when security depends entirely on controlling signing infrastructure, compromising that infrastructure can compromise everything.
Attackers exploited Binance's withdrawal systems, moving e blockchains in approximately 20 minutes.
This is precisely where Kaspa's covenant architecture becomes relevant.
Through KIP-17, Kaspa enables programmable spending restrictions enforced directly by network consensus. Funds can be constrained by predefined withdrawal limits, destination restrictions, timelocks, and multisignature requirements.
Even if an attacker compromises an authorized signing key, properly constructed covenants can prevent transactions that violate those restrictions.
The distinction is significant.
Rather than trusting an exchange's internal security systems to enforce every withdrawal policy, Kaspa allows certain protections to become consensus-enforced conditions of ownership.
This doesn't make Kaspa immune to hacks. Vulnerable applications, compromised keys, and poorly designed covenants remain risks.
But it fundamentally changes the security model.
The future of digital property rights depends on making unauthorized transfers technically impossible, not merely operationally difficult.
Attackers exploited Binance's withdrawal systems, moving e blockchains in approximately 20 minutes.
This is precisely where Kaspa's covenant architecture becomes relevant.
Through KIP-17, Kaspa enables programmable spending restrictions enforced directly by network consensus. Funds can be constrained by predefined withdrawal limits, destination restrictions, timelocks, and multisignature requirements.
Even if an attacker compromises an authorized signing key, properly constructed covenants can prevent transactions that violate those restrictions.
The distinction is significant.
Rather than trusting an exchange's internal security systems to enforce every withdrawal policy, Kaspa allows certain protections to become consensus-enforced conditions of ownership.
This doesn't make Kaspa immune to hacks. Vulnerable applications, compromised keys, and poorly designed covenants remain risks.
But it fundamentally changes the security model.
The future of digital property rights depends on making unauthorized transfers technically impossible, not merely operationally difficult.
9
52
132
3,144
Triage retweeted
🚨🚨Yesterday one signature moved ~$6.3B out of #Binance in about 20 minutes.
Biggest crypto hack in history. ~4× the #Bybit heist
Here’s why the same breach of a @kaspaunchained L1 covenant vault would have left the attacker with almost nothing. 🧵
2 - What actually happened lysis):
→ Compromised DevOps engineer’s laptop
→ Attacker reached a service container that could make Binance’s hot-wallet signing system sign
→ No private key “leaked.” The signer just signed what it was told.
3 - On Ethereum the attacker didn’t even need to drain manually.
They sprayed 50 EIP-7702 authorisations at hot wallet “Binance 14” in one tx (nonces 18,914,775–824). One matched the live nonce.
That single signature handed the wallet to an attacker-deployed sweeper. ~3 minutes later: 167k ETH + 1.6B USDT + dozens of other tokens gone.
4 - Then the same signing system signed plain transfers on BTC, TRON, XRP, SOL, Arbitrum, Base, Avalanche, Optimism, Polygon.
10 chains. Different key types. Same blast radius.
Fee to move billions: under a dollar.
5 - The root problem isn’t Ethereum or Binance’s engineers.
It’s the model: in a hot wallet, the key is total authority.
Every “withdrawal limit,” every “approval tier,” every “wait 24h” lives on a server. If you own the signer, you own the policy.
6 - Now the Kaspa side.
Since the Toccata hard fork (30 June 2026), Kaspa L1 has covenants: a UTXO that inspects the transaction spending it (amounts, outputs, locktime, DAA score, its own successor).
The rules live inside the coins, not on a server. Enforced by every node.
7 - A covenant vault (written in Silverscript) can look like this:
→ Max X KAS per withdrawal
→ Only to a pre-fixed payout address
→ Only after N blocks / DAA score since last withdrawal
→ Recovery/alarm key can cancel or sweep to cold at any time
→ Output must be the same vault with updated state
8 - Replay the Binance breach against that vault.
Attacker steals the hot key. Signs a withdrawal. Signature is valid.
So what. The covenant checks the tx:
• Over the cap → invalid
• Wrong address → invalid
• Too soon → invalid
They get one capped tranche. Then the chain itself says “wait.”
9 - During that wait, your recovery key (cold, different machine, different person) sweeps everything to safety.
The attacker can’t stop it. The attacker can’t speed up the clock.
Because the clock isn’t a clock. It’s DAA score — Kaspa’s PoW block counter at ~10 blocks/sec.
10 - To skip the delay you’d have to mine blocks faster than the entire network.
Not phish them. Not bribe them. Out-hash the world.
That’s the only way to move the time forward. A pure PoW BlockDAG makes rewriting history computationally infeasible.
11 - And the 7702 trick? Doesn’t exist here.
There’s no opcode that lets a key hand an address over to arbitrary code. A UTXO’s spend rule is fixed the moment it’s created. You can spend it within the rules or not at all.
A stolen key can’t rewrite what the coins are allowed to do.
12 - Nothing described is theoretical.
KIP-10 and KIP-17 introspection are live on mainnet. Silverscript 1.0 shipped (Sept 2026). Covenant vaults with capped withdrawals + recovery paths are already deployed and verifiable by covenant ID.
This is the first L1 where “smart vault” means consensus-enforced, PoW-secured, UTXO-native.
13 - Binance will cover the losses. Stablecoin issuers froze billions. North Korea 🇰🇵 gets the rest.
Next time, ask the exchange holding your coins:
Is your withdrawal policy a server config, or does every node on a proof-of-work chain enforce it?
Only one of those survives a compromised laptop.
#Kaspa #KAS #Covenants #NotYourKeys
Biggest crypto hack in history. ~4× the #Bybit heist
Here’s why the same breach of a @kaspaunchained L1 covenant vault would have left the attacker with almost nothing. 🧵
2 - What actually happened lysis):
→ Compromised DevOps engineer’s laptop
→ Attacker reached a service container that could make Binance’s hot-wallet signing system sign
→ No private key “leaked.” The signer just signed what it was told.
3 - On Ethereum the attacker didn’t even need to drain manually.
They sprayed 50 EIP-7702 authorisations at hot wallet “Binance 14” in one tx (nonces 18,914,775–824). One matched the live nonce.
That single signature handed the wallet to an attacker-deployed sweeper. ~3 minutes later: 167k ETH + 1.6B USDT + dozens of other tokens gone.
4 - Then the same signing system signed plain transfers on BTC, TRON, XRP, SOL, Arbitrum, Base, Avalanche, Optimism, Polygon.
10 chains. Different key types. Same blast radius.
Fee to move billions: under a dollar.
5 - The root problem isn’t Ethereum or Binance’s engineers.
It’s the model: in a hot wallet, the key is total authority.
Every “withdrawal limit,” every “approval tier,” every “wait 24h” lives on a server. If you own the signer, you own the policy.
6 - Now the Kaspa side.
Since the Toccata hard fork (30 June 2026), Kaspa L1 has covenants: a UTXO that inspects the transaction spending it (amounts, outputs, locktime, DAA score, its own successor).
The rules live inside the coins, not on a server. Enforced by every node.
7 - A covenant vault (written in Silverscript) can look like this:
→ Max X KAS per withdrawal
→ Only to a pre-fixed payout address
→ Only after N blocks / DAA score since last withdrawal
→ Recovery/alarm key can cancel or sweep to cold at any time
→ Output must be the same vault with updated state
8 - Replay the Binance breach against that vault.
Attacker steals the hot key. Signs a withdrawal. Signature is valid.
So what. The covenant checks the tx:
• Over the cap → invalid
• Wrong address → invalid
• Too soon → invalid
They get one capped tranche. Then the chain itself says “wait.”
9 - During that wait, your recovery key (cold, different machine, different person) sweeps everything to safety.
The attacker can’t stop it. The attacker can’t speed up the clock.
Because the clock isn’t a clock. It’s DAA score — Kaspa’s PoW block counter at ~10 blocks/sec.
10 - To skip the delay you’d have to mine blocks faster than the entire network.
Not phish them. Not bribe them. Out-hash the world.
That’s the only way to move the time forward. A pure PoW BlockDAG makes rewriting history computationally infeasible.
11 - And the 7702 trick? Doesn’t exist here.
There’s no opcode that lets a key hand an address over to arbitrary code. A UTXO’s spend rule is fixed the moment it’s created. You can spend it within the rules or not at all.
A stolen key can’t rewrite what the coins are allowed to do.
12 - Nothing described is theoretical.
KIP-10 and KIP-17 introspection are live on mainnet. Silverscript 1.0 shipped (Sept 2026). Covenant vaults with capped withdrawals + recovery paths are already deployed and verifiable by covenant ID.
This is the first L1 where “smart vault” means consensus-enforced, PoW-secured, UTXO-native.
13 - Binance will cover the losses. Stablecoin issuers froze billions. North Korea 🇰🇵 gets the rest.
Next time, ask the exchange holding your coins:
Is your withdrawal policy a server config, or does every node on a proof-of-work chain enforce it?
Only one of those survives a compromised laptop.
#Kaspa #KAS #Covenants #NotYourKeys
8
38
108
3,185