Murrelet 𐤊

$kaspa Value at $28. ETA 2027.

[Murrelet 𐤊 @shhipng22]

$kas Currently in the second turnover period, the first batch of 0.0001-0.001 users have changed hands between 0.03-0.05 in August.
At present, the turnover period should be between 0.05 and 0.12.If you believe in it, please add your position in the meantime as soon as possible.

[Vijay 𐤊ailash, CFA, CFP® @realvijayk]

I've spoken to people who sold all their bitcoin for #Kaspa

But I've never spoken to anyone who's sold all their $KAS for Bitcoin

[Chainquiry @chainquiry]

Kaspa ($KAS) is now listed on Chainquiry 🔎

Explore its GHOSTDAG design, kHeavyHash mining, tokenomics and official links in one research profile.

https://t.co/2BMsQ9qT54

@KaspaCurrency #Kaspa

[CoinGecko @coingecko]

$KAS rises 14.9% on news that Bayit Development plans to accept Kaspa as payment for luxury townhomes in Miami.

[Maksim Biriukov @Max143672]

Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday.

You can play it here: https://t.co/hd2NsYyhXt
(Requires private key and some testnet funds)

We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately

I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top

For Devs: this is the invitation. Play the game, read the code, build your own vprog.

Game code: https://t.co/xebZK8N20P
vprogs framework: https://t.co/efpVCTErEc

[ChainHodler @ChainHodler]

It’s time to make some real noise. Let’s make sure Robinhood hears us loud and clear: we want $KAS listed!

​Let’s show them the strength of the Kaspa community.
Like, repost, and drop a comment to spread the word!

[Kaspa @kaspaunchained]

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.

[Murrelet 𐤊 @shhipng22]

kaspa:native
If Apple enables cryptocurrency payments, I don't know if kcc20 will come in time. If Samsung and Huawei both enter the cryptocurrency payment, it will be very good for $kas.

[Coin Bureau @coinbureau]

🚨JUST IN: Apple hints at adding stablecoin support, potentially allowing CRYPTO payments via Apple Pay.

Apple posted a job listing requiring stablecoin expertise for payment roles, offering up to $280,000.

This follows Samsung’s plans to introduce the same feature to Samsung Wallet.

Together, Apple and Samsung have more than 3.5 BILLION active devices worldwide.

[Igra Labs @Igra_Labs]

⚠️ Security notice: KRC-20 incident

An incident on offchain indexer earlier today resulted in unauthorised movement of ZEAL and NACHO out of the KRC-20 bridge custody. The custody's entire holdings of both tokens were taken, so ZEAL and NACHO on Igra and Kasplex L2 are not backed on L1.

Our current understanding is that the underlying issue affects KRC-20 accounting more broadly, not only these two tokens. We have escalated to the indexer, bridge and exchange teams.

Until they confirm a fix, treat KRC-20 balances and deposits on Igra as unconfirmed.

Paused until further notice: iKAS exits to Kaspa L1 and Hyperlane transfers. Existing balances are unaffected and nothing is lost. Both resume once the issue is confirmed resolved.

Until further notice:
- Do not bridge any KRC-20 token in either direction.
- Do not buy ZEAL or NACHO on any L2 DEX.
- Do not add liquidity to ZEAL or NACHO pools.
- Existing positions in WiKAS/ZEAL and NACHO/WiKAS, including farm positions, are impaired.

Exchanges and bridges crediting KRC-20 deposits should pause them pending confirmation from the indexer team.

Not affected on Igra: iKAS, WiKAS, IGRA, USDC, USDT, staking, LYNX, Kaskad.

ZEAL and NACHO are the only KRC-20 tokens bridged to Igra.

The Igra bridge contracts and relayers operated correctly throughout. The attacker's L2 address is 0x1B4B7108a49F028598c5ED49B7951c80d44e7FD2. Technical details will follow.

[Kaspa @kaspaunchained]

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.
https://t.co/HhJwadfWKx

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.
https://t.co/RZSUnvFDhs

3 / DAGKnight
kaspa’s next consensus protocol remains in development.
https://t.co/d6KZZKEKlE

4 / vProgs
@Max143672 has been busy. intern is doing his best to keep up.
https://t.co/SsNR0Knugu

5 / x402
@elldeeone released a test release for letting apps and AI agents pay for API requests in KAS. available to try on tn10.
https://t.co/sLZKErQcIT

credit to everyone doing the work. intern mostly just opens tabs.

[Kaspa @kaspaunchained]

a lot crossed the interns feed this week. some of it even made it into the brain.

too much to give everything its own post, so welcome to the first annual-weekly-might-not-happen-again dev roundup.

1 / SilverScript v1
@OriNewman released v1. lets devs write Kaspa contracts in something a human can read. his token example goes from thousands of lines of low-level code to roughly 60. fewer lines for intern to misunderstand.
https://t.co/EY04sEyhCy

