mm-near

Results 16 issues of mm-near

Currently when you call near --generate-key --seedPhrase a b c .. It will create 2 implicit keys (one with the seedPhrase and the other one with random value) - which...

We should have a metric that tracks the 'health' of the client actor (this would have been helpful in debugging yesterday's issue). What I'd suggest - is having a metric...

T-node

As we're entering Phase 1 of sharding (with Chunk-only producers) - all the validators have to explicitly track all the shards (by setting the proper config option). This will no...

A-chain

we already have config.json - which is read at startup. We should also create another config (dynamic.json?) that would be read after each change, without having to restart the node....

testnet_retrospecive_10_2022

We should add a link from the main debug page - where we show the binary version - to the github commit. This would nicely show what code is running...

testnet_retrospecive_10_2022

Currently last blocks page only shows the 'current canonical chain'. We should also add information about blocks that are built on top of the last final block but are not...

testnet_retrospecive_10_2022

We can reject the block if the pool is full. We should mark it clearly in the debug page.

After this PR, you'll be able to verify the JSON proof that you've received from calling EXPERIMENTAL_light_client_proof using: ``` ./neard verify-proof --json-file-path foo.json ```

Currently last blocks page is showing the incorrect chunk producer in case of missing chunks. If the block was missing at height X, at height X+1, the chunk might come...

testnet_retrospecive_10_2022

Currently only 'main' page does it - but we should add such 'top bar' on all the debug pages (without this, with many tabs open, you can easily get confused...

testnet_retrospecive_10_2022