Brief Summary
- We released nearcore v1.23.0 on Mainnet, but then found out that it made validator kick-out too aggressive. Users and developers are unaffected. We missed this issue while testing on Testnet, because we miss-attributed kicked out validators to a different thing. The hotfix will be released to Testnet this week and to Mainnet the next week;
- If you have any feedback on how DevConsole should look like reach out to @josh.quintal and @tiffanygyj see contact info;
- Check out slides from the Developer Console talk at Ledger Op3n;
- JS SDK now passes all host function tests!
- @jakmeier Joined the Contract Runtime team!
Progress
- Node Experience discovered that Node.js broke near-cli-js for when using the local node;
- Node Experience added epoch info to the state viewer, improving diagnosability of our state;
- Core Tools did a bunch of cleanup for crate compliance;
- Core Tools released workspaces-rs v0.1 to crates.io;
- Developer Console did user interviewers and fixed a bunch of issues in preparation for the release;
- @piotr submitted 45 PRs with nearcore improvements;
- Core team added a counter for touched trie nodes. This will help us a lot with performance investigations of our state;
- Core team were also preparing for the next release with chunk-only producers;
- Frontier tools are adding RPC failover and redundancy into near-api-js to improve robustness of NEAR dApps;
- Contract Runtime sped up history replay by skipping trivial blocks;
- Contract Runtime added tests that diff behavior of Wasmer 0.17 and Wasmer 2;
- Contract Runtime verified that IO estimator works correctly and that weird IO behavior is due to Rocksdb caching;