|
18 | 18 | em{font-style:italic} |
19 | 19 | </style> |
20 | 20 | <h1>#jam:polkadot.io</h1> |
21 | | -<p><small>last updated 2025-05-22 03:31 UTC</small></p> |
| 21 | +<p><small>last updated 2025-05-23 03:31 UTC</small></p> |
22 | 22 | <p><a href='room_log.txt'>⇩ plaintext</a> · <a href='../../'>⇦ all rooms</a></p> |
23 | 23 | <hr> |
24 | 24 | <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> <span class='u' style='color:#d0709e'>johnjiao123</span>: </div> |
@@ -5374,6 +5374,7 @@ <h1>#jam:polkadot.io</h1> |
5374 | 5374 | <div class='msg reply'><a class='ts' href='#$T1x78DC9nL1x2KvLb0zZrpnx5_OjdTjKYXMdmTrQocE'>#</a> <a class='ts' name='$T1x78DC9nL1x2KvLb0zZrpnx5_OjdTjKYXMdmTrQocE' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$T1x78DC9nL1x2KvLb0zZrpnx5_OjdTjKYXMdmTrQocE' target='_blank'>2025-01-26 17:21</a> <span class='u' style='color:#c65779'>dave</span>: 3. Build bundle and exported segments, erasure code both, calculate the root from the shards as per the GP. For importing a segment you need the erasure root of the WP that exported it, not the root of the WP that is importing it, so there is no circularity there</div> |
5375 | 5375 | <div class='msg'><a class='ts' href='#$DjtbTD4TjRm5rmo5znmCbge8lXljHHxHKmvPeE-oqhE'>#</a> <a class='ts' name='$DjtbTD4TjRm5rmo5znmCbge8lXljHHxHKmvPeE-oqhE' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$DjtbTD4TjRm5rmo5znmCbge8lXljHHxHKmvPeE-oqhE' target='_blank'>2025-01-26 18:14</a> <span class='u' style='color:#2962d0'>luke_jamixir</span>: So the WP that exported it, do I get it's erasure root from the corrodponding WR (on chain, accumulated already) or? </div> |
5376 | 5376 | <div class='msg'><a class='ts' href='#$zxNo5wLyDppjzrNnUlccv-o3LGQFq4mkEUUgKycXd3M'>#</a> <a class='ts' name='$zxNo5wLyDppjzrNnUlccv-o3LGQFq4mkEUUgKycXd3M' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$zxNo5wLyDppjzrNnUlccv-o3LGQFq4mkEUUgKycXd3M' target='_blank'>2025-01-26 18:54</a> <span class='u' style='color:#c65779'>dave</span>: Yes, you will need to get it from the WR. The assumption is that nodes will maintain a database mapping SR to ER, which they will do by monitoring WRs that are included on chain</div> |
| 5377 | +<div class='msg reply'><a class='ts' href='#$SX9tMHGUMkk0Yu0Ibjsl_8yTXWNFCnsELw_bu4TsMpM'>#</a> <a class='ts' name='$SX9tMHGUMkk0Yu0Ibjsl_8yTXWNFCnsELw_bu4TsMpM' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$SX9tMHGUMkk0Yu0Ibjsl_8yTXWNFCnsELw_bu4TsMpM' target='_blank'>2025-05-22 11:43</a> <span class='u' style='color:#73caa8'>dvladco</span>: Do we also need to keep a mapping of work-report hash to segment-root? in case the import segment is referenced by work-report hash? Also to me it looks like these dictionaries are part of the state, is there a plan to add this in the state, or is this a minor implementation detail?</div> |
5377 | 5378 | <div class='msg'><a class='ts' href='#$mhWYLUEm8lOUS9vDbY6i6biUqTABt-hLe4XspjaPEXc'>#</a> <a class='ts' name='$mhWYLUEm8lOUS9vDbY6i6biUqTABt-hLe4XspjaPEXc' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$mhWYLUEm8lOUS9vDbY6i6biUqTABt-hLe4XspjaPEXc' target='_blank'>2025-01-26 19:33</a> <span class='u' style='color:#48d03d'>tomusdrw</span>: FYI: I've built a web app to encode/decode JAM objects: <a href="https://papi.fluffylabs.dev" rel="noopener" target="_blank">https://papi.fluffylabs.dev</a> it's a fork of an amazing papi-console, so most of the credit should go there - I just plugged in the JAM codec. Hope you'll find it useful. <span class="edited">(edited)</span></div> |
5378 | 5379 | <div class='msg'><a class='ts' href='#$KWkzt81Ws2Px7EUdZK8qwLIym7vOHz_paF0KaRfiYpE'>#</a> <a class='ts' name='$KWkzt81Ws2Px7EUdZK8qwLIym7vOHz_paF0KaRfiYpE' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$KWkzt81Ws2Px7EUdZK8qwLIym7vOHz_paF0KaRfiYpE' target='_blank'>2025-01-27 00:51</a> <span class='u' style='color:#2962d0'>luke_jamixir</span>: > <@dave:parity.io> Yes, you will need to get it from the WR. The assumption is that nodes will maintain a database mapping SR to ER, which they will do by monitoring WRs that are included on chain |
5379 | 5380 |
|
@@ -8177,6 +8178,29 @@ <h1>#jam:polkadot.io</h1> |
8177 | 8178 | my current strategy is disable the check and allow alt_name mismatched with the parsed dns name, anybody met this 'problem' as well? <span class="edited">(edited)</span></div> |
8178 | 8179 | <div class='msg reply'><a class='ts' href='#$rGepN3Z-uTaaWauIs91L7ya3MI7FFRD-RHUwXjPntpU'>#</a> <a class='ts' name='$rGepN3Z-uTaaWauIs91L7ya3MI7FFRD-RHUwXjPntpU' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$rGepN3Z-uTaaWauIs91L7ya3MI7FFRD-RHUwXjPntpU' target='_blank'>2025-05-21 08:38</a> <span class='u' style='color:#c65779'>dave</span>: I recently added a section to the SNP doc which precisely defines how the alt-name should be derived: <a href="https://github.com/zdave-parity/jam-np/blob/main/simple.md#alternative-name" rel="noopener" target="_blank">https://github.com/zdave-parity/jam-np/blob/main/simple.md#alternative-name</a></div> |
8179 | 8180 | <div class='msg reply'><a class='ts' href='#$zULwxjNHJtxlijpTy4kV5IQSOc_neo_KoSlRFOxib7M'>#</a> <a class='ts' name='$zULwxjNHJtxlijpTy4kV5IQSOc_neo_KoSlRFOxib7M' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$zULwxjNHJtxlijpTy4kV5IQSOc_neo_KoSlRFOxib7M' target='_blank'>2025-05-21 08:42</a> <span class='u' style='color:#be2950'>clearloop</span>: thanks! I had ignored this formula since I thought I have already implemented it correctly > <</div> |
| 8181 | +<div class='msg reply'><a class='ts' href='#$H9Ynd9HoRjfI4V0vpaZ0z-An7QHXoG02vqT0JEi5nq0'>#</a> <a class='ts' name='$H9Ynd9HoRjfI4V0vpaZ0z-An7QHXoG02vqT0JEi5nq0' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$H9Ynd9HoRjfI4V0vpaZ0z-An7QHXoG02vqT0JEi5nq0' target='_blank'>2025-05-22 11:58</a> <span class='u' style='color:#be2950'>clearloop</span>: any ideas about |
| 8182 | + |
| 8183 | +<pre><code class=''>ede7gocrx5435my626w74zmwejyzqw3wvuvwtnzu4sz2lwib4kxaa@127.0.0.1:40005: Disconnecting: Misbehaviour: Malformed jam_node::sync::message::Announce: Could not decode `Announce::header`: |
| 8184 | + Could not decode `Header::parent`: |
| 8185 | + Could not decode `HeaderHash.0`: |
| 8186 | + Not enough data to fill buffer |
| 8187 | +</code></pre> |
| 8188 | + |
| 8189 | +we're communicating with the latest polkajam node on osx, for the <code>up0</code> steps in spacejam: |
| 8190 | + |
| 8191 | +1. send \[0\] to open the stream ✅ |
| 8192 | +2. wait for the handshake from polkajam ✅ |
| 8193 | +3. send the handshake from spacejam to polkajam ❌ |
| 8194 | + |
| 8195 | +the handshake message from spacejam follows \[length, encoded\_handshake\], but it seems polkajam is trying to decode the handshake from spacejam as a block announcement |
| 8196 | + |
| 8197 | +if we skip handshake and enter the announcement loop, we'll get |
| 8198 | + |
| 8199 | +<pre><code class=''>DEBUG jam_node::net::peer_manager ede7gocrx5435my626w74zmwejyzqw3wvuvwtnzu4sz2lwib4kxaa@127.0.0.1:55443: Static(BlockAnnouncement) stream closed: First receive killed (Dropped) by local, then transmit killed (Dropped) by local |
| 8200 | +DEBUG jam_node::net::peer_manager ede7gocrx5435my626w74zmwejyzqw3wvuvwtnzu4sz2lwib4kxaa@127.0.0.1:55443: Peer disconnected with reason: Unknown: stream reset by peer: error 1 |
| 8201 | +</code></pre> <span class="edited">(edited)</span></div> |
| 8202 | +<div class='msg reply'><a class='ts' href='#$pABWxBR_j3jSf96sY07MmIaqTlpPeRDv_XHL8AvdgYc'>#</a> <a class='ts' name='$pABWxBR_j3jSf96sY07MmIaqTlpPeRDv_XHL8AvdgYc' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$pABWxBR_j3jSf96sY07MmIaqTlpPeRDv_XHL8AvdgYc' target='_blank'>2025-05-22 12:11</a> <span class='u' style='color:#be2950'>clearloop</span>: or we need to embed this handshake in connection level, but we can decode handshake from polkajam in the stream of up0 )) <span class="edited">(edited)</span></div> |
| 8203 | +<div class='msg reply'><a class='ts' href='#$34A622yO5vdXGNbY1UEw7K1fFDkNYZsn9SQQfMRs34o'>#</a> <a class='ts' name='$34A622yO5vdXGNbY1UEw7K1fFDkNYZsn9SQQfMRs34o' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$34A622yO5vdXGNbY1UEw7K1fFDkNYZsn9SQQfMRs34o' target='_blank'>2025-05-22 14:04</a> <span class='u' style='color:#c65779'>dave</span>: FWIW you should do (2) and (3) concurrently, and you should only do (1) if you are the one that opened the stream. But I don't think either of these is your issue 😅</div> |
8180 | 8204 | <div class='msg'><a class='ts' href='#$Rv8VyAW47t0gbaSsOFbiwvFCQTHrVDXqMeHF5wINWNs'>#</a> <a class='ts' name='$Rv8VyAW47t0gbaSsOFbiwvFCQTHrVDXqMeHF5wINWNs' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$Rv8VyAW47t0gbaSsOFbiwvFCQTHrVDXqMeHF5wINWNs' target='_blank'>2025-05-21 07:52</a> <span class='u' style='color:#d2b557'>dvdplas</span>: What I have in mind: |
8181 | 8205 | 1. Scaffold a new CoreVM app template, ready to build |
8182 | 8206 | - Is there a name for apps build on top of CoreVM? |
@@ -8254,3 +8278,20 @@ <h1>#jam:polkadot.io</h1> |
8254 | 8278 | <div class='msg'><a class='ts' href='#$b83NaDJO4tQEpBmW3AZRG4wH_Sb0DFxKtBF5lLIuMPQ'>#</a> <a class='ts' name='$b83NaDJO4tQEpBmW3AZRG4wH_Sb0DFxKtBF5lLIuMPQ' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$b83NaDJO4tQEpBmW3AZRG4wH_Sb0DFxKtBF5lLIuMPQ' target='_blank'>2025-05-21 18:05</a> <span class='u' style='color:#ce4c29'>nicholasonchain</span>: We would to see polkajam support new JIP-2 methods to fetch a block and one or more of C(1)-C(15) state by header hash to support basic explorer -- is this possible?</div> |
8255 | 8279 | <div class='msg'><a class='ts' href='#$lFAmpOOCKw16D-99lkAhh0Tp8FLw7Lgx1PMTi2LSYDg'>#</a> <a class='ts' name='$lFAmpOOCKw16D-99lkAhh0Tp8FLw7Lgx1PMTi2LSYDg' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$lFAmpOOCKw16D-99lkAhh0Tp8FLw7Lgx1PMTi2LSYDg' target='_blank'>2025-05-21 19:15</a> <span class='u' style='color:#c65779'>dave</span>: Certainly possible, can't promise a time frame though these things should be easy to add</div> |
8256 | 8280 | <div class='msg'><a class='ts' href='#$_ra2qhqSm9u1T6jTs7HXo4son_XUZWD5crre0Png1K0'>#</a> <a class='ts' name='$_ra2qhqSm9u1T6jTs7HXo4son_XUZWD5crre0Png1K0' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$_ra2qhqSm9u1T6jTs7HXo4son_XUZWD5crre0Png1K0' target='_blank'>2025-05-21 21:34</a> <span class='u' style='color:#c67452'>sourabhniyogi</span>: Is there an env variable to turn on pvm trace execution logs in <code>polkajam</code> to compare with our own binaries logs, e.g something like <a href="https://github.com/jam-duna/jamtestnet/blob/main/traces/reports-l0/00000003.log#L2-L3135" rel="noopener" target="_blank">this</a>?</div> |
| 8281 | +<div class='msg reply'><a class='ts' href='#$SXUT1DMl_jPSSDjHG018DI4-cFqHfuD_dCi019ohj8s'>#</a> <a class='ts' name='$SXUT1DMl_jPSSDjHG018DI4-cFqHfuD_dCi019ohj8s' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$SXUT1DMl_jPSSDjHG018DI4-cFqHfuD_dCi019ohj8s' target='_blank'>2025-05-22 10:12</a> <span class='u' style='color:#da5c80'>jan</span>: Force the interpreter backend and set <code>RUST_LOG=polkavm=trace</code></div> |
| 8282 | +<div class='msg reply'><a class='ts' href='#$Gv90OsJP8sFM4R8VLPM9j2yxubqwqCVXWHDZ1k717To'>#</a> <a class='ts' name='$Gv90OsJP8sFM4R8VLPM9j2yxubqwqCVXWHDZ1k717To' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$Gv90OsJP8sFM4R8VLPM9j2yxubqwqCVXWHDZ1k717To' target='_blank'>2025-05-22 12:53</a> <span class='u' style='color:#c67452'>sourabhniyogi</span>: Awesome -- any way to get the registers to appear at least some of the time, or other options? |
| 8283 | + |
| 8284 | +<pre><code class=''>2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter Compiling block: |
| 8285 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [4]: 8206: charge_gas |
| 8286 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [5]: 8206: sp = sp + 0xfffffffffffffd00 |
| 8287 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [6]: 8210: u64 [sp + 0x2f8] = ra |
| 8288 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [7]: 8214: u64 [sp + 0x2f0] = s0 |
| 8289 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [8]: 8218: u64 [sp + 0x2e8] = s1 |
| 8290 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [9]: 8222: i32 s0 = a0 + 0 |
| 8291 | +2025-05-22 20:22:42 tokio-runtime-worker DEBUG polkavm::interpreter [10]: 8224: jump 9459 if s0 == 0 |
| 8292 | +2025-05-22 20:22:42 tokio-runtime-worker TRACE polkavm::interpreter::raw_handlers -> resolved to fallthrough |
| 8293 | +2025-05-22 20:22:42 tokio-runtime-worker TRACE polkavm::interpreter::raw_handlers [4]: charge_gas: 6 (49999999 -> 49999993) |
| 8294 | +</code></pre></div> |
| 8295 | +<div class='msg'><a class='ts' href='#$QfhOkwtpWUwRdDpK7hzJpTNMOW2_JN2XQM3BWq8mOGg'>#</a> <a class='ts' name='$QfhOkwtpWUwRdDpK7hzJpTNMOW2_JN2XQM3BWq8mOGg' href='https://matrix.to/#/!wBOJlzaOULZOALhaRh:polkadot.io/$QfhOkwtpWUwRdDpK7hzJpTNMOW2_JN2XQM3BWq8mOGg' target='_blank'>2025-05-22 13:34</a> <span class='u' style='color:#c65779'>dave</span>: Proposal for a standard secret key derivation method here: <a href="https://github.com/polkadot-fellows/JIPs/blob/c888a85736b18261b848224a5e242e6a42f8e4ff/JIP-5.md." rel="noopener" target="_blank">https://github.com/polkadot-fellows/JIPs/blob/c888a85736b18261b848224a5e242e6a42f8e4ff/JIP-5.md.</a> We're planning to make PolkaJam follow this method. Note that we intend to use the same method for deriving keys from on-disk seed files as for deriving the "dev chain" validator keys. Currently different methods are used which means for example it is not currently possible to use an on-disk seed file for a dev chain validator. |
| 8296 | + |
| 8297 | +This change _will_ cause breakage, in particular the dev account keys listed here will change: <a href="https://docs.jamcha.in/basics/dev-accounts." rel="noopener" target="_blank">https://docs.jamcha.in/basics/dev-accounts.</a> The new dev account keys are listed in the "test vectors" section at the bottom of the linked doc. Apologies for any hassle this causes, hopefully this change will make things simpler and easier in the long run though!</div> |
0 commit comments