Name: kaspa:native
Uploaded: 2026-07-15T13:14:36.000Z
Duration: PT12.571S
Channel: Zealous Swap
Description: Zealous Swap shorts video about kaspa:native

kaspa:native

Zealous Swap

11,324 views • 1 month ago

Kaspa's Toccata hard fork is live on mainnet kaspa:native... show more

BSCN

27,684 views • 2 months ago

Kaspa prices transactions by how much permanent storage they... create A dust attack once flooded #Kaspa with tiny coin fragments that every full node must store forever. Unlike old blocks, which nodes can discard, these coin records never expire. KIP-9, a protocol rule co-authored by Kaspa's Michael Sutton, was the answer. Every transaction is charged on two scales, computation and storage, and pays whichever is higher. The storage charge climbs when value is split into small, scattered outputs, and falls to zero when coins merge into fewer equal ones. The result makes ledger bloat slow or expensive. Per the KIP's analysis, wasting 50GB of node storage in one day requires a budget of 125 million kaspa:native. On 100,000 KAS, it would take 750 years.show more

BSCN

17,378 views • 13 days ago

Kaspa nodes delete most of the chain's history by... design Bitcoin nodes store and replay every block back to 2009. #Kaspa takes the opposite approach: nodes keep only recent blocks and discard everything older than a cutoff known as the pruning point. Since the Crescendo upgrade took block production from 1 to 10 per second, that window covers roughly 30 hours of history, down from 50 before, per the official Rusty Kaspa release notes. New nodes sync from the pruning point rather than from the chain's first block. Operators who want a longer archive can set a retention period of at least two days. Every node still keeps the full ledger of unspent coins, so kaspa:native balances stay verifiable without the deleted history.show more

BSCN

23,459 views • 14 days ago

Kaspa's Toccata upgrade is seeing real use seven weeks... after activation Seven weeks after Kaspa's Toccata hard fork, the upgrade's new machinery is in visible use. Kaspalytics counts 1,196 covenant-creating transactions in the past 24 hours, with over 2,700 covenant outputs created, programmable spending rules now running natively on kaspa:native L1. The ZK side is earlier-stage: just 9 ZK precompile transactions in the same window, split between Groth16 and R0Succinct proof verifications. The clearest adoption signal sits on layer 2. Igra, the EVM-compatible L2 anchored to Kaspa, logged around 54,000 transactions in 24 hours, dwarfing every other protocol on the network, with KRC inscriptions a distant second near 1,900. Miners have moved on cleanly too: 86% of recent blocks come from node version 2.0.1, the post-Toccata release, suggesting the consensus change has settled without a lingering split.show more

BSCN

18,187 views • 19 days ago

Kaspa's kHeavyHash mining algorithm traces back to a 2019... optical proof-of-work paper #Kaspa was built to be mined on light-based chips that do not exist yet. Its proof-of-work algorithm, kHeavyHash, comes from a 2019 arXiv paper called Optical Proof of Work, whose authors wanted mining cost to sit in hardware rather than electricity. The design places a matrix multiplication step, a block of arithmetic run across a grid of numbers, between two Keccak-family hashes from the SHA-3 standard. That middle step is the part meant to run on photonic chips. In practice, kaspa:native hashrate comes from conventional ASICs. IceRiver shipped the first kHeavyHash machines in 2023 and Bitmain followed with its KS series, pushing GPUs out of contention. The optical hardware that the design anticipated has yet to reach Kaspa mining.show more

BSCN

17,929 views • 7 days ago