GIO-CT5555 𐤊 retweeted
At Komms, we compete with the major centralized workplace platforms by building on existing incentivized decentralized networks such as Kaspa and Bittensor.
This lets us avoid the substantial costs of operating large-scale data centers.
We then pass those huge savings on to our customers.
Check out the huge savings we are talking about here on our calculator and see how much we could potentially save your business if you switch to Komms:
komms.app/business.html
$TAO $KAS
GIO-CT5555 𐤊 retweeted
Some days you chase the spotlight.
Some days the spotlight finds you.
Happy #BlackCatDay to the OGs.
🐈⬛ $NACHO $KAS
GIO-CT5555 𐤊 retweeted
i’ll do everything in my power on the technical side to help this initiative move forward and navigate any protocol-level obstacles along the way.
on a personal note, Alex has a rare mix of technical depth, bizdev talent and deep Kaspa knowledge. i honestly can’t think of anyone better suited to lead it, and i really appreciate him taking this on
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
GIO-CT5555 𐤊 retweeted
i’ve spent the last few months bringing native Kaspa payments to x402.
tldr: x402 is an open, chain agnostic payment protocol built around the long existing HTTP 402 code. kaspa-x402 intends to bring native KAS into that shared standard.
i keep seeing people use “x402” to mean anything built around the HTTP 402 response code. HTTP 402 has existed for decades, and anyone can hang their own payment flow off it.
x402 refers to a specific open protocol built on top of that code. it standardises how a server requests payment, how a client authorises it, and how the payment is verified and settled.
it can be used for paid APIs, AI agents buying data or tools, and MCP servers charging per call. kaspa-x402 adds native KAS to the existing x402 v2 flow.
there are two payment paths:
- exact for a normal one off KAS payment, with an optional KIP10 additive mode
- batch-settlement for small or repeated payments, where the client funds a SilverScript covenant once and signs a fixed charge voucher for each request
the longer term goal is to contribute the Kaspa support upstream into the wider x402 project, so Kaspa works within the same standard being adopted elsewhere.
i’m looking for humans and agents to go through it deeply before the final v1 release. read the code, build against it, test the assumptions and try to break it. if you find something, pls let me know.
code: github.com/elldeeone/kaspa-x…
upstream x402: github.com/x402-foundation/x…
docs: kaspa-x402.org
TN gateway: demo.kaspa-x402.org
discussion: kas-smiths.org/t/kaspa-x402-…
GIO-CT5555 𐤊 retweeted
Something potentially important is being built quietly on Kaspa.
AI agents can now be connected to KAS-payable services through MCP.
The interesting part?
The agent itself can:
→ discover a service
→ receive an HTTP 402
→ pay in KAS
→ execute the request
→ receive the result
No account. No API key. No human approving every payment.
There is even a newly released kaspa-x402 library where an AI inference request returns both the model output and the Kaspa TXID that paid for it.
Think about the flow:
AI Agent → HTTP 402 → KAS → API/compute → result
This does NOT mean Kaspa x402 is production-ready or officially standardized.
The reference implementation is still Alpha/Testnet-10 and explicitly says mainnet remains blocked pending further hardening.
But the direction is worth watching.
The future demand for blockspace may not come only from humans sending money.
It may come from machines paying machines.
And KAS is already being experimented with as that money.
$KAS
Sources:
• github.com/Kali123411/kaspa-…
• npmjs.com/package/kaspa-x402
• kaspa-x402.org
GIO-CT5555 𐤊 retweeted
🔥 BURN nacho-the-kat:native / NFT RAFFLE 🎟️
Four NFTs: blue, yellow, red, rainbow.
Simple rules:
Your wallet receives one (virtual) ticket for every 250K nacho-the-kat:native donated to the address(es) below. For example, 1M NACHO donation gets 4 tickets.
All proceeds will be burned! 🔥
$KAS Address (KAT controlled): kaspa.stream/addresses/kaspa… kaspa:qqch24lhsn5md7u57lgqz30kt0euqk7uwr0csrvpletxdsaa8fp7cdgxqgzfu
EVM Address (KAT controlled): explorer.igralabs.com/addres… 0x123ddd6EbFAFB687FEe659A9f2F1d25298C965e8 explorer.kasplex.org/address…
Raffle lasts one week. 🐈⬛
Random winner for each NFT.
Maximum 250 tickets for sale.
Drawing from purchased tickets.
⚠️ To enter raffle, do not donate from an exchange. Send to your own wallet first, then donate.
As well, feel free to donate Nacho Kat NFTs to either address to be sold in an upcoming auction that burns all nacho-the-kat:native proceeds. Already 230M to be burned!
Blue (9103) - kaspa.com/nft/collections/NA…
Yellow (9089) - kaspa.com/nft/collections/NA…
Red (7596) - kaspa.com/nft/collections/NA…
Rainbow (8003) - kaspa.com/nft/collections/NA…
GIO-CT5555 𐤊 retweeted
Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.
The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.
The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.
Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.
Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.
Up until that point, this account will share the plans, details and progress of the work as it develops.
GIO-CT5555 𐤊 retweeted
here is the only discussion i'm aware of: kas-smiths.org/t/kcc721-prop…, and i see you already took part of it.
i believe we can re-use kcc-20 as a base, with kcc-23 and minor adjustments in order to get the desired result
GIO-CT5555 𐤊 retweeted
THE TIME IS NOW ⏳🏁
Kaspians, help us get this car onto more people’s screens! 💚
We have 4 days left, we’re at 47%, and 39 incredible backers have already helped us get this far.
After months of building and sharing every step, let’s share this next step together. Repost this, send it to a friend, or share it with a community that loves motorsport, Kaspa, or seeing an idea become something real.
Somewhere beyond our own timelines are people who would love this project and might want to contribute they just haven’t seen it yet. Your share could be how they find us.
To everyone who has supported the build, contributed or helped spread the word: thank you from the bottom of my heart. ❤️
Let’s take Kaspa from our screens to the starting line. 🏁
🔗 staghunt.app/bounties/bnty-m…
🌐 kasparally.com
#Kaspa #KaspaRally
GIO-CT5555 𐤊 retweeted
They declared $KAS dead.
The network didn’t get the memo🗿
“Kaspa is finished.”
“It’ll never come back.”
Meanwhile the chain keeps running.
Past 7 days:
$KAS — 5.8M transactions
$BTC — 4.9M
$LTC — 1.25M
This is happening while $KAS is down, attention has shifted, and the timeline is flooded with new launches fighting for the same liquidity.
Markets can ignore a project for months, that doesn’t mean the builders stopped or the network stopped operating.
When sentiment is this low, it’s fair to ask whether price is reflecting fundamentals or simply the lack of attention.
Transaction counts alone won’t take $KAS into the top 10. But writing it off while the network keeps putting up these numbers deserves a second look.
$KAS
GIO-CT5555 𐤊 retweeted
📢 nacho-the-kat:native Incident Recovery & KCC20 Migration: Where We Stand
Original KRC20 supply: 287B
Migration snapshot supply: 330B
What happened on Sept 20:
A vulnerability in the KRC-20 standard (Kasplex) was exploited to forge ~49B NACHO from the layer 1 (L1) vault, inflating the total supply with unbacked layer 2 mints.
Incident response:
→ Paused KatBridge the same day
→ 6B+ nacho-the-kat:native voluntarily burned by holders working with us (legends forever)
→ Burned all remaining nacho-the-kat:native in the L1 vault to lock in the final number.
🔗 Vault Burn TX: kaspa.stream/transactions/9f…
The L1 vault now holds zero NACHO, and every token is accounted for.
Next step, finalize the KCC20 migration tool that any project that was supported by KatBridge will be able to use.
Then, deploy the nacho-the-kat:native KCC20 token and begin migration from KRC20 NACHO or ERC20 NACHO on Kasplex or Igra.
The burn has only just begun.
Supply keeps going down from here:
🔥 → Voluntary burns during the KCC20 migration.
🔥 → Migration fees used to buy and burn.
🔥 → Unmigrated tokens burned after the window closes.
Every token burned, even on KCC20, reduces all calculated supply metrics including the max supply, total supply, and circulating supply. These are the standard supply metrics that are verified across crypto dashboards that we will keep updated, so that you can see the direct impact of each burn!
⚠️ There is no official KCC20 NACHO token yet. Anything claiming to be one is a scam. The official migration will be announced only through our verified channels.
Stay nacho-the-kat:native. 🐾
GIO-CT5555 𐤊 retweeted
Hey Kastlers 🏰
Due to our mistake last week, we had to disable the bridge feature again on mobile (the extension is live). Our UI still allowed bridging KRC20 to Igra while this route was disabled on @Kaspa_KAT, which we use behind the scenes as a provider.
Some of you tried to bridge KRC20 and saw your tokens disappear. This was terrible and won’t happen again. To prevent it from spreading further, last weekend we disabled the bridge again.
Now all the problems have been fixed. Thanks to the help of the formidable @Kaspa_KAT team, the best partners possible in this world, the stuck funds have been returned to the users. The new mobile release is about to bring the bridge back without the KRC20 route, plus a new feature.
If you were affected, please check your funds now. If you see any inconsistency, text us in our Telegram channel and we will look into it right away.
Thanks all for your understanding. 🛡️
Hey Kastlers! The bridge is finally back on Kastle, both mobile and for the first time in the browser extension as well!
For the first transfer, always be careful and try to send a small amount first. Wait for it to arrive. Then send the full amount.
The KRC-20 routes stay closed for now. Those contracts are still paused while KAT finalizes the migration to the KCC20 standard.
If you see something odd come and tell us in our Telegram group. 🛡️
GIO-CT5555 𐤊 retweeted
📊 $NACHO Nation — Migration Window Vote Is Open 🗳️
$NACHO (every variant: KRC20, Igra L2, Kasplex L2) is moving soon to KCC-20 on Kaspa L1.
All holders must migrate within the set timeframe. Once it closes, migration to KCC-20 will no longer be available.
How long should the migration window be?
🟢 30 days
🟡 60 days
🔵 90 days
⚪ Other: Tell the community your opinion in 💬 general-chat on Discord.
Every vote counts.
Every opinion counts.
Make it heard.
Let's go $KAS Family!
⏰ Voting closes 26th October, 8 PM UTC.
🗳️ Vote on Discord. Link 👇
discord.com/channels/1243729…
🤖 Made with AI
