CryptoMoses retweeted
Kaspa Token Standard KCC-20 Enters Final Review
Kaspa’s (@kaspaunchained) $KAS KCC-20 token standard has entered its final review stage before potential finalization.
The proposal establishes standards for fungible tokens concerning their ownership, balance and transaction process. This includes how wallets and apps interpret the information of tokens and how they handle borrowed tokens.
A finalization of KCC-20 could give developers a standard approach when working on token tools within Kaspa.
CryptoMoses retweeted
kaspa:native looks like it’s gearing up for a HUGE move 👀
Where’s the @kaspaunchained community at? 🔥
CryptoMoses retweeted
JUST IN: Kaspa Network crosses 2.4 billion total transactions
The network has now processed 2.418 billion transactions just months after the Toccata hardfork went live.
CryptoMoses retweeted
Kaspa is becoming much more than just a PoW L1...
We dive into the Toccata Hardfork and examine its impact on the Kaspa ecosystem ⬇️
bsc.news/post/kaspa-toccata-…
CryptoMoses retweeted
bitcoin dev's were discussing covenants back in 2013.
bip-119 later proposed one approach to covenants, restricting spending to a predefined transaction template. it was never activated on btc tho.
kaspa’s covenants go further (covenants++ if you like). scripts can enforce spending rules, carry application state forward and let that state split into branches that progress independently. multiple contracts can also update together in one transaction, with all changes accepted or none of them.
dev's write that logic in silverscript, which compiles it into scripts kaspa enforces on L1.
CryptoMoses retweeted
KAS topluluğu, hazır mısınız? 🥁
Gate TR x @turkiye_kaspa iş birliği başladı!
Sen de yerini al, kaspa:native ödüllerini kaçırma!
Detaylar ve katılım 👇
gate.tr/campaigns/6405
CryptoMoses retweeted
Top 10 Blockchains — $RUECAT DEX 🏆Overall Score:
1. Kaspa $KAS — 72.6/100
2. Solana $SOL — 71.7/100
3. Internet Computer $ICP — 70.9/100
4. Stellar $XLM — 69.2/100
5. Algorand $ALGO — 68.1/100
6. XRP Ledger $XRP — 67.6/100
7. Aptos $APT — 66.8/100
8. NEAR Protocol $NEAR — 66.8/100
9. Sui $SUI — 66.5/100
10. Injective $INJ — 66.1/100
$KAS $SOL $ICP $XLM $ALGO $XRP $APT $NEAR $SUI $INJ #Blockchain #TPS #GasFees #Layer1 #Crypto #Web3 #DeFi #RUECATDEX #Altcoins #OnChain
CryptoMoses retweeted
kaspa is an open network for money and apps, secured by proof of work.
you can transact without needing anyone’s approval. devs can build assets and contracts with rules the network itself enforces.
miners compete to produce blocks through computing power and electricity, not the size of their KAS wallet.
an attacker trying to undo a confirmed transaction has to compete against the combined mining power of the entire honest network while it keeps mining. even then, they can’t make nodes accept transactions that break the rules.
kaspa includes and orders blocks mined in parallel, so miners blocks aren’t discarded simply for losing a race. those frequent blocks let the network reach agreement in seconds while keeping bitcoin’s proof-of-work security principles.
kaspa calls this real-time decentralization.
CryptoMoses retweeted
Kaspa has supported embedding data in transaction scripts since launch. devs could build software to read that data off-chain and interpret it however they wanted. Kaspa’s consensus doesn’t enforce that interpretation.
the Toccata hard fork expanded what those scripts can do. covenants let devs define, for example, who can move an asset and under what conditions. Kaspa itself enforces those rules on L1.
KCC20 uses covenants so Kaspa enforces token ownership and transfer rules. the reference implementation is nearly complete.
CryptoMoses retweeted
$KAS Update
The bigger thesis is starting to work its way through the daily.
First thing I want now is clean acceptance above $0.04.
If that holds, $0.053 is the next level that matters.
I still expect this move to build in steps, not a straight line. Pullbacks along the way are part of the structure, not a reason to lose the bigger view.
$KAS
The liquidity left behind after the last bull cycle has finally been taken.
A two and a half year downtrend is now broken, and nearly a full year of accumulation looks close to ending.
From here, I expect the next expansion to eventually push price back above $0.20.
I’ll put it simply. I think these are the cheapest prices you’re going to get.
CryptoMoses 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.
teapawt.net/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.
teapawt.net/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.
teapawt.net/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-…
CryptoMoses retweeted
We’re looking for 3 Maxis. 👀
1 $BTC Maxi.
1 $KAS Maxi.
1 $XRP Maxi.
The idea: bring all three together for an X Space and let each one make the case for their project.
No pointless shouting. No “my bag is better than yours.”
Just conviction, arguments and an open discussion about why you believe your project deserves to win long term.
Think you’re the right person?
Drop a comment or tag someone who is.
💙🤍💙
CryptoMoses retweeted
We received lots of interest from the Kaspa community! We'll speak to our dev about listing $Kas. In the meantime please check out our website, read our whitepaper and please leave any questions below! Also follow our main dev @CCSMainDev for website updates, tips and tricks