Node Public Interfaces Team Weekly Update - 2021-11-19

[frol]

The previous update is #5157. See more engineering updates posted on gov.near.org

Brief Summary

• Explorer received a number of optimizations and it is much faster now! Thanks @shelegdmitriy and @telezhnaya for their hard work
  https://explorer.near.org/accounts/near - the number of incoming and outgoing transactions can now actually be displayed on accounts with a high number of transactions 🎉
  

• NFT Events standard is ready for adoption! Please, upgrade your contracts to get support of your NFT contracts on Wallet and Explorer

  • Since the last update we deployed NFT support in Indexer-for-Explorer no testnet and mainnet! See assets__non_fungible_token_events table in the database
    feat: add NFT events support near-indexer-for-explorer#169
  • As a follow-up, we invite to join the discussion about FT Events standard:
    FT NEP-141 require having minting/burning interface NEPs#271

• All the indexers were migrated to the latest NEAR protocol version (nearcore 1.22) with sharding enabled on mainnet!

Blockers

None!

Result

(Acronyms: O - Objective, KR - Key Result)

• O1: Support success of DevConsole

  • KR1: Provide knowledge, experience and hands-on help with DevConsole bootstrap
    • Continued the discussion about near-cli-rs UX (@frol)
      New commands layout near-cli-rs#75
  • KR2: Developer tools should support RPC-as-a-Service authorization mechanism
    • Updated near-jsonrpc-client-rs's authentication mechanism to support the new scheme, but also making it a bit more generic and easily implementable by downstream users (@miraclx)
      feat: make auth interface more generic near-jsonrpc-client-rs#26

• O2: Support success of custodial wallets

  • KR1: Provide expertise and quick fixes to RosettaRPC on demand
    • Clarified the design of Rosetta implementation in nearcore around account balances representation (@frol)
      Rosetta API and near CLI are reporting 2 different balances for given account #5086
    • Clarified the design of Rosetta implementation in nearcore around constructing complex transactions (@frol)
      Rosetta does not allow to withdraw all available funds  #5129

• O3: Remove friction from building dApps

  • KR3: Release near-jsonrpc-client-rs (while we have the published version on crates.io already, we need to finish some of the work for the future releases)

    • Revised publishing automation, finalizing on a better system. Thanks to @matklad for his contributions (@miraclx)
      re: chore: ready workspace for publishing #5130
    • Introduced a new version field to the workspace manifest that globally dictates the versions of all crates in the workspace (@miraclx)
      pksunkara/cargo-workspaces@master...miraclx:grouping-versioning-and-exclusion#files_bucket
    • Ensure CI tags the commit responsible for a version bump, and appropriately pushes the tag to GitHub making cross-referencing between crates.io and github easy. Thanks to @chefsale for his time, helping with CI push authorization (@miraclx)
      https://github.com/near/near-ops/pull/657
    • Fix serialization of the chunk request causing errors. Thanks to @nikurt for spotting this (@miraclx)
      near/near-jsonrpc-client-rs@f40ad74
    • Refactored to ensure each method call does not consume the client. Helps avoid unnecessary cloning where possible. Thanks to @nikurt for pointing that out (@miraclx)
      near/near-jsonrpc-client-rs@471a53b
    • Relicensed to MIT + Apache-2.0 (@miraclx)
      near/near-jsonrpc-client-rs@43aea25

  • KR5: Maintain 99.(9)% uptime for Indexer for Explorer

    • Added troubleshooting guide to near-indexer-for-explorer (handbook) (@khorolets)
      https://github.com/near/near-indexer-for-explorer/blob/f459ca7586aba91cdc31980bdbc2914bcd9391ec/TROBLESHOOTING.md
    • Created example indexer with the most frequent use case
      https://github.com/near-examples/indexer-tx-watcher-example
    • Supported indexer partners in upgrading to nearcore 1.22.0 with sharding (@khorolets @frol @nikurt @mhalambek)
    • Added timeout for public_readonly in Indexer DB (Mainnet, Testnet) (@telezhnaya)
      feat: add timeout for public_readonly role near-indexer-for-explorer#190

• O3: Remove friction from building dApps

  • KR1: FT / NFT information is easily available for the developers

    • Landed NFT support in Indexer-for-explorer on testnet and mainnet! (@telezhnaya)
      feat: add NFT events support near-indexer-for-explorer#169
    • Reviewed NFT events support in near-contract-standards (@frol)
      feat(NFT): add events to standard near-sdk-rs#627

  • KR7: Indexer for Explorer storage is performant under the estimated load [aspirational]

    • Collected the thoughts about migration from Postgres in Indexer (@telezhnaya)
      Consider global migration from Postgres near-indexer-for-explorer#189

• O4: Give users better insights about the current and historical status of the network

  • KR2: Explorer enables efficient exploration of NEAR history (navigation through history & search improvements)
    • Created ingoing transactions table in Near Analytics: required to speed up transactions counters for each account in Explorer (@telezhnaya)
      Optimize the computation of total transaction count for each account near-explorer#773
      feat: add table with ingoing transactions near-analytics#23
    • Renamed daily_transactions_per_account_count to daily_outgoing_transactions_per_account_count. With the new ingoing transactions table, previous naming could confuse the users. Be careful and update your scripts if you were using this table (@telezhnaya)
      fix: rename transactions -> outgoing_transactions near-analytics#24
    • Optimized the query of incoming and outgoing transactions count for each account along with refactoring of all queries on Explorer (@shelegdmitriy)
      refactor: Move queries to backend near-explorer#774

• [NEW] O5: Support lockup contract stakeholders

  • KR1: Document common flows of Lockup v2 and v3 contracts
    • Manually reviewed vesting termination flow of Lockup v2 contract and concluded that it works as intuition suggested (@telezhnaya @frol)
    • Clarified Lockups wiki around soft-deprecated lockup_timestamp and release_duration lockup rules that were heavily used before the Phase II launch (@telezhnaya)
      Add the info about employee's lockups, cleanup wiki#17
    • Added the test to lockup contract that the termination follows the schedule from wiki (@telezhnaya)
      https://wiki.near.org/getting-started/near-token/lockups#termination-of-vesting
      fix(lockup): add test of unlocking schedule with termination core-contracts#188