Node Public Interfaces Team Weekly Update - 2021-09-03

[frol]

The update from the last week is here: #4751

Let us know in the comments about the most exciting update this week!

Brief Summary

This week Node Interfaces team has been helping METABUIDL buidlers, future FT/NFT users, and Indexer Framework users.

Highlights:

• near-jsonrpc-client-rs is shaping to its first version!
• FT and NFT support in Indexer for Explorer is one of our top priorities these days
• Indexer-as-a-Service PoC is shaping up

Results

• indexer-for-explorer

  • Released 0.9.2 (hotfix) as it was failing on testnet because of wrong AccountId type in indexer serializer (@khorolets)
    fix: Change receiver_id type to String to be compatible with nearcore near-indexer-for-explorer#160

• nearcore

  • Investigated the incident breaking betanet and canaries (PR which assumed that top level accounts creation is the same on all networks, while there is a divergence between mainnet and others) (@chefsale with the chain team)
  • Investigated nearcore licencing (kudos to @austinabell!)
    chore: Add MIT and Apache licenses and update crate licenses #4732
  • Refactor to using more appropriate internal struct naming for both the EXPERIMENTAL_changes and EXPERIMENTAL_changes_in_block methods to clear up confusion (@miraclx)
    refactor(jsonrpc-primitives): use more appropriate identifiers around changes-related RPC structs #4754
  • Ensure all Rpc*Response / Rpc*Error types implement Deserialize (@miraclx)
    refactor(jsonrpc-primitives): ensure impl Deserialize on all public jsonrpc-related types #4770
  • Deduplicate BlockReference from near-jsonrpc-primitives. It already exists in near-primitives (@miraclx)
    refactor(jsonrpc-primitives): deduplicate BlockReference #4769
  • Remove stale references to near-runtime-utils (@miraclx)
    chore: remove stale references to near-runtime-utils #4774

• near-jsonrpc-client-rs

  • Renamed providers repo from near-api-rs to near-jsonrpc-client-rs, indicative of a lower-level client that higher-level interfaces (like near-api-rs) can be built upon (@miraclx)
    chore: rename crate to near_jsonrpc_client near-jsonrpc-client-rs#5
  • Redesign the client interface, allowing the generation of both RPC + HTTP endpoints on the same client. (@miraclx)
  • Revise each method signature, ensure the return types are equivalent to their counterparts in near-jsonrpc. (@miraclx)

• indexer-service

  • PoC of Indexer as a service document is published on the NEAR Forum Indexer as a service. Proof of concept - Projects - NEAR Forum (@khorolets)
  • Set up frontend for project (@shelegdmitriy)

• meta

  • Supported METABUIDL Hackathon participants! ❤️
  • Migrated near_rewards to the right RPC endpoint (@chefsale) :partyparrot:
    fix(rpc): use the correct RPC endpoint URL khorolets/near_rewards#9

Challenges & Blockers

• FT/NFT support. We want to have a discussion about that; join us in Zullip and/or reach out to @telezhnaya if you have any thoughts:
  • Some popular FT/NFT contracts do not follow NEPs strictly. It's better to know about each of the contract. Please share FT/NFT contracts if you know some and you think it's important to support them in Explorer and Wallet, we will analyze them.
  • FT/NFT NEPs do not fix minting/burning methods. It heavily affects the way of collecting data.

Action Items

• indexer-for-explorer:

  • Work on FT/NFT support (@telezhnaya)
    feat: add ft, nft aggregated tables near-indexer-for-explorer#153

• nearcore

  • Migrate buildkite pipelines to reasonable names (@chefsale)
  • Remove client re-export from near-jsonrpc and relegate the near-jsonrpc-client to dev-dependency only. (@miraclx)
  • Look into Query ViewState with with non-existing account id and invalid prefix does not return error as expected #2793, since strict AccountId's introduction addresses this, cleanup the cases and close linked issues. (@miraclx)

• near-jsonrpc-client-rs

  • Use a trait, implemented on all Rpc*Request structs to simplify the design and prune boilerplate. (@miraclx)
    • Resolve the use of the same Rpc*Request structs by multiple RPC methods. (e.g broadcast_tx_async and broadcast_tx_commit both using RpcBroadcastTransactionRequest) (@miraclx)

• indexer-service

  • Implement PoC (contracts side) as described in the document on the forum (@khorolets)
  • Organize a call with Pingbox authors about combining efforts in Indexer as a service (@khorolets @frol)
  • Implement indexer-service node (@khorolets)
  • Finish sketching the main page (@shelegdmitriy)
    https://www.figma.com/file/kc2Gnb333T98IyMslKhezC/Indexer-Service-Contract-UX-draft?node-id=0%3A1