numewo2 retweeted
Two KCC-20 tokens, same name, same ticker, same logo. This is how Kasla tells them apart: the covenant ID itself is drawn into a mark, so you can see at a glance whether this is “your” token. The ID also sits next to every name, and anything unverified is labelled as such before it gets near a payment.
Seven things I learned making a wallet safe for launch day, for anyone building one on Kaspa:
kasperolabs.com/kcc20-wallet…
numewo2 retweeted
WSX NEWS: 🔥 @Kaspaseal Targets October 23 Mainnet Launch for Kaspa’s KCC-20 Ecosystem
A new token-launching platform is preparing to enter the @KaspaCurrency ecosystem. @Kaspaseal is scheduled to launch on mainnet on October 23, bringing a KCC-20 memecoin launchpad to Kaspa Layer 1.
The platform is designed to let creators launch tokens with supply fixed at genesis and token rules enforced on-chain, aiming to make token creation more transparent and predictable.
One notable feature is its proposed creator-reward model: launchers earn 0.5% of each trade in their token, paid directly in $KAS. That links creator rewards to ongoing trading activity while adding another potential use case for Kaspa’s native asset.
With KCC-20 advancing through its review process, the launch could become another development to watch across Kaspa’s growing token ecosystem. The key milestones will be the mainnet rollout, how the rules work in practice, and whether users adopt the platform. 👀
Kii is giving a keynote at the ETIM Forum 2026 in Torremolinos, Spain on 28 October.
We will show KiiWORKS: digital product passports for industry, built from the ETIM data manufacturers already publish and verifiable by anyone on Kaspa.
#Kaspa
numewo2 retweeted
P2SH arrived on Kaspire! Yesterday, @OriNewman introduced KIP-22 for quantum resistant P2SH addresses, today you can already use it.
The P2SH feature hides the public key of your wallet address as long as the KAS received there remain unspent. With a standard Kaspa address, this public key is directly visible. In contrast, a P2SH address initially reveals only a cryptographic fingerprint of the underlying spending script.
Why is this significant? In theory, a sufficiently powerful quantum computer could derive a private key from its corresponding public key. By keeping the public key hidden, this direct point of attack is removed.
However, the public key becomes visible once a transaction is made. For this reason, Kaspire uses a fresh P2SH address for any change. Addresses that have already been used should not be reused to receive further funds.
To use this new feature update your Chrome Extension to version 0.5.11 and Android app to version 0.11.53. Both updates are live. You can find your P2SH addresses under Receive – P2SH account (requires a seed-based wallet, private-key wallets are not supported).
🤖 Made with AI
numewo2 retweeted
PR #31 (KCC-20 Last Call advancement) was merged on October 7, 2026 at 20:38:09 UTC. 14 days from that is October 21.
KCC-20 is final on October 21.
Quick clarification on KCC-20 timing 👇
PR #31 moved KCC-20 to Last Call on 7 Oct, but the header has no Last-Call-Deadline. On a 14-day count that's ~21 Oct.
A few questions please:
1.Is 21 Oct the intended end of the review window, or is a deadline still to be set?
2.KCC-1 and KCC-2 went Last Call on 1 Oct — do all three move to Final together, or does KCC-20 wait on those two?
3.Is the argent-lang reference impl + merged vectors considered to satisfy the KCC-0 §4.2 "public implementation" requirement?
Asking so builders know when it's safe to ship against KCC-20 as Final rather than Last Call. Appreciate the work on this 🙏
@manyfest_ @michaelsuttonil
@IzioDev
@asaefstroem
numewo2 retweeted
$KAS
Stronger quantum resistant addresses coming to KaChat very soon!
All you need to do is simply generate a new spend address. All new spend addresses have the upgrade. Send Kaspa to it and don't send anything out and that address will remain protected.
Upgraded addresses start with kaspa:p... while the legacy addresses that always expose the public key start with kaspa:q...
numewo2 retweeted
#Kaspa
Kaspa(カスパ)の上で、「alice.k」のような名前を、たくさんの人が一斉に取りに来たらどうなるのか。
何も工夫しないと、全員が一つの窓口に並ぶことになります。Kaspaは何車線もある高速道路のように取引を同時に処理できるのに、アプリの入口が一つだと、料金所の一か所で詰まってしまう。
Kaspaのコア開発者、マイケル・サットンさんが2026年10月16日(日本時間)に投稿した技術的な解説をもとに、UTXO(お札)とコベナント(ルール付きのお札)の基礎から、行列を避ける3つのやり方など、順番に説明します。
youtu.be/3LddW7WZAIA
numewo2 retweeted
I believe we will eventually add native pqdsa support, but this is only the first step. (btw, it's possible to implement pqdsa with kaspa script, see github.com/biryukovmaxim/kas…)
numewo2 retweeted
Kaspa Privacy Initiative needs a face. 🗳️
Three directions, all built on Kaspa's own K. Black & white on purpose: vote on the shape first, colours come in poll 2.
Which one should KPI take? What each concept means is in the thread below 👇
32%Seal
9%Cipher
59%Shield
237 votes • 11 hours numewo2 retweeted
#Kaspa $KAS
Ori Newmanさんより、KIP-22が公開されました。
「公開鍵をアドレスに直接さらさず、ハッシュの裏に隠しておく」ためのウォレット側の取り決めです。
簡単ですが、まとめてみました。
1️⃣なぜ必要なのか?その背景は?
Kaspaの普通のアドレス(kaspa:q…)は、中に公開鍵がそのまま入っています。
今は安全ですが、高性能な量子コンピュータが登場すると、公開鍵から秘密鍵を割り出せる可能性があります。
つまり「受け取った瞬間から狙われうる」状態なので、そこを改善しようという内容。
2️⃣仕組み
公開鍵を“ハッシュの封筒”に入れて保管する方式ということで。
・受け取り時:チェーンに載るのは封筒(ハッシュ)だけ
・保管中:公開鍵は誰にも見えない
・送金時:ここで初めて中身を見せる
「ずっと丸見え」が「使う瞬間だけ見える」に変わります。
3️⃣いつ使えるのか?注意点は何か?
ネットワークのアップグレードは不要で、各ウォレットが対応すれば使えます。
ただしまだDraftで、議論はこれからです。
今からできる対策:
・アドレスを使い回さない
・xpub(拡張公開鍵)をむやみに共有しない
※深堀するとRedeem ScriptやPay to Script Hashなど色々出てきますが、とりあえずまだまだ草案段階ですので、詳細が固まってきたら解説動画化するかもって感じですかね🤔
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
numewo2 retweeted
将来、十分に強力な量子コンピューターが登場すると、次のような攻撃が可能になる恐れがある
① ブロックチェーン上の公開鍵を取得
② 量子計算で公開鍵から秘密鍵を導出
③ 秘密鍵で取引署名し、資産を奪取
現在のKaspaの標準アドレスは公開鍵が露出しているため、将来的にこの攻撃の対象となり得る
そこでコア開発者Ori Newmanが、新たな改善提案「KIP-22」を公開
公開鍵をハッシュで隠し、送金時まで露出させないことで、量子攻撃のリスクを軽減する
しかも既存のP2SHを活用するため、ハードフォークなしで実現できる設計だ🔥
※ただし、送金時には公開鍵が露出するため、完全な耐量子化ではない
現在は提案段階で、ウォレット側の対応も必要となる
DAGKNIGHTがKaspaの「性能」を進化させるなら、KIP-22は資産の「安全性」を高める一歩
Kaspaは量子コンピューター時代を見据え、長期的な安全性の強化にも取り組んでいる
#Kaspa #KAS #KIP22
🤖 Made with AI
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
🚨 Quick clarification!
We’re serious about the direction we’ve shared.
But for example, Tokenized Stocks is one of those things which will take time to turn it into reality.
We’re building for the long term. There’s a lot of work ahead, and we’re here to do it.
$Kas
numewo2 retweeted
It's an honor to be part of the @fablesfi partner list. Let the adventure begin !
numewo2 retweeted
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 (kron.technology/audit).
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 idx.kron.technology/v1/dex-e…
- /latest-block: latest indexed block
- /asset?id=: name, symbol, decimals, total and circulating supply
- /pair?id=: 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 idx.kron.technology/v1/aggre…
- /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 api.kron.technology/api/regi….
- An open-source SDK is on npm as @kronsdk/kron-sdk (github.com/KronSDK/kron-sdk).
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 (kron.technology)
@DEXToolsApp
I like! This is a really simple and inexpensive way to significantly reduce the quantum threat to Kaspa users.
Traditional addresses expose the public key controlling the funds. A sufficiently powerful quantum computer could derive the private key from that public key and steal the funds.
KIP-22 proposes a simple change: instead of exposing the public key, an address commits to a cryptographic hash (a fingerprint) of the spending conditions. The public key stays hidden, and unlike elliptic-curve cryptography, strong cryptographic hashes remain highly resistant to quantum attacks.
Only when we spend the funds do we reveal the necessary information for the network to verify the transaction.
There is still a theoretical attack vector where an attacker could intercept a spending transaction, derive the private key, and attempt to front-run the original transaction. But since PoW relies on hashing, which is far more resistant to quantum attacks, the network should remain operational and continue confirming transactions, leaving an attacker with only a very narrow window to act.
Exploiting this would require not just a quantum computer capable of breaking public-key cryptography, but one powerful enough to do this faster than the network converges. On Kaspa, that means just a few seconds. That's a much stronger "theoretical adversary," and it's unclear whether such a machine will ever exist.
Personally, I doubt quantum computers will ever be able to break public-key cryptography at realistic key sizes (I suspect that Hilbert space itself is discrete and has a much coarser resolution than commonly assumed, but that's a different topic).
So TL;DR: KIP-22 isn't a "complete" post-quantum solution, but it's an elegant, relatively low-cost way to significantly reduce the attack surface for quantum adversaries.
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
numewo2 retweeted
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…



































