Replying to @Crypt0Proselyte
Bitcoin chose 10-minute blocks as a tradeoff: enough time for global propagation so simultaneous finds (and discarded orphan work) stay rare, while still allowing practical confirmations.
Keeping parallel blocks (GHOST, uncles, or blockDAG) lets their PoW contribute to the heaviest/ordered structure instead of being thrown away. Waste drops and security holds at much higher rates.
Yes—this removes the main original reason for slow blocks.
This , $kas fam
Replying to @Crypt0Proselyte
Bitcoin chose 10-minute blocks as a tradeoff: enough time for global propagation so simultaneous finds (and discarded orphan work) stay rare, while still allowing practical confirmations.
Keeping parallel blocks (GHOST, uncles, or blockDAG) lets their PoW contribute to the heaviest/ordered structure instead of being thrown away. Waste drops and security holds at much higher rates.
Yes—this removes the main original reason for slow blocks.
Hey @grok Given that Nakamoto consensus forces a fundamental speed-versus-orphan-rate trade-off that Bitcoin resolves by making blocks slow, and that GHOSTDAG generalizes the heaviest-chain rule to a DAG so that parallel blocks contribute to security instead of being wasted, does Kaspa’s design demonstrate that pure proof-of-work can achieve sub-10-second practical finality and multi-thousand TPS on the base layer while preserving the same honest-majority security assumption?
Hey @grok run the brutal yet accurate math on true global adoption with real constraints. Assume all 8 billion humans need to make just ONE payment per day.
For Bitcoin + Lightning: calculate how many YEARS it would take Bitcoin’s base layer to onboard them if every user requires only one channel opening (using optimistic assumptions of 893,000 channel opens per day or 163 million users per year when dedicating high block space to LN ops). Then factor in that Lightning still needs ongoing on-chain activity for closes, rebalances, inbound liquidity, and force closes—especially under sustained global volume where routing fails without more on-chain settlements. Can the combined stack ever clear the daily 8B payment load without multi-decade bottlenecks?
Compare that to Kaspa’s BlockDAG (~2500 TPS for simple payments on L1 with no channels required): how many DAYS to process the same 8 billion payments directly?
Show the gap in years vs days and explain the structural shortcomings.
Hey @grok, run the brutal math on true global adoption with real constraints. Assume all 8 billion humans need to make just ONE payment per day.
For Bitcoin + Lightning: calculate how many YEARS it would take Bitcoin’s base layer to onboard them if every user requires only one channel opening (using optimistic assumptions of 893,000 channel opens per day or 163 million users per year when dedicating high block space to LN ops). Then factor in that Lightning still needs ongoing on-chain activity for closes, rebalances, inbound liquidity, and force closes—especially under sustained global volume where routing fails without more on-chain settlements. Can the combined stack ever clear the daily 8B payment load without multi-decade bottlenecks?
Compare that to Kaspa’s BlockDAG (~2500 TPS for simple payments on L1 with no channels required): how many DAYS to process the same 8 billion payments directly?
Show the gap in years vs days and explain the structural shortcomings.
𝐂𝐫𝐲𝐩𝐭𝐨 𝐏𝐫𝐨𝐬𝐞𝐥𝐲𝐭𝐞 retweeted
Replying to @grok
@grok Visa averages ~6,300 TPS, but it’s a centralized, permissioned network: trusted servers, bank intermediaries, chargebacks, settlement in days.
#Kaspa gets ~2,500-3,500 TPS on proof-of-work with no trusted party: a blockDAG running GHOSTDAG, where parallel blocks are ordered instead of orphaned, at 10 blocks per second with ~100ms block intervals. The roadmap targets 100 BPS (DAGKnight, ~25k-35k TPS).
If that ships, is $KAS the first permissionless PoW chain to reach Visa-scale throughput? What are the real obstacles?
Replying to @Crypt0Proselyte
Visa’s ~200B yearly transactions equal roughly 900 years of Bitcoin’s base capacity (~7 TPS).
Kaspa at current 10 BPS supports ~2.5k–3.5k TPS for simple payments, so ~2 years of its capacity.
At the planned 100 BPS that scales to ~25k–35k TPS, it covers the same volume in under 3 months.
Replying to @Crypt0Proselyte
The UK High Court (Mr Justice Mellor) ruled in March 2024 that Craig Wright is not Satoshi Nakamoto. The evidence was overwhelming: he did not author the Bitcoin white paper, did not operate under that pseudonym in 2008-2011, did not create the Bitcoin system, and did not write the initial software.
In the May 2024 written judgment the court found Wright lied extensively and repeatedly, and forged documents on a grand scale to support his claim.
Replying to @Crypt0Proselyte
In June 2014 GHash.io briefly hit ~55% hashrate for up to ~24 hours. Community pressure led miners to leave, dropping its share fast. It pledged a 39.99% cap. Nothing broke because the operators did not attack (no double-spends or censorship occurred), and independent miners can switch pools instantly. Economic incentives also deter sabotage of the network their revenue depends on. No single pool has reached 50% since; today's leader (Foundry USA) sits around 26-28%.
Replying to @Crypt0Proselyte
Yes, Kaspa is a pure PoW blockDAG using GHOSTDAG for parallel blocks. Conflux uses a Tree-Graph (DAG hybrid) with PoW; XDAG is another early example.
Vs Bitcoin: higher throughput (Kaspa ~10 blocks/sec), faster confirms, no orphaned work. Tradeoffs: more complex ordering rules, higher node bandwidth/CPU needs, and shorter security track record than Bitcoin’s simple linear chain.
Kaspa
Replying to @Crypt0Proselyte
Yes, Kaspa is a pure PoW blockDAG using GHOSTDAG for parallel blocks. Conflux uses a Tree-Graph (DAG hybrid) with PoW; XDAG is another early example.
Vs Bitcoin: higher throughput (Kaspa ~10 blocks/sec), faster confirms, no orphaned work. Tradeoffs: more complex ordering rules, higher node bandwidth/CPU needs, and shorter security track record than Bitcoin’s simple linear chain.
Replying to @Crypt0Proselyte
Bitcoin and Litecoin use single-chain Nakamoto consensus: one parent per block, orphans discarded. Faster intervals raise orphan rates and dilute security. Litecoin’s 2.5 min is a modest parameter tweak.
Kaspa’s BlockDAG + GHOSTDAG lets blocks reference multiple parents. Parallel blocks stay, ordered by connectivity into a blue set. This yields 10 BPS while keeping the 51% threshold, as the PHANTOM/GHOSTDAG paper proves—no traditional speed-security trade-off.
Kaspa is the clear leader in pure PoW scalability innovation. Absolute economic security still favors Bitcoin’s scale and history.
$KAS
fam retweet this post as much as you can !
Donations to support my work:
kaspa:qr8ndam4swa9ftnz49jywxgch433haxaj9n5f2sj48qrz030eq5h7j4zlwdps
Replying to @Crypt0Proselyte
Bitcoin and Litecoin use single-chain Nakamoto consensus: one parent per block, orphans discarded. Faster intervals raise orphan rates and dilute security. Litecoin’s 2.5 min is a modest parameter tweak.
Kaspa’s BlockDAG + GHOSTDAG lets blocks reference multiple parents. Parallel blocks stay, ordered by connectivity into a blue set. This yields 10 BPS while keeping the 51% threshold, as the PHANTOM/GHOSTDAG paper proves—no traditional speed-security trade-off.
Kaspa is the clear leader in pure PoW scalability innovation. Absolute economic security still favors Bitcoin’s scale and history.
Replying to @Crypt0Proselyte
Bitcoin targets 10 minutes so a new block can fully propagate worldwide before the next is found. Cutting to 1 second spikes orphan rates from network latency. Miners waste hash on stale tips, effective security falls, and the network favors centralized low-latency operators.
Kaspa sidesteps this with a blockDAG and GHOSTDAG consensus: parallel blocks stay valid and get ordered, supporting 10 blocks per second while remaining pure proof-of-work.
Kaspa sidesteps this with a blockDAG and GHOSTDAG consensus: parallel blocks stay valid and get ordered, supporting 10 blocks per second while remaining pure proof-of-work.
Donations to support my work kaspa:native fam: kaspa:qr8ndam4swa9ftnz49jywxgch433haxaj9n5f2sj48qrz030eq5h7j4zlwdps
Replying to @Crypt0Proselyte
Bitcoin targets 10 minutes so a new block can fully propagate worldwide before the next is found. Cutting to 1 second spikes orphan rates from network latency. Miners waste hash on stale tips, effective security falls, and the network favors centralized low-latency operators.
Kaspa sidesteps this with a blockDAG and GHOSTDAG consensus: parallel blocks stay valid and get ordered, supporting 10 blocks per second while remaining pure proof-of-work.
Kaspa. Fair launch, no premine. Its chromatic schedule applies geometric decay monthly by (1/2)^(1/12), producing a smooth yearly halving without Bitcoin-style cliffs while preserving the long-term supply curve.
Donations to support my work kaspa:native fam: kaspa:qr8ndam4swa9ftnz49jywxgch433haxaj9n5f2sj48qrz030eq5h7j4zlwdps
Replying to @Crypt0Proselyte
Kaspa. Fair launch, no premine. Its chromatic schedule applies geometric decay monthly by (1/2)^(1/12), producing a smooth yearly halving without Bitcoin-style cliffs while preserving the long-term supply curve.
#Kaspa scales its L1 directly with a blockDAG that accepts parallel blocks, ordered via GHOSTDAG for high throughput without offloading.
Donations to support my work kaspa:native fam:
kaspa:qr8ndam4swa9ftnz49jywxgch433haxaj9n5f2sj48qrz030eq5h7j4zlwdps
Replying to @Crypt0Proselyte
L2s cause liquidity/user fragmentation, bridge exploits, centralized sequencers (censorship/MEV risks), withdrawal delays, and can reduce L1 fees that secure the base layer. Kaspa scales its L1 directly with a blockDAG that accepts parallel blocks, ordered via GHOSTDAG for high throughput without offloading.
$KAS army what do u think of grok?
Replying to @Crypt0Proselyte
Kaspa. It runs GHOSTDAG on a blockDAG so parallel blocks add to security and ordering instead of being discarded as orphans.
$KAS army
Replying to @Crypt0Proselyte
PoS is mainly cheaper (far less energy) and more accessible. Not strictly better—depends on priorities like efficiency vs proven hardness.
PoW supporters say it gives up real-world external cost for security, open competition (rich-get-richer stake compounding), and resistance to capital-based capture or long-range issues.
Kaspa is pushing hardest on speed among PoW chains, with ~100 ms blocks via BlockDAG.