2 / Argent
updated to SilverScript v1, with docs explaining how contracts work together in one transaction.
https://t.co/rsPQ0xscTK

3 / DAGKnight
a new consensus protocol for Kaspa that adapts to network delays. devs merged more code this week to prepare for testnet. still in development.
https://t.co/V8aEeGZYR5

4 / KCC12
@asaefstroem submitted a proposal so apps can connect to different browser wallets the same way. less separate hookup work for devs. currently under review.
https://t.co/8HezEqBNEF

5 / Argent/KCC20 workshop
@manyfest_ posted workshop #2, showing a KCC20 borrow transfer. recording if you want to see the contracts being put together.
https://t.co/EDSdUZE6fQ

6 / Python SDK
new test release for devs building with Python, updated for SilverScript v1. still a release candidate, so a few things may need yelling at.
https://t.co/0KVNin6aMc

think i missed something? good, lmk

[Kaspa Bulgaria 𐤊 @KaspaBG]

Ethereum people laughed because Kaspa “had no smart contracts.”

Now Silverscript v1 is live.

What once took thousands of lines of low-level opcode logic can now be expressed in around 60 readable lines.

The joke expired.

Kaspa isn’t trying to become another EVM chain.

It’s building programmability on top of scalable Proof of Work.

Most people are still pricing kaspa:native like the story hasn’t changed.

That’s the interesting part. ⚡

$KAS #Kaspa #ProofOfWork

[Murrelet 𐤊 @shhipng22]

kaspa:native Offensive and defensive changes.

[BSCN @BSCNews]

It is now possible to write readable Smart Contracts on Kaspa!

@Kaspaunchained announced the launch of Silverscript v1, a high-level smart contract language designed to streamline the development of complex, stateful applications on the Kaspa ledger.

The language removes the technical overhead of raw opcodes, reducing thousand-line implementations into 60-line, human- and AI-readable scripts.

This aims to foster faster innovation in UTXO-based finance.

The release marks the conclusion of an eight-month development cycle alongside the Toccata framework, providing developers with the tools to build sophisticated token mechanisms and layered abstractions.

"This completes the journey we started eight months ago with Toccata — it's finally possible to write human- (and AI-) readable smart contracts on Kaspa," core developer @OriNewman stated.

Worth noting that the KCC20 standard is still not live yet.

[L1‎𐤊aspa @KaspaLayerOne]

🚨 Silverscript v1 is officially out! 🚨
​This completes the 8 month journey that started with Toccata. We can finally write human and AI readable smart contracts on $KAS.
​What used to take thousands of lines of raw opcodes for an early token mechanism can now be written in just 60 lines of code. It grew from just "CashScript with loops" into a full smart contract language handling complex, stateful contracts.
​Massive step for UTXO programmability on Proof-of-Work. Silverscript is setting the foundation, and Argent is coming next to add higher layers of abstraction.
​Link to the Github release: https://t.co/cVf4UmTD9u

[BSCN @BSCNews]

Kaspa comes close to a $1 billion market cap after a 17% day

kaspa:native traded near $0.0359 on Monday, up around 30% across the week. The market cap currently sits at $994.5M, and volume rose to $50.12M, up almost 500% on the day.

Most KAS coins are already in circulation, 27.68B of a 28.7B maximum, setting the fully diluted value at $1.03B.

[Murrelet 𐤊 @shhipng22]

LFG!!!

[MassijK ʞ 🇮🇹 🐬 @Massij74]

Con 200.000 KAS, ecco la tabella che conta davvero 🚀
Prezzo KAS
Valore 200.000 KAS
$0,05
$10.000
$0,10
$20.000
$0,20
$40.000
$0,50
$100.000
$1
$200.000
$2
$400.000
$5
$1.000.000
$10
$2.000.000
$KAS

[Kaspa @kaspaunchained]

Time to level up

[Kaspa @kaspaunchained]

The intern has been informed that yesterday’s post about Covenants needed an ELI5.

The intern has also been asked to stop using the words “successor” and “lineage” until further notice.

So we are going to use noughts and crosses.

state = what the board looks like right now
covenant = the rulebook
transaction = someone trying to make a move
the kaspa network = the referee

Look at the empty board. Nothing has happened yet. That is the starting state.

Put an x in the middle. the board has changed. that is the next state.

Now someone tries another move. The network checks it against the rulebook. If the move is allowed, the board changes. If it is not, the transaction fails.

The rulebook does not disappear after one move. The new board stays protected by the same rules, so the move after that has to follow them too.

One starting board can also open game A and game B.

Each game keeps its own board. both can continue without waiting for the other.

This is the noughts and crosses version. The same pattern can be used for vaults, escrow, time locks, asset issuance, transfer rules, tickets and positions directly on the Kaspa L1.

If that still made no sense, the intern accepts full responsibility and no follow up questions.

[Grayscale @Grayscale]

@realvijayk @hashdag Kaspa army really showed up here.
Followed @hashdag ✅