<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nested Transactions on Time Friend</title><link>https://time-friend.com/en/tags/nested-transactions/</link><description>Recent content in Nested Transactions on Time Friend</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 02 Sep 2026 13:30:14 +0400</lastBuildDate><atom:link href="https://time-friend.com/en/tags/nested-transactions/index.xml" rel="self" type="application/rss+xml"/><item><title>From the '1 TPS' Joke to 'Unlimited Scaling': What Cardano Actually Changed</title><link>https://time-friend.com/en/archive/cardano-dijkstra-technical-core/</link><pubDate>Sun, 30 Aug 2026 09:30:00 +0000</pubDate><guid>https://time-friend.com/en/archive/cardano-dijkstra-technical-core/</guid><description>&lt;p&gt;The last article covered where Cardano is going and why to believe it. This one zooms in on the hardest parts: &lt;strong&gt;what Dijkstra actually changes, and how it produces &amp;ldquo;unlimited scaling&amp;rdquo; and &amp;ldquo;two-minute settlement.&amp;rdquo;&lt;/strong&gt; I&amp;rsquo;ll tie the whole piece to one question — where exactly is a consensus chain&amp;rsquo;s bottleneck?&lt;/p&gt;
&lt;h2 id="the-ceiling-every-chain-hits-one-formula"&gt;The ceiling every chain hits: one formula&lt;/h2&gt;
&lt;p&gt;Nearly every public chain is bound by the same physical constraint: &lt;strong&gt;a new block must be seen by the network quickly.&lt;/strong&gt; The reasoning chain is short: a block is the vehicle of consensus, and the whole network extends the same ledger. If a block is too big and takes too long to propagate, some nodes will produce the next block before seeing it, two branches grow at once, and the chain forks. So a protocol must choose between &amp;ldquo;big blocks&amp;rdquo; and &amp;ldquo;frequent blocks,&amp;rdquo; and throughput gets locked into &amp;ldquo;block size ÷ block time&amp;rdquo; — any chain that builds its security on global synchronization is stuck with this formula.&lt;/p&gt;</description></item></channel></rss>