| 29 May 2024 |
 jtakalai | (clearly the indexing has stopped for unknown reason... also newly deployed contracts don't show up, which is why I noticed/care) | 11:34:29 |
|  Radha changed their display name from Radha to Radha ooo Jun 3. | 15:55:22 |
| 30 May 2024 |
 Bruce | Subscan | hi, jtakalai Thanks for report. We have reported this issue to the peaq team | 01:32:37 |
| Bruce | Subscan | Subscan will resume after the node network is restored | 01:33:20 |
| jtakalai | ok... but in general, this was the correct place to report? Do you use other chats as well? | 07:05:13 |
| jtakalai | thanks! Hope they get it sorted | 07:05:21 |
| jtakalai | I'd like to point out though, that the EVM chain RPC that they gave seems to work just fine (https://peaq.api.onfinality.io/public), it's just subscan that doesn't get updated | 07:12:27 |
| jtakalai | works again :) | 09:22:37 |
|  Keegan | W3F changed their display name from Keegan | W3F to Keegan | W3F - traveling. | 13:13:20 |
| 31 May 2024 |
 SK | 
Download image.png | 00:15:15 |
| SK | Has anyone noticed that the number displayed for the Current Price is incorrect? https://coretime-kusama.subscan.io/coretime_dashboard | 00:15:20 |
 Lark | Subscan | This issue has been resolved, thanks for your feedback | 07:48:19 |
| jtakalai | Does Subscan offer API for EVM contract verification? Bonus if it's compatible with Etherscan (because there's already tooling for it...) | 07:49:53 |
| jtakalai | In reply to @jtakalai:matrix.org
Does Subscan offer API for EVM contract verification? Bonus if it's compatible with Etherscan (because there's already tooling for it...) bonus-bonus: also detectc and handle proxy contracts like Etherscan does: https://amoy.polygonscan.com/address/0xE9C98bdE63248e58E9137Db8270D9675B9E34b93#code notice the buttons "read as proxy", "write as proxy" | 08:16:16 |
| jtakalai | relevant EIP: https://eips.ethereum.org/EIPS/eip-1967 | 08:16:53 |
| jtakalai | (i.e. if the bytecode of contract is one of specific bytecodes, then look into storage slot 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc for the "real contract" that should be verified) | 08:17:55 |
| jtakalai | In reply to @jtakalai:matrix.org
Does Subscan offer API for EVM contract verification? Bonus if it's compatible with Etherscan (because there's already tooling for it...) * bonus-bonus: also detect and handle proxy contracts like Etherscan does: https://amoy.polygonscan.com/address/0xE9C98bdE63248e58E9137Db8270D9675B9E34b93#code notice the buttons "read as proxy", "write as proxy" | 08:40:54 |
| Keegan | W3F changed their display name from Keegan | W3F - traveling to Keegan | W3F. | 11:59:19 |
|  Anton Khvorov | Nova Wallet changed their profile picture. | 14:07:29 |
|  @marekhakala:parity.io left the room. | 16:39:46 |
| 3 Jun 2024 |
|  Bill | W3F changed their display name from Bill | W3F - slow responses until 3 June to Bill | W3F. | 03:09:17 |
| Radha changed their display name from Radha ooo Jun 3 to Radha. | 03:30:14 |
| Keegan | W3F changed their display name from Keegan | W3F to Keegan | W3F - slow response - until June 10th. | 07:53:41 |
| Bill | W3F | Hi, I noticed that looking up old account balances (before Feb 2021) does not work. They show ridiculously high numbers. I believe this was due to a runtime change which changed the storage location of the balance. | 08:11:24 |
| Bill | W3F | 
Download Screenshot 2024-06-03 at 10.11.35.png | 08:11:47 |
|  David | W3F changed their display name from David | W3F to David | W3F - Slow responses until June 7. | 13:07:13 |
|  Filippo | W3F changed their display name from Filippo | W3F | Blockchain Week Rome to Filippo | W3F. | 13:34:24 |
|  Bader | W3F changed their display name from Bader | W3F @Consensus2024 to Bader | W3F. | 14:49:25 |
| 4 Jun 2024 |
| Bruce | Subscan | It seems so. I will hide this part of the data first. | 13:56:38 |
| 5 Jun 2024 |
 Yakio | Subscan | Hi Bill | W3F
Thank you for your feedback. We are currently investigating the issue. Our initial suspicion is that the problem arose due to a change in type definitions following a Polkadot runtime update, which led to issues with data parsing. We need to review the historical upgrades and correct the historical data. During this process, the affected data will be temporarily hidden and will be made available for querying once the fixes are implemented. | 07:01:17 |
