Kaspa
KAS7D price series. Open $0.03352, close $0.03905, high $0.04522, low $0.0332, change 16.52%.
Kaspa was fair-launched in November 2021 with no pre-mine, zero pre-sale, and no coin allocations, and is 100 percent community-managed. Kaspa aims to be the world's global sequencer for traditional finance and decentralized crypto markets by utilizing proof-of-work and its BlockDAG consensus protocol, GHOSTDAG. Being the world's fastest proof-of-work network, Kaspa combines five properties: (1) hard money principles, (2) Bitcoin's ethos of security-first fundamentals (boasting a security threshold of fifty percent with significant market hashrate), (3) decentralization from rapid block rate mining, (4) block speeds faster than any PoW or PoS network, and (5) smart contract development through based-rollups without fragmented liquidity. Ushering in all five properties, Kaspa is on track to fulfill Satoshi Nakamoto's vision of a digital medium of exchange while also advancing global layer-one sequencing and minuscule confirmation times dominated by internet latency (cf. chapter 6 of the the paper for some initial benchmarks). The Kaspa implementation includes a lot of cool features and subprotocols including Reachability to query the DAG's topology, Block data pruning (with near-future plans for block header pruning), SPV proofs, and later subnetwork support which will make future implementation of layer 2 solutions much easier.
A freshness-weighted mid, and the complete venue breakdown behind it.
One normalized endpoint, 1 credit per call. The responses below are this instrument’s real data.
The normalized mark, with opt-in freshness and confidence.
curl "https://api.getliaw.com/v1/prices/latest?assets=KAS"e=USD" \ -H "Authorization: Bearer $LIAW_KEY"
{ "data": [ { "asset": "KAS", "quote": "USD", "price": "0.038960000000000000", "updated_at": "2026-09-24T03:14:38.093Z" } ], "meta": { "request_id": "<request id>", "served_at": "<ISO 8601 serve time>", "count": 1 } }
Live KAS values, straight from the feeds on this page. request_id and served_at are per-request — the server fills those in.
