Weekly update 2021-05-20

[frol]

Last week update is here: #4303

Done

• operations:
  • released nearcore 1.19.0 on mainnet [notes: we had some complications due to migrations running about 4 hours for archival nodes] (@mhalambek)
  • cleaned up Terrafrom configs from resizing archival and RPC nodes on mainnet (@mhalambek)
  • rolled out testnet RPC terrafrom to sync up with latest module changes (@mhalambek)
• indexer-for-explorer
  • released 0.6.4 [just bumped nearcore to 1.19.0] (@khorolets)
  • updated the behavior of saving the creation receipt id for implicit accounts based on the first TRANSFER action instead of every single one fix: Handle recreation of implicit accounts properly to avoid confusion for the users near-indexer-for-explorer#107 (@khorolets)
    • migrated the data by resetting last_update_block_height to 0 in all records in accounts table and re-indexing from genesis (used mainnet-indexer-for-explorer-node3 instance for that) (@khorolets)
• nearcore:
  • progressed on the PR of decoupling neard into neard (bin) and nearcore (lib) crates (some CI checks still needs to be addressed) (@miraclx) refactor(neard): decouple into individual crates #4292
  • fixed a couple of ignored tests in neard rpc_nodes that were failing after the deprecation of query requests re-routing fix(jsonrpc): Update tests test_rpc_routing and test_rpc_routing_error in neard (no routing for query method) #4304 (@khorolets)
• docs:
  • documented EXPERIMENTAL_receipt method (jsonrpc) Document JSON RPC new EXPERIMENTAL_receipt method docs#699 (@khorolets)
  • merged the improvements of the documentation for lockup contract docs(lockup-contract): refactored README for better clarity core-contracts#144 (@telezhnaya)
  • finalized the strategy we want to use to compute the circulating supply https://github.com/telezhnaya/docs/blob/master/docs/tokens/lockup_calculations.md (@telezhnaya)
• explorer:
  • released new design of Nodes page 🎉 feat(frontend): Implementation of new design on Nodes page near-explorer#613 (kudos to @shelegdmitriy)
  • exposed protocol configuration information on Charts & Stats page feat(frontend): expose protocol configuration on stats page near-explorer#625 (@shelegdmitriy)
  • fixed a bug of missing contract details for some accounts fix(frontend): Fix contract details displaying near-explorer#629 (@shelegdmitriy)
  • hot-fixed finality status fix(frontend): Fix transaction details status near-explorer#635 (@shelegdmitriy)
  • upgraded dependencies refactor: Upgrade JS dependencies and update Next.js near-explorer#630 (@shelegdmitriy)

Plans

• nearcore:
  • expose structured errors via JSON RPC (still coming up with a decision about naming and structure to return) (@khorolets)
• near_rewards:
  • experiment with handling non-lockup accounts staking feat: As a USER I want to be able to use this app with regular account (without lockup) along with lockups khorolets/near_rewards#6 (@khorolets)
• docs:
  • finalize the documentation for lockup contract lockup: add info about whitelisting contract to README core-contracts#147 (@telezhnaya)
  • review the high-level documentation for lockup contract lockup: add vesting info, add graphs with schedule to the doc docs#691 (@frol)
• explorer:
  • implement the computation of circulating supply in JS feat(backend): Calculate circulating supply near-explorer#636 (@telezhnaya)
  • expose receipts on Block Details page Display receipts on the Block Details page near-explorer#590 (@shelegdmitriy)

Discussions

• @khorolets: We’ve started a discussion with @chefsale about the binary building for Indexer for Explorer, current builds fail with segmentation error on manually created machines (the difference is in machine types manuals are N1, automated are E2)
  Decided to reproduce the error for Sandi and leave the machine alone so he can investigate (mainnet node3 is busy, we can consider abusing node1 or node2 since automated nodes are working)
• @frol: We continue some collaboration with SingleStore, and now we have an internal SingleStore instance having a live backup of data from PostgreSQL:
• @khorolets: We don't really want to migrate from open-source PostgreSQL to a proprietary solution
  • @frol: Totally agree, we consider using SingleStore for analytical queries and allow read-only replication from it in the future.
• @mhalambek: Our PostgreSQL instances are not tuned very well
  • @frol: We want to ask around for expertise with PostgreSQL tuning