(自分用メモ) 最新KIP一覧 ※KIPを追うと、Kaspaの進化の方向性がよく見える為 現在、公式リポジトリには15件が掲 10件がPR・提案段階 ・KIP-2：DAGKNIGHT ・KIP-15／21：取引順序と状態の証明 ・KIP-16：ZK証明の検証 ・KIP-17／20：Covenantと状態管理 ↑上記は特にToccata、vProgs、L2、DEX、ステーブルコインなど、今後のKaspaエコシステムを支える重要な基盤 #Kaspa #KAS #BlockDAG #DAGKNIGHT #vProgs

huge honor but I’m also nervous ngl

（自分用メモ） 2026年9月19日現在 直近24時間のKaspa関連 X投稿：2,599件 ユニーク投稿者：1,039人 全ソーシャル投稿：2,974件 暗号資産全体に占める話題シェア：0.659% 話題量順位：18位 エンゲージメント：約180万件

this KIP-12 is superseded by KCC-12. goal: dApp doesn't need to integrate browser wallet 1 by 1. If you own a dApp (/want to), or you own a browser wallet, please read the proposal and add your thoughts (not LLM thoughts, we can do that on our own)

Kaspa v2.1.0 is out [Link in the reply] All node, mining, and infrastructure operators across mainnet and testnets are strongly encouraged to upgrade. This release introduces P2P Protocol Version 11, extracts a standalone ZK SDK, and reflects an ongoing focus on proactive defense-in-depth across the node architecture. Key Highlights: • P2P Protocol Version 11 & Chunked IBD: Large Initial Block Download (IBD) payloads (including Pruning Point Proofs, headers, and trusted data) are now streamed in 20 MiB chunks. This eliminates message- framing bottlenecks and timeouts during node sync, backed by overall safety limits and transfer timeouts, while maintaining full backwards compatibility with Protocol 10 peers. • Standalone ZK SDK: Zero-Knowledge proof and script-generation tooling has been extracted into a dedicated crate (kaspa-txscript-zk-sdk). It adds support for RISC Zero Groth16 and STARK verifier generation with dynamic or static image IDs, bounds control proofs against oversized inputs, and resolves cross-platform build issues. • General Hardening: Comprehensive defense-in-depth upgrades across the node, including stricter P2P message and block limits to guard against DoS vectors, a workspace-wide arithmetic safety audit to eliminate overflow risks, enhanced stratum bridge stability, and tighter consensus validation. These structural safeguards significantly strengthen node resilience and provide higher confidence in overall network security.

I should be more careful with my wording re kcc20 for future record: a properly written kcc20 covenant will enjoy L1-grade security (bcs L1 will enforce those properly written rules), but kcc20 is inherently just a spec/convention. a specific kcc20 covenant instance might still have implementation bugs or even compiler toolchain exploits, just like any other programmable system (eg just like vulnerabilities found in specific eth smart contracts). that is to say that not all kcc20 covenants will be equal, and a future problem in one of them does not necessarily reflect on the others or on the underlying L1 script engine

（自分用メモ） 2026年9月14日現在 直近24時間のKaspa関連 X投稿：3,107件 ユニーク投稿者：1,318人 全ソーシャル投稿：3,535件 暗号資産全体に占める話題シェア：0.808% 話題量順位：14位 エンゲージメント：約99.9万件

the next crypto giant might be solving a problem nobody cares about yet. when demand finally arrives, its foundation will already be in place.

（自分用メモ） 2026年9月9日現在 直近24時間のKaspa関連 X投稿：3,245件 ユニーク投稿者：1,343人 全ソーシャル投稿：3,653件 暗号資産全体に占める話題シェア：0.782% 話題量順位：18位 エンゲージメント：約120万件

A lot of people think what makes Kaspa unique is the technology. But the technology is really the consequence of a deeper philosophical difference. Most crypto projects ask: How can we maximize performance without sacrificing decentralization? Kaspa asks: How can we maximize decentralization without sacrificing performance? That slight inversion of priorities changes everything. It changes what the system optimizes for, which tradeoffs are acceptable, and ultimately what kind of threat model matters. Kaspa and in particular the upcoming DAGKnight fork are built around the idea that a decentralized monetary network should remain resilient even under extreme failure scenarios like global infrastructure disruption, war, or other large-scale breakdowns. Because fast digital coordination should not force people to choose between trusting a small group of node operators over a small group of banks. For many applications, that distinction may not matter. But for the applications where credible neutrality, censorship resistance, and resilience matter most, that ideological edge is the product. Kaspa does not merely compete at the technological level. It competes at the philosophical level and the technology is just the downstream consequence of following that philosophy to the end.