bot: update 2025-04-28

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-04-27 03:29 UTC</small></p>
+<p><small>last updated 2025-04-28 03:30 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='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>

archive/_21ddsEwXlCWnreEGuqXZ_3Apolkadot.io/room_log.txt

@@ -1,5 +1,5 @@
 # room: #graypaper:polkadot.io
-# exported: 2025-04-27 03:29 UTC
+# exported: 2025-04-28 03:30 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: 

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-04-27 03:28 UTC</small></p>
+<p><small>last updated 2025-04-28 03:30 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='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>
@@ -7402,3 +7402,10 @@ <h1>#jam:polkadot.io</h1>
 
 it even supports links to messages, threads with paddings, great work, direct and efficient <span class="edited">(edited)</span></div>
 <div class='msg reply'><a class='ts' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$UdC_hsXtHsa_eS3A_f_12yWFH7zR9GpyaA6YB6UYDy4' target='_blank'>2025-04-26 14:23</a>&ensp;<span class='u' style='color:#787fdf'>erin</span>: thank you!</div>
+<div class='msg'><a class='ts' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$eHVieXlcGdFejlwuWy17ptpAXcI_ZmyK0ugQbQHjF44' target='_blank'>2025-04-27 21:59</a>&ensp;<span class='u' style='color:#6f63cc'>decentration</span>: Just working on the pvm implementation i just want to confirm with what is the minimum requirement for M1... in the article (<a href="https://hackmd.io/@polkadot/jamprize)" rel="noopener" target="_blank">https://hackmd.io/@polkadot/jamprize)</a> it references PVM for M3 but not M1. 
+
+1. Is it enough to expose the JAM host-function interface while stubbing the RISC-V runtime?
+2. Or do we already need full RISC-V sandbox execution (load blob -&gt; run -&gt; trap -&gt; return ephemerals) in M1?
+3. If execution is required, may we rely on an existing impl such as PolkaVM as a temporary backend and postpone a custom PVM to M3?
+4. Alternatively, is all PVM work evaluated only from M3 onward?
+5. And, is there a difference between M1 and MN1? <span class="edited">(edited)</span></div>

archive/_21wBOJlzaOULZOALhaRh_3Apolkadot.io/room_log.txt

@@ -1,5 +1,5 @@
 # room: #jam:polkadot.io
-# exported: 2025-04-27 03:28 UTC
+# exported: 2025-04-28 03:30 UTC
 2024-04-20 02:08 johnjiao123: 
 2024-04-20 02:09 johnjiao123: 
 2024-05-30 21:48 nradko: Hey everyone,
@@ -7429,3 +7429,10 @@ there are a few quality of life improvements still to be done but any feedback o
 
 it even supports links to messages, threads with paddings, great work, direct and efficient [edited]
   ↳ 2025-04-26 14:23 erin: thank you!
+2025-04-27 21:59 decentration: Just working on the pvm implementation i just want to confirm with what is the minimum requirement for M1... in the article (https://hackmd.io/@polkadot/jamprize) it references PVM for M3 but not M1. 
+
+1. Is it enough to expose the JAM host-function interface while stubbing the RISC-V runtime?
+2. Or do we already need full RISC-V sandbox execution (load blob -> run -> trap -> return ephemerals) in M1?
+3. If execution is required, may we rely on an existing impl such as PolkaVM as a temporary backend and postpone a custom PVM to M3?
+4. Alternatively, is all PVM work evaluated only from M3 onward?
+5. And, is there a difference between M1 and MN1? [edited]