Vlad Frolov

Note: we need a visual design for that. We need to review what the current Chunk model misses from the Chunk Header available from RPC. Chunk model contains: * block...

@nikurt I would like to avoid storing garbage. Please, consider to make telemetry messages well-defined

@nikurt > If the latter, that is justified by making it much easier to make changes to telemetry info. Ease of making changes can turn into a problem that clients...

This is blocked on someone thinking through how to address the issue that nearcore signs telemetry JSON text and adds the signature inside that JSON, and thus when Explorer parses...

Hmmmmm, that sounds very suspicious! There is no locked balance. Here are the RPC responses: ``` $ http post https://rpc.testnet.near.org jsonrpc=2.0 id=dontcare method=query params:='{ "request_type": "view_account", "finality": "final", "account_id": "ethonnearclient08"...

@bowenwang1996 where is it documented/announced? How can we observe it? Is it a matter of config? Will it require hard-fork to disable these rewards?

@kcole16 @corwinharrell @vgrichina @khorolets @amgando FYI, the balance may increase with incoming function call transactions due to fees paid by the caller are partially rewarded to the receiver/contract account. We...

> why do you think we should disable it? I somehow thought it was a temporary solution; now I see that it is a permanent economic incentive.

Yes, there is no actionable item at the moment

@cuongdcdev Thanks for bringing this up! It is indeed unfortunate, but in general case there is no way we can index actions based on the arbitrary function call arguments. However,...