Node 𐤊 retweeted
Replying to @pubity
The demo was 100% for show, the thing wasn't even a tesla its a hollow plastic frame with a tesla wrapper
Node 𐤊 retweeted
Accept kaspa:native anywhere, anytime. ⚡
KasRegister turns your phone or browser into a high-speed Kaspa POS terminal.
🛒 Fast checkout
📦 Easy setup
📊 Live tracking
🔗 kasregister.vercel.app/
#Kaspa #KasRegister
Node 𐤊 retweeted
KaspaCom in your pocket ⚡️
With the latest update for the Android app of Kaspire Wallet you now have access to the marketplace by @KaspaCom in your mobile app. Trade KRC721, KRC20 and KNS wherever you are.
You can find the marketplace directly from K-Agora. Trade decentralized KRC721 NFT, KRC20 token and KNS name orders without leaving Kaspire. Keep KaspaCom orders, commissions and purchase history separate from Kaspire's own marketplaces. Search and filter collections, inspect traits and sort NFTs by price or rarity rank. Browse ranked collections and tokens in batches.
The full KCOM experience is here!
🤖 Made with AI
Node 𐤊 retweeted
kcc20 is about making it easier for wallets and apps to work with tokens on kaspa.
it proposes a shared way to describe who owns the tokens, how many they hold and how transfers work. it gives builders a common format to follow when their wallets and apps read token information or prepare transfers.
kcc20 is now in last call, its final review before becoming a finalized standard.
Node 𐤊 retweeted
According to CoinMarketCap, there are 63.58 million cryptocurrencies, yet no project comes close to what Kaspa is building. This project exists, and people are sleeping on it.
Faces will be melted. Join the revolution. kaspa:native
Node 𐤊 retweeted
I asked ChatGPT to compare Kaspa with the top 10 for speed, scalability and the evolution of cryto. These are the results. Unbelievable. ⚡
#Crypto #blockchain #nextbitcoin #memecoin #finance
Node 𐤊 retweeted
KaspaCom Markets is coming to Kaspa mainnet
KaspaCom Markets is bringing KCC20 order book trading natively to Kaspa L1, fully decentralized and self-custodial.
Limit Orders. Market Orders. Trade on your terms.
The KCC20 standard is almost ready. So are we. Mainnet is next. ⚡️
Node 𐤊 retweeted
The #kaspa arcade is open!
A tribute to the kaspa devs, ecosystem, and community.
Soft launch, free to play in October.
Follow us for updates on new games and news about the #kaspaarcade!
kaspaarcade.com
kaspa:native
Node 𐤊 retweeted
based apps can use kaspa to order user transactions while maintaining balances and other shared app data off-chain.
the app processes that activity and produces a proof that the recorded instructions changed its state according to its rules.
an L1 covenant checks the proof against kaspa’s recorded activity and validates the update.
the L1 support for this has been available since the toccata hf.
Node 𐤊 retweeted
🔥 Something nobody talks about enough...
Every time a token launches on KRON, kaspa:native is locked forever.
Not temporarily.
Not until someone withdraws it.
Forever.
That KAS effectively leaves the circulating supply.
More tokens launched → More KAS locked 🔒
More KRON adoption → More KAS locked 🔒
More ecosystem growth → More scarcity for kaspa:native ⚡
KRON isn't just building on Kaspa.
We're building in a way that directly strengthens the economics of the network we believe in.
Build on Kaspa. Lock KAS. Forever.
⚡ kron.technology
#Kaspa #KAS #KRON #Crypto
Node 𐤊 retweeted
Node upgrade: rusty-kaspa v2.1.0 complete
All KRON infrastructure is now running rusty-kaspa v2.1.0, released today (Sep 22):
• mainnet trading node (sequencer + public wss)
• mainnet indexer node
• the kaspaname.com nodes
• TN10 staging
Each node was swapped in place from a digest-pinned image and resumed from disk. No resync, no data loss. Trading paused for under a minute while the primary node came back.
What's in v2.1.0: P2P protocol 11 with chunked initial sync, wire-size limits and inbound hardening, a workspace-wide integer-overflow audit, and cleanup of the pre-Toccata code paths. What's not in it: any change to consensus rules, mass limits or script pricing. Every deployed KRON covenant behaves exactly as before, and we verified that against the full diff before touching anything.
Heads-up for anyone running their own node: v2.1.0 peers with v2.0.1, so there is no rush, but the release notes recommend upgrading and we agree.
One thing we fixed on our side during the rollout: our indexers didn't reconnect on their own after a node restart. A code fix for that is in progress so future upgrades are fully hands-off.
kaspa:native
Node 𐤊 retweeted
another week of devs building things faster than intern can explain them.
back by popular demand, another dev roundup.
1 / KCC20
@manyfest_ says the reference implementation is mostly done. a few touch-ups remain, and they want more devs to review it. getting there, but not finalized yet.
xitter.cf/manyfest_/status/21010…
2 / Argent
@IzioDev shared a template, working examples and a video walkthrough for building Kaspa L1 apps. something to actually build from after all the explaining we’ve been doing.
xitter.cf/IzioDev/status/2100178…
3 / DAGKnight
kaspa’s next consensus protocol remains in development.
github.com/kaspanet/rusty-ka…
4 / vProgs
@Max143672 has been busy. intern is doing his best to keep up.
github.com/kaspanet/vprogs/p…
5 / x402
@elldeeone released a test release for letting apps and AI agents pay for API requests in KAS. available to try on tn10.
xitter.cf/elldeeone/status/20993…
credit to everyone doing the work. intern mostly just opens tabs.
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-…
Node 𐤊 retweeted
I will tighten the Kaspa pitch. Quickly check current facts so the rewrite stays accurate. What if proof-of-work did not have to be slow?
That is the bet Kaspa (kaspa:native) is making.
Classic PoW chains force miners onto one block at a time. When two honest blocks land together, one gets thrown away. Kaspa does not do that. Kaspa uses a BlockDAG and GHOSTDAG: parallel blocks stay in the ledger and are ordered. Extra work adds security instead of becoming orphans.
Live today:
- Proof-of-work (kHeavyHash)
- ~10 blocks per second (~100 ms block times)
- Fast inclusion, confirmation stacking in seconds
- Fair launch in 2021: no ICO, no premine, no insider allocation
PoW did not have to stay stuck at 10-minute blocks. Kaspa is what a chain looks like when the bottleneck is the chain structure, not the work itself.
kaspa:native is one to watch.
Node 𐤊 retweeted
Why exactly are vProgs on $KAS considered an absolute game changer for #Kaspa and the entire crypto industry explained:
One of the hardest problems in blockchain design is combining independent application sovereignty with the ability to interact securely without overwhelming the base chain.
For years developers had to choose between slow execution on Layer 1 or fragmented liquidity across isolated Layer 2 bridges. Kaspa solves this by introducing verifiable programs that run complex computations completely off chain while maintaining deep ties to a fast Layer 1. Instead of forcing every node to process heavy smart contracts the network relies on zero knowledge proofs. The applications do the heavy lifting independently and Kaspa nodes instantly verify the mathematical proof of that work natively at the protocol level.
This structure means each verifiable program acts as a self contained unit that controls its own rules and internal state. They can read data from other programs to ensure seamless cross application transactions but they only write to their own state. By utilizing a dynamic Computation DAG to track dependencies Kaspa ensures data availability without ever letting a single application overload the network.
The end result is an ecosystem where applications remain completely independent but can still interact atomically and securely. You get all the programmability required for complex decentralized exchanges and vaults directly on a Proof of Work network without sacrificing a single ounce of speed.
Node 𐤊 retweeted
Yonatan Sompolinsky – The Mind Behind Scalable Decentralization and Kaspa🧠
—With 4,223 citations on Google Scholar, Yonatan Sompolinsky has cemented his role as a foundational thinker in blockchain scalability and distributed systems. “The minds behind Kaspa aren’t just anybody. These are the architects who saw the limits of traditional blockchains and dared to reimagine them. They didn’t follow trends — they set new standards. Backed by peer-reviewed research and real academic firepower, they built Kaspa not for hype, but for history. This isn’t just another crypto project — it’s what happens when the brightest minds in distributed systems decide decentralization deserves better.”
Study Kaspa.
Think Kaspa💡
$Kas #Kaspa $Btc
Node 𐤊 retweeted
Newest article on @KaspaCom is live!
Part 2 breaks down PoW, and ties it back into Part 1.
As always, any feedback is appreciated!
kaspa.com/learn-kaspa/post/b…

























