Alexander Skidanov

@mikhailOK I assume that if we fix it, there's no way to upgrade to it other than a hard fork?

I see, the proposal is that if the handshake is old, we expect the GenesisId to be just the genesis block hash, otherwise the properly computed genesis id?

also note that nightly heavily relies on the relative paths, so if we change the dirs, nightly needs to be changed accordingly.

For (1), if I'm reading this function correctly https://github.com/near/nearcore/blob/416b38ce10f844b4f1936d18759d33a159d9f571/chain/chain/src/chain.rs#L1475 The issue still exists (the function is called from `process_block`, and it doesn't appear to check anywhere that the epoch is...

In EVM the keys to the account storage are 52 bytes, where the first 20 bytes are the contract address, and the last 32 bytes are the slot, which are...

Anton confirmed that the self-destruct is responsible for wiping out the storage.

In this particular implementation I do the same thing that they suggest to do in the paper: send to both children, and use the weighted average of them as the...

@evgenykuzyakov pre-compiled contracts don't have to be in-memory, right? If not, I like the approach.

> So we can still have the chain stay on whatever version was last decided on while rolling back a feature by changing what it means to be at that...

> What are the difference in time loading from disk compiled code vs loading WASM + compiling? WASM is also loaded from disk. We can measure precisely, but generally the...