Vlad Frolov

@telezhnaya @shelegdmitriy Thanks for pulling these bits together! Let's keep this issue open, but overall, we should just implement the new Activity-based Account Details page, and that will address this...

> difference in protocol version changes of nightly in betanet It seems that we need to automatically build indexer-for-explorer based on nearcore commit we use for betanet (patch Cargo.toml on...

> I disagree, quite often it includes some changes in the dependencies which might not be fine with diesel :( If that breaks, it is better to be aware of...

@khorolets Let's measure it on the specific block with and without concurrency and then make the final decision.

Just for the future investigation, the recent blocks that caused slowdowns on mainnet are around [#61617473](https://explorer.near.org/blocks/Snn61AxZbci6bkRUizmwcRCCw6v8tpnJgFhDydLiEJx)

Given that natively staked balance is only useful for the staking pool accounts, and regular accounts delegate their tokens through the staking pool contract, which looks like a token transfer...

@pisomanik Those are Aurora-bridged tokens and we are surely working on adding the support with custom indexing

@telezhnaya Hmm, what is going on here? Is it by design that we close all the issues on github?

The context is in the PR description: https://github.com/near/near-enhanced-api-server/pull/40. Some contracts followed the NEP while others relied on near-sdk-rs implementation and now we need to parse both cases and align the...

@khorolets ideally, we should have looked at what was the state of those files before rewriting and why near-lake-framework-rs passed incomplete StreamMessage down the line 🧐