Node Public Interfaces Team Weekly Update - 2021-10-01 #4929
frol
started this conversation in
Node Public Interfaces
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The previous update is #4876. See more engineering updates posted on gov.near.org
Brief Summary
Blockers
NFT NEP-171 require having minting/burning interface NEPs#254
Result
Explorer received performance and stats improvements:
Display Circulating Supply chart on Stats near-explorer#740
SELECT
statements should run faster! (@telezhnaya 🎉)We are close to cut the first proper release of near-jsonrpc-client-rs! (@miraclx 💪)
near-jsonrpc-primitives
when building with theadversarial
feature flagfix(jsonrpc-primitives): fix adversarial-related compilation errors #4884
chore: mark all but a few crates private (unpublishable) #4909
chore: remove deprecated IsSyncing variant check #4905
refactor(methods): promote use of traits, double down on the macro complexity near-jsonrpc-client-rs#11
response.handler_error()
for extracting the specific method call error type directly, skipping the longer pattern matching syntax where possible, defaulting to the latter if notnear/near-jsonrpc-client-rs@854695a
near/near-jsonrpc-client-rs@c18dff3
.error_data
value doesn't naturally deserialize to the error type, default to attempt deserializing the older.data
field.operations
Add tutorial to live-run.md to up a localnet sdk-docs#49
Revert "Fix bug in config.js for localnet" near-api-js#696
Action Items
[OBJECTIVE] Remove friction from building dApps
[KEY RESULT] FT / NFT information is easily available for the developers:
[KEY RESULT] Release near-jsonrpc-client-rs (@miraclx):
near-jsonrpc-primitives
to it's own dedicated crate to alleviate the use ofnear-network
which unconditionally depends onnear-store
. (@miraclx)nearcore
along withnear-jsonrpc-client-rs
. (@miraclx)client
re-export fromnear-jsonrpc
with the newnear-jsonrpc-client-rs
and drop the oldnear-jsonrpc-client
inside nearcore. (@miraclx)Rpc*Request
and theirRpcMethod
,RpcHandlerResult
andRpcHandlerError
implementations into the newjsonrpc-primitives-adversarial
crate.[KEY RESULT] Maintain 99.(9)% uptime for Indexer for Explorer:
start-from-interruption
on indexer-for-explorer as it is too slow for no reason (@khorolets)near-indexer-for-explorer#168
[OBJECTIVE] Give users better insights about the current and historical status of the network
refactor(frontend): Move telemetry to database near-explorer#753
Objectives and Key-Results for Node Interfaces Team in 2021Q4
Node Interfaces Team (@khorolets @telezhnaya @miraclx @shelegdmitriy @chefsale @mhalambek) lead by @frol and in collaboration with DevPlatform leader @jberrytech defined the following objectives and key-results for the upcoming quarter:
O1: Make RPC service reliable for the customers while keeping nodes infrastructure sustainable
KR: To be announced 😄
O2: Support success of DevConsole
KR1: Provide knowledge, experience and hands-on help with DevConsole bootstrap
O3: Support success of custodial wallets
KR1: Provide expertise and quick fixes to RosettaRPC on demand
O4: Remove friction from building dApps
KR1: FT / NFT information is easily available for the developers
KR2: Indexer-as-a-Service MVP is available for the early-adopters
KR3: Release near-jsonrpc-client-rs
KR4: Indexer Framework projects fully support nearcore sharding
KR5: Maintain 99.(9)% uptime for Indexer for Explorer
KR6: Indexer for Explorer storage is performant under the estimated load [aspirational]
O5: Give users better insights about the current and historical status of the network
KR1: Explorer features the status of NEAR network clearly and without downtimes
KR2: Explorer enables efficient exploration of NEAR history
Beta Was this translation helpful? Give feedback.
All reactions