sky.𐤊 (@skyytf) profile picture
Joined February 2018
Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)Photo by sky.𐤊 (@skyytf)
Kaspa’s evolution: from local scripts to stateful systems, without losing locality I want to try to explain, in simple words, the vision and the gradual implementation path for smart contracts and complex financial systems on Kaspa. Instead of trying to cover everything, I am going to weave one continuous line of thought: from the most basic primitives, through the key additions we are making, toward the system-level picture. A meta note: even in parts where the destination feels intuitively clear, conceptual clarity only emerges while building. This is not just engineering, and not pure theory either. It is system research: making the model itself clear as we walk. A simple ladder to keep in mind: • UTXO scripts constrain spend authorization • Covenants constrain next outputs • Lineage authenticates which instance is “the real one” • ZK verifies transitions by succinct proofs, without on-chain execution One guiding principle throughout: we want these capabilities as first-class consensus and script-engine primitives that compose cleanly, not as clever edge-case constructions. --- UTXO as the base model: a constitution that governs a resource The UTXO model is, at its core, a script (a “constitution”) that controls a resource. That constitution is local in two senses: • Local in space: the spending script sees only the inputs it spends, plus whatever data the spender provides. • Local in time: the script is a one-shot gate. Once a spend happens, the old constitution does not persist into the future. The future is governed by whatever new scripts the coins are sent to--but there is no inherent linkage between old rules and new rules. In the common case, the constitution is minimal: “only someone who can prove possession of a private key may spend”. In pseudo-form it is basically: SigVerify(pk). The spender provides a signature proving they control the private key behind pk, and that they authorized this specific transaction. --- The one thing that is enforced over time: conservation of value There is one strong temporal law baked into the base model: conservation of value. Consensus enforces that the total KAS value created by a transaction is less than or equal to the total KAS value it consumes. This is why “Kaspa the asset” is not just data in a UTXO. It is a native resource with a conservation law enforced by the protocol. So Kaspa already has one temporal invariant “for free”. --- But what if we want richer rules than “who can spend”? Now imagine we want more complex logic. Examples: • Coins can only be sent to a whitelist of addresses. • Only 5% of the balance can be spent per day. • This resource must evolve under a fixed policy over time. This is where the right mental model becomes a state machine. A state machine has a state and a transition function. The transition function must be able to enforce what the next state is allowed to be. In UTXO terms, “writing state” happens by creating the outputs of the spending transaction--so a real transition function must be able to constrain the outputs. The problem is the locality constraint: in the classic btc-style scripting model, without introspection, the spending script cannot constrain what it is creating. It gates the spend, but it cannot reason about outputs. Without seeing outputs, implementing a genuine state machine is impossible. (Notwithstanding btc’s indirect workarounds via sighash tricks, which can approximate limited introspection in specific patterns.) --- Introspection: enabling state machines in a local-compute model This is why transaction introspection opcodes are a foundational step. (This is what KIP-10 introduced, starting with Crescendo.) Once the script engine can read transaction fields, and crucially inspect output scripts, the transition function can finally say: “you may spend this input only if you create outputs that satisfy these constraints”. Conceptually, that is the birth of what we call a covenant: a spend is no longer pure ownership transfer. Spending becomes conditional on preserving a policy across time. It lets a resource enter a covenant: the owner’s freedom becomes constrained by an on-chain policy that must remain true after the spend, not only at the moment of spending. Note how this enables persistence without losing locality. The script only enforces a one-step look-ahead, by constraining the next outputs. But if it requires those outputs to carry the same policy forward, it becomes an inductive rule: one-step enforcement is enough to preserve the covenant across arbitrarily many future transitions. --- Completing the state machine model: primitives and lineage At this point we can describe covenants in principle, but to make general state machines possible we need two things: better building blocks, and a notion of authority for non-KAS state. (1) Byte and hash primitives: even if you can see outputs, you still need the low-level tools to express robust constraints. That means byte-string construction and parsing (e.g., OpCat, OpSubstr) and strong hashing with domain separation (e.g., OpBlake2bWithKey). Without these, you can’t reliably build commitments, slice out exact fields, or enforce consistent state encodings that make transition validation composable. (This is what KIP-17 added on TN12.) (2) Lineage (provenance): “who says this state is real?” Once a covenant represents non-KAS state (a token, an asset, or the compressed state commitment of an off-chain application), the state is no longer self-authenticating the way KAS value is. A short concrete story: • I can create a UTXO whose script claims “I am TokenX with supply 1,000,000”. • Nothing in consensus prevents me from writing that claim into a script and funding it with real KAS. • So the real question becomes: how do wallets know which instance is the real TokenX state machine? This problem only appears once “state” is no longer the native KAS resource, so it helps to separate the KAS case from the non-KAS case: • If the covenant is “about KAS”, the value already has native, consensus-backed provenance via conservation. You do not need lineage to prove the KAS value was not created from thin air. • For non-KAS state, there is no conservation law. Without lineage, you cannot prevent “fake instances” of the same-looking scheme. So for non-KAS covenants, lineage must be part of the design: the instance has to be anchored to a recognized genesis, meaning an agreed initial state and rules for a specific state machine instance, and then continued through valid transitions. KIP-20 addresses this by introducing consensus-tracked covenant IDs for instance identity and lineage. --- The next layer: ZK With covenants able to enforce transitions and lineage, we can move beyond “everything must be revealed and executed in-script on-chain”. This is already the direction on TN12 with ZK verification opcodes (KIP-16). Without ZK, each state transition must be validated on-chain by revealing what the base layer needs to check. In practice, every step tends to carry three costs: revealing the state preimage, revealing the rules preimage, and executing the transition checks in-script. ZK verification opcodes let us keep only commitments on-chain and prepare the public transition inputs, then a proof attests that there exists a valid hidden witness and execution trace that takes the old commitment to the new commitment under the intended rules. That gives scalability, and sometimes privacy. L1 enforces correctness without re-executing the full computation in-script, and without forcing state and rules to be re-published on every transition. The bigger consequence is expressiveness: ZK is machinery above covenants that lifts the “on-chain execution” ceiling. The base layer verifies validity, while the full transition function can be arbitrarily complex off-chain, including loops and large computations. In that sense, covenants plus ZK give a path to general-purpose computation anchored and enforced by L1. --- Outlook: Part 2 Part 2 will go deeper into the ZK layer and the shared-state story: • How a zk app can be based, meaning L1 sequencing fully determines the transition history. • How these primitives support canonical bridging of KAS. • How we further modify the base layer so multiple zk apps or vprogs can synchronously compose without waiting for base-layer messaging roundtrips.
47
281
30
858
84,016
The Kaspa network just got its DeFi moment. 🌐 Founder of @KaspaFinance @cryptojameslee explains how @kasplex is bridging mainstream DeFi to Kaspa and why scalability is the key to growth. Watch the full interview with @graminitha1 from @token2049 Singapore here. 🔽
68
193
21
513
87,449
What are vprogs and why is Kaspa rallying (at last) 🧑🏼‍💻 Overview of Kaspa vProgs Kaspa vProgs, or Verifiable Programs, represent a foundational protocol upgrade for the Kaspa blockchain, a high-throughput proof-of-work (PoW) network utilizing a blockDAG (Directed Acyclic Graph) structure rather than a traditional linear chain. Introduced in mid-2025 through a draft yellow paper by core developer Michael Sutton, vProgs aim to enable native programmability on Kaspa’s Layer 1 (L1) without compromising its core strengths in speed, security, and decentralization. This framework addresses longstanding limitations in blockchain scalability by decoupling computation from on-chain execution, allowing for complex, verifiable applications while preserving the network’s lightweight consensus mechanism. Prior to vProgs, Kaspa primarily functioned as a base layer for payments and simple token standards like KRC-20, lacking robust support for full smart contracts. vProgs position Kaspa as a “universal settlement layer” capable of supporting decentralized finance (DeFi), tokenized real-world assets (RWAs), and other programmable use cases, all while maintaining sub-second finality and throughput exceeding 10,000 transactions per second. In every sense out is Ethereum squared. Or Bitcoin on steroids. Key Architectural Features vProgs introduce a modular, composable system designed for efficiency and sovereignty. The core elements include: ✅ Off-Chain Execution with On-Chain Verification: Complex computations occur off-chain to avoid burdening the L1 with resource-intensive tasks. Once executed, zero-knowledge proofs (ZKPs) are generated to mathematically attest to the results’ validity. These proofs—rather than the full execution data—are periodically anchored to Kaspa’s blockDAG, ensuring integrity without bloating the chain. This “verify-first, execute-off-chain” model aligns with Kaspa’s emphasis on minimalism, where the L1 focuses solely on validation. ✅ Self-Sovereign Modules: Each vProg operates as an independent state machine, managing its own accounts, storage, and gas metering. Developers can define custom rules and scopes, promoting modularity akin to “LEGO-inspired” building blocks. This sovereignty prevents interference between programs, while built-in mechanisms like ScopeGas charge precisely for cross-vProg interactions, mitigating externalities such as spam or resource abuse. ✅Computation DAG: Mirroring Kaspa’s underlying blockDAG, this dependency graph tracks data flows and execution order across vProgs. It enables parallel processing and precise cost allocation, ensuring that referenced data remains accessible and transactions finalize atomically within the same block. ✅ Synchronous Composability: Unlike asynchronous models that introduce delays or non-atomicity, vProgs facilitate real-time interactions between programs. Cross-vProg calls settle instantly on L1, fostering unified liquidity and eliminating the need for bridges or fragmented rollups. This is achieved through dependency scoping, where only relevant data is shared, optimizing parallelism.
27
228
12
717
49,632
Daily Dose of Doc 👨‍⚕️ The cryptocurrency and blockchain market exhibited a clear recovery over the past 24 hours, with total market capitalization reclaiming the $3 trillion level after an influx of approximately $110 billion. Overall sentiment improved from extreme fear to cautious optimism, supported by oversold conditions and positive fundamental developments. Trading volumes ranged between $122 billion and $162 billion, while DeFi total value locked rose to between $262 billion and $273 billion. Liquidations remained elevated at $213 million to $385 million, predominantly affecting short positions. Major assets recorded gains, led by Bitcoin rising 1.5–1.8% to approximately $88,200, Ethereum advancing 3.9–4.9% to around $2,935, Solana climbing 5.2–5.7% toward $140, and XRP surging nearly 9% to $2.24. Among notable performers, #Kaspa continued its strong momentum with a further 20% increase, fueled by growing excitement and positive news surrounding the rapid proliferation of vProgs across its ecosystem. Other standout movers included Sui up nearly 12%, Ethena +13%, and several mid-cap and meme tokens posting triple-digit percentage gains. On the infrastructure front, the Monad mainnet officially launched with over half of its MON token supply locked for staking, while Wormhole Labs introduced Sunrise DeFi to enable same-day listings on Solana. MetaMask Mobile expanded its functionality to include perpetual futures trading for more than 150 tokens and U.S. equities with up to 40x leverage. Grayscale received NYSE approval for Dogecoin and XRP ETFs, marking another milestone in institutional product expansion. Regulatory developments were mixed but included a favorable SEC no-action letter confirming the utility status of a Solana-based dePIN token. Institutional outflows persisted, however, with digital asset funds recording $1.9 billion in net redemptions last week amid the broader monthly drawdown. Overall, the combination of technical rebounds, new mainnet launches, ETF approvals, and sustained ecosystem momentum—particularly in high-throughput networks such as Kaspa—contributed to a constructive 24-hour period for the cryptocurrency and blockchain sector. What are vprogs and why is Kaspa rallying (at last) 🧑🏼‍💻 —>
2
10
1,694
sky.𐤊 retweeted
Kaspa’s runtime architecture achieves scalability not by optimizing block-level throughput, but by rethinking the role of blocks entirely. Instead of treating state transitions as discrete batches that must be processed sequentially, Kaspa models them as a continuous stream of causally-related transactions, with blocks serving only as logical markers that define the boundaries of possible reorgs. This shift in perspective moves the performance bottleneck away from "how fast can we process everything inside a block" toward "how can we parallelize all currently known tasks across the entire DAG". When a block contains a spike of non-parallelizable work, traditional blockchains must stall until the block is fully processed. Kaspa does not. Because unrelated transactions can be scheduled immediately - even those belonging to future blocks - the system avoids idle CPU cycles and eliminates the classic straggler problem. Most existing DLT architectures tightly couple block production with state commitments, proofs, or other finalization steps, making their execution model inherently sequential. Even if they support some parallelism within a block, they still wait for a block to finish before moving on to the next one. This introduces unnecessary latency and forces the runtime to juggle responsibilities that are orthogonal to efficient workload distribution. Kaspa’s strict separation of concerns allows the entire execution model to collapse into a minimal, expressive, and highly generic framework - small enough to run any ACL (access-control list) enabled VM at essentially bare-metal performance. Its design models causal dependencies at the lowest hardware-relevant level, enabling an execution flow that is: - completely lock-free - free of WAL flushes or global sync barriers - based entirely on eventual consistency This results in a simpler, more scalable, and far more hardware-efficient architecture than anything deployed in blockchain systems today. In effect, Kaspa does for distributed ledgers what TensorFlow and CUDA Graphs did for machine learning: it exposes a parallel execution model that can scale seamlessly with modern hardware, turning theoretical throughput into practical reality (the 64000 TPS that Solana achieves in the lab let's bring that to practice). I am extremely excited about this as this is exactly what I always wanted to build with IOTA and now it's finally done. We are still working on implementing the higher levels of abstraction like designing a capability based linear type system abstraction for state management and resource access that gets rid of the need for manual capabilities wiring like in SUI and there is still a bit of work left but I don't think that you will ever be able to build a more scalable architecture than directly modeling the causal structure of state changes down to the lowest hardware layer. Kaspa is going to melt faces my friends and it's going to be so much better that it will be impossible to ignore! And it's such a simple API with Rayon level abstraction ... I am seriously getting a nerd-gasm just looking at the code 😅: github.com/hmoog/kas-l2/blob… This goes out to KEF and the entire community: Thank you so much for allowing me to take part in this journey - this really feels like coming home! 🥰
113
464
78
1,266
156,882
Kaspa’s Path to Zero-Knowledge Smart Contracts In the evolving landscape of blockchain technology, Kaspa stands out for its innovative approach to scalability and functionality. At the heart of its next phase is vProgs—verifiable programs designed to enable zero-knowledge smart contracts. This concept moves beyond traditional on-chain execution models, leveraging off-chain computation and cryptographic proofs to maintain a lightweight Layer 1 (L1) while unlocking sophisticated programmability. Drawing from ongoing research and development, including Kaspa’s recently released yellow paper, this post provides a structured overview of vProgs, their architecture, challenges, and potential impact. Kaspa’s Unique BlockDAG Architecture Kaspa’s core strength lies in its block-directed acyclic graph (blockDAG) structure, governed by the GHOSTDAG consensus protocol. Unlike linear blockchains, this design allows parallel block creation, delivering high throughput and rapid block times—often under one second. This efficiency is essential for vProgs, as it supports the timely submission and verification of proofs without compromising network performance. An upcoming enhancement, the DAGKnight upgrade, further refines this by reducing latency and accelerating finality. In a DAG environment, where minor reorganizations (reorgs) can occur, DAGKnight ensures that state commitments remain reliable, enabling vProgs to anchor securely to the L1 without excessive delays. vProgs represent a departure from monolithic virtual machines (VMs) that execute all logic on-chain. Instead, they emphasize modularity and efficiency: Each vProg maintains its own logic and state. Transactions explicitly declare their intended read and write sets, providing transparency into data interactions.. The L1 sequences commands but does not perform computations. Execution occurs off-chain, where the vProg processes inputs and generates a zero-knowledge (ZK) proof attesting to correct execution. The L1’s role is limited to validating the ZK proof, ensuring integrity without storing or running the full program. This preserves Kaspa’s L1 as a lean settlement layer. The ultimate objective is synchronous composability—allowing vProgs to interact seamlessly in real time, fostering an ecosystem of interdependent applications. To avoid vendor lock-in, vProgs accommodate diverse programming languages and VMs. Interoperability is achieved via a standardized interface for proofs and input/output (I/O), enabling one vProg to invoke another regardless of underlying technology. Finally, vProgs extend ZK proofs to include failure states—such as crashes, gas exhaustion, or infinite loops—preventing stalled transactions and maintaining liveness. For applications requiring confidentiality, vProgs facilitate calls between programs without exposing sensitive data. This is accomplished through cryptographic commitments: one vProg commits to an output privately, which the next uses as input. A chain of proofs ultimately verifies end-to-end consistency without data leakage. Kaspa’s combination of blockDAG, proof-of-work consensus, and DAGKnight provides the ideal substrate for vProgs: rapid inclusion, stable anchoring, and verifiable execution. This synergy positions Kaspa to host high-throughput, privacy-preserving applications—ranging from DeFi protocols to AI-driven oracles—while preserving L1 simplicity. Kaspa’s trajectory merits close attention. If you are out want to be a @UpholdOTC client, we have an in-depth report for you available now, why Kaspa is a game changer you don’t want to miss. Best, Doc [email protected]
40
345
21
849
47,391
sky.𐤊 retweeted
🤯 Kaspa 粉絲必看!Vprogs 大師班重點整理 (by @michaelsuttonil ) 各位 Kaspa 夥伴們,我剛消化完 Michael Sutton 長達 1.5 小時的 Vprogs 大師班訪談,內容實在太震撼了!這不只是一個新功能,這可能將徹底改寫 DeFi 和智能合約的遊戲規則。 我為大家整理了 Kaspa 粉絲最想知道的重點,這就是 Kaspa 未來的藍圖! 1. 什麼是 Vprogs?它不是傳統的 L2! 簡單來說,Vprogs 可以被理解為「微型 Base Rollups」[03:30]。 L1 (Kaspa) 負責核心工作: Kaspa L1 充當「單一排序器 (Sequencer)」、資料可用性 (DA) 層與結算 (Settlement) 層。 鏈下執行,鏈上驗證: 所有的智能合約計算都在鏈下 (off-chain) 執行,但會透過 ZK 證明 (有效性證明) 在 L1 上進行驗證。 這代表 L1 保持極致輕量,同時又能安全地賦能複雜的應用。 2. Vprogs 的殺手鐧:同步可組合性 (Synchronous Composability) 這就是 Vprogs 完勝以太坊 L2 生態的關鍵。 以太坊 L2 的痛點: 流動性碎片化 (Fragmented Liquidity)。你在 Optimism 上的 Uniswap 和在 Base 上的 Uniswap 是完全獨立的資金池。 Kaspa 的解決方案: 由於 Kaspa L1 是唯一的規範排序器 (Canonical Sequencer),所有 Vprogs 共享一個統一的全局狀態。 最終實現: 統一流動性 (Unified Liquidity)! 這代表一個 Vprog (例如 DEX) 可以和另一個 Vprog (例如借貸協議) 在一筆交易中「原子化地」[08:11] 互動,就像它們都在 L1 上一樣。這使得建立一個統一的「資產中心 (Asset Hub)」[27:42] 成為可能,徹底告別流動性孤島。 3. Vprogs 的巨大野心:超越單一 VM Vprogs 的目標不是選擇「一個」虛擬機 (VM) 稱霸。 它的設計是VM 虛擬機無關的 (VM-agnostic)。這意味著: 來自 Solana 生態 (懂 Rust) 的開發者 來自 以太坊生態 (懂 Solidity) 的開發者 他們未來都可以使用自己熟悉的「模板」在 Kaspa 上建構 Vprogs!這將極大地降低開發者門檻,吸引全球人才。 4. L1 的秘密武器:「計算 DAG (Computational DAG)」 你可能會想:如果 L1 不執行合約,它如何管理這一切? 答案是:計算 DAG (CDAG)。 廚房的比喻: Michael 用了一個很棒的比喻。把 Vprogs 想像成一個大廚房,有很多廚師 (Vprogs) 在處理共享的食材 (狀態)。 CDAG = 中央任務圖表: L1 上的 CDAG 就像是掛在冰箱上的「中央任務圖表」[55:07]。它不實際烹飪 (執行),但它精確地追蹤「哪個廚師 (Vprog) 在什麼時候、讀取或寫入了哪些食材 (狀態)」。 L1 的真正工作: L1 的工作是監管 (Regulate) 這個 CDAG,確保每個 Vprog 的「計算範圍」和成本都在限制內。這能防止某個「吵鬧的鄰居」(高流量 Vprog) 拖垮整個系統,實現真正的主權 (Sovereignty)。 5. 為什麼 Vprogs 能無限擴展?完美的激勵機制 Vprogs 的擴展性來自一個巧妙的市場驅動機制:證明的頻率 (Proof Frequency)。 問題: 如果 ZK 證明太久才提交一次 (例如一天一次),Vprogs 之間的依賴關係會變得極度「糾纏 (Entangled)」[01:12:11],最終導致每個 Vprog 都必須運行所有其他 Vprogs 的數據,系統崩潰成一個「臃腫的 L2」。 Vprogs 的解法: Vprog 的營運方 (dApp) 有強烈動機去支付 Prover (證明者) 更頻繁地提交證明。 為什麼? 頻繁證明 = 依賴關係被「打破」,保持系統輕量。 更便宜的可組合性 = 吸引更多用戶流量。 更多流量 = 該 Vprog 能賺取更多手續費。 這是一個由 Vprog 自身利益驅動的、主權的 (Sovereign) 擴展飛輪! 總結:這就是 Kaspa 的宏大願景 Michael 強調,這一切都源於 Yonatan (Kaspa 創辦人) 在 2020 年就看到的「以太坊碎片化問題」[32:43]。Kaspa 的目標從一開始就是要正確地解決這個問題。 Vprogs 正在解決區塊鏈的「互操作性困境 (Interoperability Dilemma)」[37:14],提供一個真正同步、可組合且無需信任的系統。 身為社群,我們能做什麼? 就是教育!理解 Vprogs 的強大之處,並把這些資訊傳播出去。 Kaspa 的未來,就是 DeFi 的未來。 #Kaspa #KAS #Vprogs #MichaelSutton #DeFi #智能合約 #ZK #Rollups #Layer2 #統一流動性 #區塊鏈
🚨 NEW Episode w @michaelsuttonil vProgs MasterClass (MUST WATCH) Full Youtube - youtu.be/xHlOcR1x2tU CC @hashdag @FreshAir08 In this exclusive 90-minute deep-dive, Ankit sits down with @michaelsuttonil, Co-Author of #KASPA #vProgs, for the most comprehensive explanation of vProgs (Verifiable Programs) to date. This isn't just another crypto interview - it's a masterclass in next-generation blockchain architecture. This is the conversation that will define how we think about blockchain scalability, liquidity fragmentation, and the future of decentralized applications. vProgs represent #Kaspa's answer to what many consider blockchain's greatest unsolved problem: the fragmentation crisis. While Ethereum's rollups trap developers and users in isolated silos (Base, Arbitrum, Optimism), vProgs create a unified, one-dimensional space where programs can synchronously compose while maintaining sovereignty. @michaelsuttonil breaks down complex concepts like #basedrollups, canonical ordering, #computationalDAGs, and #synchronouscomposability into understandable explanations. Whether you're a developer evaluating blockchain platforms, a researcher studying L2 solutions, or an investor trying to understand #Kaspa's technological edge, this episode provides the clarity you need. What makes vProgs revolutionary? Unlike traditional L2s that require trust assumptions and complex bridging, vProgs inherit L1 security directly, eliminate censorship risks, and create true unified liquidity through atomic composability. The experience? As Michael explains, it should feel "as if programs are on L1" despite executing off-chain with ZK proof verification. TOPICS DISCUSSED: vProgs Fundamentals - What they are and why they're called "verifiable programs" instead of smart contracts Single Sequencer Architecture - How Kaspa L1 enables synchronous composability that fragmented L2s cannot achieve. Based Rollups Superiority - Why having all roles on L1 eliminates trust assumptions and inherits full security Ethereum's Fragmentation Problem - The "failure supernova" that inspired Kaspa to design differently from day one One vs Two-Dimensional Liquidity - Why current L2s trap users in bundles and how Vprogs solve this Unified Liquidity & Asset Hubs - Creating a single liquidity space without bridges or fragmentation L1 Experience on L2 - How atomic composability makes off-chain execution feel native• Multiple VM Support - Supporting different virtual machines (Solana-style, EVM-adapted) as templates Validity Proofs vs Zero-Knowledge - Clarifying the cryptographic architecture behind vProgs Sovereignty + Composability - Balancing program independence with seamless communication ComputationalDAG - The breakthrough that made the entire vision click into place -------------------- This video is for educational purposes only and not financial advice. Always conduct your own research before engaging with blockchain projects or investments. #vProgs #kaspa #kaspa #kaspacurrency #kaspaupdates #kaspaecosystem #kaspanews
9
48
139
6,955
I have not been asked repeatedly what I think of OG bitcoiners selling their stash. Especially because those were the people who used to say things like 1 BTC = 1 BTC or no nonsense like never sell. If I had made billions of dollars by holding BTC for 13 years, I would certainly sell some to buy myself some new office chairs. Jokes aside, there are several reason reasons why OG crypto holders are selling. Number one is to buy back them in the form of ETFs, which offer incredible tax advantages with current rules, especially in the US. It is also a way of legitimizing heat to hidden stashes. The second reason is that they have realized that the real revolution isn’t Bitcoin but Blockchain, which is being used in every industry. There are therefore many other projects that promise greater returns than bitcoin, which is still lacking a widespread use case. It certainly didn’t become the E cash payment system Satoshi envisage it to be. And in times of political uncertainty, gold is still the only save haven even more so often ETFs and institutional adoption have turned bitcoin into a risk asset. You live and learn. You can see this clearly with the diminishing CAGR. A declining CAGR suggests a shift in the primary investment thesis, gradually moving away from buying Bitcoin purely for its explosive, high-CAGR growth. Instead, it strengthens the argument for Bitcoin as an instrument of value preservation with high, but more moderate, returns and as a hedge against traditional financial systems failures and fiat. That is the reason why many bitcoiners is see opportunities elsewhere, and why pundits and investors like Cathie Wood have recently lowered their price targets. This maturity is accelerated by events like the launch of spot Bitcoin Exchange-Traded Funds (ETFs), which bring in large, institutional capital that is generally less volatile than retail-driven speculative flows, thus dampening extreme price swings and contributing to a lower, steadier growth rate. As the CAGR (reward) decreases, investors must carefully consider the asset's risk (volatility): A good investor looks at risk-adjusted returns, often measured by the Sharpe ratio. If the return continues to fall while the volatility (risk) remains high, the Sharpe ratio will decline, making the investment less attractive relative to its risk. The goal for a maturing asset is for its volatility to also decline, which some sources suggest is happening, to maintain a competitive risk-adjusted return. The space is ever-evolving, and in the next phase, it will be crucial to pick the right project. The distinction between bitcoin and altcoins is no longer relevant. In fact, the term alternative coin was coined by bitcoin fanatics in the early days in order to disparage competing crypto project. I say let’s get rid of it all together and concentrate on identify those projects that will change the world and avoid those that will likely fail. Not just the world of finance, but also trade, insurance, industry, etc.. I recently spoke to a select panel of former bitcoin maxis who are now diversifying into chains like @Avalanche for their AI adoption, @peaq for the machine industry, or some of the artificial intelligence projects, having realized that AI is nothing without blockchain. Some projects create entire new ecosystems such as $TAO for example. And even though I still don’t like the technology and philosophy behind Solana, it too is attractive to some investors. Then there is $SUI and $KAS … The old-style linear model was briefly extended by layers, but innovations like DAGs or Kaspa’s #BlockDAG make early copycats of Ethereum look like fax machines in the age of WhatsApp. We are in an exciting tech space with room for many projects, it’s not a question which football team you support. Do not be alarmed by some OG’s selling parts or all of their holdings. They are just growing out of adolescent maximalism.
25
52
6
204
17,317
Replying to @binance
@binance, Thanks for including me in the top 100 blockchain people list, appreciate the signal! I must decline the Dubai invite though. I do not wish to disrespect, but many of the award voters are avid kaspians who rooted for my kaspa status at least as much as for my research. Let them win or count me out. Crypto has turned from a euphoric cypherpunk project to a house-friendly casino. You may not be the culprit, but as a top player you hold the lion’s share of the responsibility to correct this, and the October crash your USDe oracle glitch helped trigger adds to what needs to be addressed. There are three classes of crypto, as @mert put it recently: commercial crypto, casino crypto, cypherpunk crypto. <<Binance should hold a privilege policy for the latter.>> A TBTF CEX should know better and play a different game with hardcore crypto projects. When binance lists a green frog three weeks post its “launch” but skips a fair-launched-Nakamoto-Consensus-100ms-upgrade-ATH-top-20-the-only-nonbitcoin-marathon-mined project, this is not merely binance rationally calculating; it is also binance molding the market in a way that is alas misaligned with the roots of the movement. You may feel that kaspa’s sovereign money thesis is boring – that bitcoin is already money and that implementing an internet-speed bitcoin is useless - fine. Wrong but fine. But what’s the thesis for the green frog? Money is a classic chicken-and-egg product. It is a scam up until one moment before tipping point, “most of the value comes from the value that others place in it.” Considering your resources and influence, I think it's safe to say you can serve as both the egg and the chicken and make it worth your while to push sound attempts towards tipping point. @cz_binance tweeted recently that “strong projects will be listed.” But binance is part of what defines "strong", it bears responsibility for the market’s compass and impulse and definition of strong. It is not a read-only entity. Binance listing fees are legit, they are just unfit for category cypherpunk. Kaspa devs and early supporters fairly mined less than half what satoshi and hals mined. We don’t have a 20% ZEC-style founders’ reward or protocol-enforced dev fund; this is not a jab at ZEC and the wonderful @Zooko, who was crashing in my car on a late Thursday back in the low ZEC MC days – if somebody deserves to win it is zooko – but assuming binance is not taking a maxi bet, it should revisit its relationship with hardcore crypto. We are here through bull and bear, ICOs NFTs XYZs; and we are the source of confidence that restores faith and capital inflow post meme-induced or CEX-induced crashes. Please fix this. Thanks again, hashdag cc @michaelsuttonil Exhibit A: Binance Innovation Zone Exhibit B: 10 bps Nakamoto Consensus
The Blockchain 100 winners are here! See who made the list of top crypto creators. Thank you for voting & celebrating the future of blockchain education. Check the results 👇 binance.com/en/square/blockc…
2,769
4,193
1,148
8,739
3,593,900
💡想法:#kaspa 主网架构不改变的情况下,目前只想到这两种办法能让kas撤出交易所,但这需要多少时间呢?到哪一步了!#kas #kaspa $kas $kaspa
1
1
2
338
Dear crypto, It starts and ends with txn ordering. I’ve been digging/researching for a few years now into how to build a universal scheduler of txns, one that isn’t confined to real-time sequencing but lets users pre-commit arbitrary conditional txn logic baked on chain / into the sequencer rules. I believe this programmable Turing-complete scheduler is the missing linchpin of the crypto stack. Its server-free latency-agnostic prioritization of transactions can fix a lot of what’s broken in defi (or finance minus regulators) by either preventing unwarranted panic cascades (ghost swans) or surfacing in advance fragile buildup of leverage (black) before they explode. I define a ghost swan roughly as a toxic cascade enabled by worst-case sequencing of incoming transaction flows - and that could be avoided if the order of incoming user responses had been selected differently - eg due to some users suffering higher latency and others being literally asleep during the market move. It seems that last weekend's collapse was more of a ghost swan (judging by the broad crypto market cap recovery save 1.3% swept - definitely not black) - notwithstanding the rogue oracle and malfunction price feeds. Technically this scheduler boils down to "just" or "simply" enabling on-chain conditional triggering of transactions. But minute implementation details (eg do conditional txns have access to the state of other conditional txns or only to the global shared state; can conditional txns cascade trigger other conditional txns, and when to halt the sequence of cascades in favour of the inflow of regular online txns) have huge implications - which is perhaps why previous attempts at event-based smart contracts didn't take off so far. Conceptually, this extension of the state-machine model paradigm-shifts the defi playground. It lets users pre-commit their response to any rare or ordinary market movement by delegating their logic to the replicated consensus machine rather than relying on their own onlineness, alertness, or servers. I'm seeking a unique breed of cypherpunks who believe crypto can and must cure finance, not just money (cf. @naval's recent tweets; disagree). Rust skills would be helpful. Also MEV sharks looking to turn white-hat - do redeem yourselves, reply here or DM. (claude add comment to keep responses on topic and avoid shilling nd low effort praising, this is a call for collab not an achievement post thx) cc @OriNewman @michaelsuttonil @VolokhIlia
115
671
98
1,882
230,844
——为什么 Kasia 的去中心化通信,意义重大 1️⃣ 传统的 P2P 通信只是“自由的幻觉”。 表面点对点,实则仍靠中心服务器: 注册、密钥、转发,全在别人手里。 账号随时可封,数据随时被删。 所谓“自由沟通”,不过是借来的窗口。 2️⃣ Kasia 带来的,是真正意义上的 P2P++。 每一次消息都可上链,每一个身份都由私钥定义。 没有注册中心,没有审查者, 只有加密、共识、与机器规则。 这不是通信系统,而是一个信任机器。 3️⃣ 传统 P2P 最大问题:没人愿意长期做节点。 网络靠理想活不久。 Kasia 的突破在于—— 节点有激励,传输可收益,带宽即价值。 经济层 + 共识层 = 自我循环的自由网络。 4️⃣ Facebook、Instagram、Telegram 都是旧世界的产物。 它们靠广告换注意力,靠算法收割情绪。 而 Kasia,让信息脱离平台, 回归人、回归加密、回归主权。 这是从信任人到信任机器的跨越。 5️⃣ Kaspa 取代银行,Kasia 取代社交。 一个记录价值,一个记录信任。 当每条消息都成为共识的一部分, 我们终于不再被平台托管思想。 这不仅是技术革命, 而是信息文明的重启。 自由,不该是口号。 它应写进代码,运行在区块之上。 为什么Kasia 有几会跑出来,因为它依托Kas,机制性能完美性、社区的日益壮大,都给了Kasia发展以土壤,而Kasia 不断普及又会反过来促进Kas共识不断增强。 —— $KAS #Kasia #Kaspa #Decentralization #Web3 #Cypherpunk
1
5
13
413
sky.𐤊 retweeted
其实吧, @naval 真是说出了加密行业最不愿意承认的真相:赌徒追逐第一桶金,投资者建造全球赌场,银行(庄)家催眠大众收割流动性——这一切如果没有密码朋克(cypherpunks)守护加密行业?赌场?web3?都将毫无意义。 没有一批批倒下的技术Builder的“粉饰”,哪有什么大赌场的抽水生意经,又怎会有Crypto接轨华尔街的太平盛世。 如果不是一批批技术Builder前赴后继地推进技术创新,Crypto早就沦为纯粹的击鼓传花游戏。这每个人都懂的道理,只是不知为何,Crypto世界如今成了一个大型剧场,大家小心翼翼守护着利益,都在台面演,水下搞! 请记住,如果没有密码朋克守护的那个“遥不可及”梦想——这一切都只是泡沫,都只能是泡沫。 换句话说,整个Crypto行业,它不是"暴富系统",不是“投机工具”,不是“提款通道”。。。是缘于中本聪的一个简单纯粹的梦想。那现状演绎至如此绝望,只是身在局中的“我们”,偏离了这一梦想,以“暴富之名”? 真的暴富了也算!祝福朋友们。但是,存量博弈,咋可能没有输家?曾经大家身边那些心怀极客梦想的Builder,曾经那些追逐去中心化梦想的Holder,都哪里去了?留下满场的Trader要怎么继续这游戏? 讽刺的是,作为硅谷互联网创业与投资领域的大咖,Naval的这条推文,大多数韭菜解读成喊单 $ZEC 是过于狭隘了,这背后对“密码朋克文化缺失”的呼吁,才是我们应该关注的重点。 有个朋友跟我说了句话,我觉得真TM在理:真理掌握在“上帝”手里,但乌合之众总是优先被“凯撒”吸引,以“救世主之名”。
Crypto is… Desperate gamblers chasing their first bag. Investors funding the buildout of the global casino. Bankers hypnotizing the masses to collect their vig. …all meaningless and ephemeral without the cypherpunks, who defend the dream of encrypted and unstoppable cash.
51
56
10
344
106,997
Kasia — encrypted. decentralized. fast. Now live on Google Play. play.google.com/store/apps/d…
37
137
28
448
86,094
sky.𐤊 retweeted
Proof of nothing vs Proof of Work. Daily transactions: Visa | ■■■■■■■■■■■■ 757M Master | ■■■■■■■■■ 392M Kaspa | ■■■■■■ 158.4M Solana | ■■ 100M Visa & Master Card = trust Solana = when running Kaspa = trustless (math + PoW)
On October 5, 2025, the Kaspa network processed over 158 million transactions in a single day, nearly matching Bitcoin’s total transactions for the entire past year. According to data from YCharts and Glassnode, the Bitcoin network processed approximately 160 million transactions between October 5, 2024, and October 4, 2025 (inclusive).
4
61
2
290
10,400
sky.𐤊 retweeted
另:厚望 @justinsuntron 早日让 $kas 登陆@HTX_Global!
This quoted post is unavailable.
60
95
27
367
80,771
sky.𐤊 retweeted
🔥 WHAT IS KASPA & WHAT MAKES IT SPECIAL? @kaspaunchained $KAS stands out in the world of PoW L1 blockchains and not just for its speed... Here's everything you need to know about the upstart L1 ⬇️ bsc.news/post/kaspa-blockcha…
15
46
1
233
12,793
sky.𐤊 retweeted
🚀 Tangem’s Weekly Swap Highlights 🚀 $XRP — @Ripple $SOL — @solana $BNB — @BNBCHAIN $ASTER — @Aster_DEX $KAS — @kaspaunchained The tokens driving the most swap volume (in + out). Do you see your pick on the list?
31
26
7
213
41,679
Kaspa just broke a record everyone In ALL of crypto Retweet!!! TAG SPREAD THE WORD we also have smart contracts on sound money 🤣🤣🤣🤣
76
564
52
1,185
84,245
With the upcoming DAGKNIGHT protocol Kaspa improves over Bitcoin's trust model by remaining secure under chaotic internet, removing the 10 minute latency assumption. eprint.iacr.org/2022/1494 Continuously validating nodes -- many (kasnodes.com). Full-history-IBD-and-store-nodes not native protocol citizens, TB/year would fill up quickly. Default operation mode pruned, default IBD mode SPV-like, using FlyClient+MLS primitives to prove heaviest "chain". Other protocols that improved over Bitcoin while still optimizing for same puritan model, eg GrinMW, didn't take off. Apparently Bitcoin remains king for many good reasons
28
363
30
1,126
75,038