bot: update 2025-06-16

Author: github-actions

archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/index.html

@@ -18,7 +18,7 @@
 em{font-style:italic}
 </style>
 <h1>#graypaper:polkadot.io</h1>
-<p><small>last updated 2025-06-15 03:38 UTC</small></p>
+<p><small>last updated 2025-06-16 03:38 UTC</small></p>
 <p><a href='room_log.txt'>⇩ plaintext</a> · <a href='../../'>⇦ all rooms</a></p>
 <hr>
 <div class='msg'><a class='ts' href='#$G0deSwnlYlCrSn5lIFL__hi6bgWVITql5VyahU4bzpI'>#</a> <a class='ts' name='$G0deSwnlYlCrSn5lIFL__hi6bgWVITql5VyahU4bzpI' href='https://matrix.to/#/!ddsEwXlCWnreEGuqXZ:polkadot.io/$G0deSwnlYlCrSn5lIFL__hi6bgWVITql5VyahU4bzpI' target='_blank'>2024-04-17 20:29</a>&ensp;<span class='u' style='color:#da6aa2'>syed</span>: <a href="https://matrix.to/#/!hyzRkDqDthePbodYFz:parity.io/$f_DMsIEcDXZegw6Sabnehzc-LrdDQkmq5MbxDDyoZxY?via=parity.io&amp;via=web3.foundation" rel="noopener" target="_blank">https://matrix.to/#/!hyzRkDqDthePbodYFz:parity.io/$f_DMsIEcDXZegw6Sabnehzc-LrdDQkmq5MbxDDyoZxY?via=parity.io&amp;via=web3.foundation</a>
@@ -6215,3 +6215,6 @@ <h1>#graypaper:polkadot.io</h1>
 
 It is surely doable, we just have to actually do it.  I think a solution between &quot;tiny&quot; (V=6, C=2) and &quot;full&quot; (V=1023, C=341) should be pursued so that N teams can pursue parallelization of requests/responses ( and various politeness concerns ) within the Toaster in pairs or something like that. <span class="edited">(edited)</span></div>
 <div class='msg reply'><a class='ts' href='#$vYH8CTysWCHFHRByiyqPnPpADgSnwYrQEvpZBY8lp8U'>#</a> <a class='ts' name='$vYH8CTysWCHFHRByiyqPnPpADgSnwYrQEvpZBY8lp8U' href='https://matrix.to/#/!ddsEwXlCWnreEGuqXZ:polkadot.io/$vYH8CTysWCHFHRByiyqPnPpADgSnwYrQEvpZBY8lp8U' target='_blank'>2025-06-13 16:46</a>&ensp;<span class='u' style='color:#c65779'>dave</span>: FWIW the full network protocol will provide a way of fetching bundles/segments directly from guarantors, as a fast path. The less fast path which is possible now is to request the shards containing original data, in which case reconstruction is just concatenation. If you need to do full reconstruction of segments it should still be possible to have only a single call into the EC library _if_ the shard indices are the same for every segment. If they&#x27;re not then I&#x27;m not sure how efficiently reconstruction can be done.</div>
+<div class='msg'><a class='ts' href='#$lAXPRX0irI_ZhYpxxdl_UAc6wej_gtJ7nPROO8WOU6k'>#</a> <a class='ts' name='$lAXPRX0irI_ZhYpxxdl_UAc6wej_gtJ7nPROO8WOU6k' href='https://matrix.to/#/!ddsEwXlCWnreEGuqXZ:polkadot.io/$lAXPRX0irI_ZhYpxxdl_UAc6wej_gtJ7nPROO8WOU6k' target='_blank'>2025-06-15 07:15</a>&ensp;<span class='u' style='color:#4036ac'>ascriv</span>: The header has a parent hash and prior state root. We need to guarantee the posterior state root of the parent block equals this prior state root. Does this mean implementations must also keep track of the posterior state roots along with headers? Otherwise it seems naively that an incoming header could point to any ancestral header as its parent </div>
+<div class='msg'><a class='ts' href='#$yXjqIrovUSJHi2fDsJXnx7nw4rbIhJp6O9MTui9Z5ZQ'>#</a> <a class='ts' name='$yXjqIrovUSJHi2fDsJXnx7nw4rbIhJp6O9MTui9Z5ZQ' href='https://matrix.to/#/!ddsEwXlCWnreEGuqXZ:polkadot.io/$yXjqIrovUSJHi2fDsJXnx7nw4rbIhJp6O9MTui9Z5ZQ' target='_blank'>2025-06-15 08:59</a>&ensp;<span class='u' style='color:#cd8957'>gav</span>: Implementations will need to be able to determine the posterior state root for any block they retain in their chain which could serve as a parent. </div>
+<div class='msg'><a class='ts' href='#$DcM50NhD_lelbXBVYeMmbKFS0lBsy1NB83rv104qH5c'>#</a> <a class='ts' name='$DcM50NhD_lelbXBVYeMmbKFS0lBsy1NB83rv104qH5c' href='https://matrix.to/#/!ddsEwXlCWnreEGuqXZ:polkadot.io/$DcM50NhD_lelbXBVYeMmbKFS0lBsy1NB83rv104qH5c' target='_blank'>2025-06-15 09:00</a>&ensp;<span class='u' style='color:#cd8957'>gav</span>: The fork-choice rule and finality ensure that this set cannot grow indefinitely (and thus that a new block cannot have a non-recent parent).  <span class="edited">(edited)</span></div>

archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/room_log.txt

@@ -1,5 +1,5 @@
 # room: #graypaper:polkadot.io
-# exported: 2025-06-15 03:38 UTC
+# exported: 2025-06-16 03:38 UTC
 2024-04-17 20:29 syed: https://matrix.to/#/!hyzRkDqDthePbodYFz:parity.io/$f_DMsIEcDXZegw6Sabnehzc-LrdDQkmq5MbxDDyoZxY?via=parity.io&via=web3.foundation
 
 2024-04-17 20:29 syed: 
@@ -6221,3 +6221,6 @@ https://graypaper.fluffylabs.dev/#/7e6ff6a/202501202501?v=0.6.7
 
 It is surely doable, we just have to actually do it.  I think a solution between "tiny" (V=6, C=2) and "full" (V=1023, C=341) should be pursued so that N teams can pursue parallelization of requests/responses ( and various politeness concerns ) within the Toaster in pairs or something like that. [edited]
   ↳ 2025-06-13 16:46 dave: FWIW the full network protocol will provide a way of fetching bundles/segments directly from guarantors, as a fast path. The less fast path which is possible now is to request the shards containing original data, in which case reconstruction is just concatenation. If you need to do full reconstruction of segments it should still be possible to have only a single call into the EC library _if_ the shard indices are the same for every segment. If they're not then I'm not sure how efficiently reconstruction can be done.
+2025-06-15 07:15 ascriv: The header has a parent hash and prior state root. We need to guarantee the posterior state root of the parent block equals this prior state root. Does this mean implementations must also keep track of the posterior state roots along with headers? Otherwise it seems naively that an incoming header could point to any ancestral header as its parent 
+2025-06-15 08:59 gav: Implementations will need to be able to determine the posterior state root for any block they retain in their chain which could serve as a parent. 
+2025-06-15 09:00 gav: The fork-choice rule and finality ensure that this set cannot grow indefinitely (and thus that a new block cannot have a non-recent parent).  [edited]

archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/index.html

@@ -18,7 +18,7 @@
 em{font-style:italic}
 </style>
 <h1>#jam:polkadot.io</h1>
-<p><small>last updated 2025-06-15 03:38 UTC</small></p>
+<p><small>last updated 2025-06-16 03:37 UTC</small></p>
 <p><a href='room_log.txt'>⇩ plaintext</a> · <a href='../../'>⇦ all rooms</a></p>
 <hr>
 <div class='msg'><a class='ts' href='#$we4SYXTHwmKn094X9Zs_7mWUOoUVh4icvVdxD83RZfs'>#</a> <a class='ts' name='$we4SYXTHwmKn094X9Zs_7mWUOoUVh4icvVdxD83RZfs' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$we4SYXTHwmKn094X9Zs_7mWUOoUVh4icvVdxD83RZfs' target='_blank'>2024-04-20 02:08</a>&ensp;<span class='u' style='color:#d0709e'>johnjiao123</span>: </div>

archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/room_log.txt

@@ -1,5 +1,5 @@
 # room: #jam:polkadot.io
-# exported: 2025-06-15 03:38 UTC
+# exported: 2025-06-16 03:37 UTC
 2024-04-20 02:08 johnjiao123: 
 2024-04-20 02:09 johnjiao123: 
 2024-05-30 21:48 nradko: Hey everyone,