Node Public Interfaces Team Weekly Update - 2021-07-23

[frol]

Last week update is here: #4537

Brief Summary

This week we spent designing and exploring the future directions and the solutions we want to implement.

• Heads up! 1.20.0 release is happening on Monday (2021-07-26), so it will be rolled out on mainnet after two weeks running 1.20.0-rc on testnet
• Contribute to Explorer self-identification!
  [2021 UX Reevaluation] – User Research near-explorer#668
  [2021 UX Reevaluation] – Design Discovery / Exploration near-explorer#665
  [2021 UX Reevaluation] – Competitive Analysis near-explorer#664
• Check out new NEAR CLI design proposal!
  https://gov.near.org/t/new-near-cli-design-proposal/3616

Results

• nearcore
  • Benchmarked JSON RPC using drill (benchmark tests might be extended) (@khorolets)
    GitHub - near/jsonrpc-benchmark: NEAR JSON RPC benchmark results
  • Revised the AccountId PR to ensure it doesn't cause a protocol change (@miraclx, @frol)
    refactor: Introduce strictly typed and assuredly validated AccountId #4440
• explorer
  • Explorer gets more high-level self-identification through analysis and collecting user feedback (HUGE props to @reefoh 🎉)
    [2021 UX Reevaluation] – User Research near-explorer#668
    [2021 UX Reevaluation] – Design Discovery / Exploration near-explorer#665
    [2021 UX Reevaluation] – Competitive Analysis near-explorer#664
  • Finalized PR of merging Validators, Proposals, and Pools into single tab (@shelegdmitriy)
    feat(frontend): Expose whole pools list near-explorer#661
• near-cli-rs
  • New NEAR CLI design proposal! (@frol provided insights collected while working on near-cli-rs, and @volovyk-s with @DiscRiskandBisque compiled the new proposal)
    https://gov.near.org/t/new-near-cli-design-proposal/3616
  • Improved the human-readable output of a transaction used for review before sending the transaction to the network (@FroVolod)
    print-transaction:updated printing for transaction near-cli-rs#35

Challenges & Blockers

• indexer-for-explorer
  • How to structure the account_changes table, so the events order is easily-derivable? (@telezhnaya and @frol are working on it)
    Do we miss some balance changes? near-indexer-for-explorer#77 (comment)
  • (an old-standing issue) How to re-structure the database to include the transactions that have the same hash? (@telezhnaya and @frol stuck unable to make the final decision there, and de-prioritized it for now)
    Some rows are missing because of transaction hash collisions near-indexer-for-explorer#84

Action Items

• nearcore
  • Following in the light of refactor(neard): decouple into individual crates #4292 and refactor: Introduce strictly typed and assuredly validated AccountId #4440, we decouple some core crates into smaller specialized crates so they're lightweight, independently publishable and ultimately, reusable outside of nearcore (@miraclx)
  • Once all nits are addressed, finally publish near-account-id refactor: Introduce strictly typed and assuredly validated AccountId #4440 (@miraclx)
  • Follow up on the JSON RPC benchmark with the partners providing NEAR RPC as a Service (@khorolets and @janewang)
• indexer-for-explorer
  • Introduce logic to stop retrying to store data after N attempts and report the situation somewhere we can find it and handle (@khorolets)
• explorer
  • Finalize displaying active and deleted access keys on accounts page (@shelegdmitriy)
    feat(frontend): Display active access keys on Account Details page near-explorer#675
  • Complete API implementation to view average fees (@shelegdmitriy)
    feat(frontend): Implement API endpoint to view fees near-explorer#682
• near-cli-rs
  • Finalize the NEAR CLI design (DevPlatform and Node Interfaces team joint effort)
• operations
  • Integration of grafana and pagerduty via terraform (@mhalambek)
  • Wallet cloudflare integration to enable China usage (@mhalambek)
  • Intiate split of RPC services per product, example wallet has it's own rpc endpoint and machines, same for bridge and so forth (@mhalambek)