alien.kas

DM me alien.kas on @KaChat_

no one no limitation
kaspa maxi

[514COEURS @kaspaDJ]

I’ll match 1% of whatever the Kaspa wallet #1 donates.
The f*cker better participate.
Make it BIG!

[KaspaDollar @KaspaDollar]

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.

[⁵⁄₉ @fiveoutofnine]

So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and https://t.co/QlOXb3COq3 went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.

[KCC Coordination Forum @kccforum]

Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.

We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build.

Come build with us.

[alien.kas @alien_kas]

@loftedice @KaspaSilver U should have two wallets generated. One for never use (hold only large amount) and one for spending with average amount. That will do.

[Kron @KronTechnology]

Hi DEXTools team,

Shawn from KRON here. We saw you're looking to connect with projects on Kaspa, so I'm reaching out directly.

What KRON is
KRON is a DEX running natively on Kaspa L1. Pools are Kaspa covenants (no L2, no bridge), and tokens are KRON's KCC-20 covenant tokens paired against native KAS. It's been live on mainnet since July 2026, and the covenants were independently audited by Hashlock in September 2026 (https://t.co/UDGwTeUDzC).

What we've already built for data aggregators
CoinGecko pointed us to GeckoTerminal for onboarding. We built a full adapter in GeckoTerminal's Integration API format, and GeckoTerminal is integrating us now. The same data is open to you:

DEX events API (GeckoTerminal format), base https://t.co/LBifEgynoa
- /latest-block: latest indexed block
- /asset?id=<tokenId>: name, symbol, decimals, total and circulating supply
- /pair?id=<pairId>: pair assets, creation block/tx, fee (bps)
- /events?fromBlock=&toBlock=: every swap and liquidity event, with exact amounts, maker address, reserves after each event and native price

Market data API, base https://t.co/NGBwlBYost
- /tickers: price, volume and liquidity per pair
- /historical_trades and /supply/{tick}

The full history is backfilled from the first pool. All endpoints are public with open CORS.

A few Kaspa-specific notes:
- Kaspa is a blockDAG, so "block number" is the blue score of the accepting chain block; timestamps are in seconds.
- Token ids are covenant ids (64-hex). KAS is the native quote asset.
- A signed token list with per-token metadata and logos is at https://t.co/iHUbRNbKZK.
- An open-source SDK is on npm as @kronsdk/kron-sdk (https://t.co/jSy211psVr).

What would you need from us?
Could you let us know what your integration requires? In particular:
1. Can you consume an API like the one above, or do you index chain data yourselves? If so, what node or RPC access would help?
2. Do you need a specific data format or extra fields?
3. Token metadata, logos or socials in a particular format?
4. Any listing form, verification step or point of contact on your side?

Happy to set up a shared channel and turn around whatever you need quickly.

Thanks,
Shawn
KRON (https://t.co/N77cN62pew)
@DEXToolsApp

[Michael Sutton @michaelsuttonil]

@DEXToolsApp @KaspaHub @RelayProtocol @SilentSwap I’m a core Kaspa dev. What do you need and how can I help?

[alien.kas @alien_kas]

Up
@OriNewman @michaelsuttonil

[DEXTools @DEXToolsApp]

@KaspaHub @RelayProtocol @SilentSwap If the main project to talk to us, we can think about it.

[DEXTools @DEXToolsApp]

@KaspaHub @RelayProtocol @SilentSwap If the main project to talk to us, we can think about it.

[Gerhard (Bitcoin Strategy) @BitcoinStrat]

🚀 Kaspa Chain Got Busier

Kaspa fell about 13% this week, but the chain itself got busier. From Tuesday to Saturday the network handled about 84,000 transactions per day, roughly 26% more than the week…

$KAS #kaspa #crypto

Try Premium for 7 days:
https://t.co/Pqan237b8F

[The Kaspa Onion ꓘ @thekaspaonion]

Woah! Kaspa does what zcash does!
Woah! Kaspa does what monero does!
Woah! Kaspa has what solona has!
Woah kaspa has what Bitcoin has

Woah! Kaspa has apps like the app store has!!!

Very soon it will click
And people will realize that kaspa just ended 99% of cryptp

[Ori Newman @OriNewman]

Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending

https://t.co/SOslUfDwKB

[Zealous Swap @ZealousSwap]

V3 pools are now live on the Igra network, with router support activating as liquidity deepens.

kaspa:native

[Sa1𐤊rishna @Sk21451]

A new crowdfunding campaign to renew the Meta subscription for Kaspa Social accounts!

Check the full details and support here: https://t.co/J0j2dd5bvO

[Kaspa @kaspaunchained]

@naruto11eth we do

[Michael Sutton @michaelsuttonil]

it’s exciting to watch y’all starting to realize (as well as actually realize/build) what can be built on post-Toccata Kaspa

[alien.kas @alien_kas]

kaspa:native

[Crypto Rover @cryptorover]

Some altcoins will outperform. Others will get left behind.

Here are some of my picks for the next 3-6 months:

L1
$SOL
$AVAX
$SUI
$KAS

AI
$NEAR
$TAO
$RENDER
$FET

Privacy
$ZEC
$XMR
$NIGHT

RWA
$LINK
$XLM
hedera-hashgraph:native
$QNT
$XRP

DeFi
hyperliquid:native
$UNI
$ENA
$AAVE
ethereum:0x808507121b80c02388fad14726482e061b8da827

Which altcoins would you add? 👇

[Ori Newman @OriNewman]

Some thoughts on the upcoming eCash hardfork https://t.co/xKUoew0wpA

[Killa @KillaXBT]

This is what happens when you spend 1/3rd of your life staring at charts.

You start spotting patterns most never see.

Just look at the PA. For more than a year, $BTC has kept repeating the same swing-high, swing-low pattern.

If we continue building a clear bearish narrative next week, the next phase will likely result in higher.

It’s only based on 600 days of price action, right.

Would you bet against a pattern that’s been this consistent?

[Olaf Weller @WellerOlaf]

Kaspa Privacy Initiative — Development Update

Following my conversation with @michaelsuttonil, we set out to test whether Kaspa's Based Apps and KIP-21 could provide the foundation for a shielded native KAS protocol.

The feasibility PoC on TN10 is now complete!

Across PRs #31–33, we've demonstrated:

✅ Real Kaspa L1 lane ordering
✅ Execution with cryptographic ZK proofs
✅ Proof-based settlement accepted by Kaspa
✅ Rejection of deliberately omitted operations
✅ State reconstruction and successful native KAS withdrawal after executor downtime

This is a significant step forward. Rather than building our own transaction-ordering infrastructure, we can potentially build on capabilities already available in Kaspa.

We've also added a new design principle in PR #34: future protocol upgrades should preserve users' access to their funds and aim to enable privacy-preserving migration between versions.

Now comes the part we've been working towards: actual financial privacy.

Our next milestone is a shielded payment cycle: Alice deposits native test-KAS, privately pays Bob, and Bob withdraws native test-KAS.

We'll begin by designing the private notes, commitments, nullifiers and ZK proof rules needed to make that possible.

The Based App PoC demonstrates technical feasibility within its tested scope. It is not yet a privacy protocol, an independently audited system or a final architecture decision.

But we're moving from proving the infrastructure to building the privacy layer itself.

All research remains open source. Technical feedback and contributions are welcome!

https://t.co/h4gdcS0FpP