Mustafa Al-Bassam

Can you elaborate on why code would need to be hot loaded? The code for state transitions should be the same code defined by the app.

They should have the code (i.e. state machine) for the Cosmos app, and then they could validate the state transition fraud proof by loading an instance of the app (state...

In order for chain A to verify the state transition fraud proofs for chain B, it must have the state machine code for that chain. By default, the state machine...

>@musalbas: smart contracts can be upgraded, right? Not without hardforking unless they have upgrade keys (which everyone wants to avoid because that means the smart contract has a centralized point...

Yes, we're talking about it possibly changing after mainnet.

Specifically this: https://github.com/klauspost/reedsolomon/pull/191 cc @liamsi

We may want to consider versioning the shares in order to allow for backwards-compatibility for on-chain smart contracts or programs that need to parse the shares but are not upgradeable.

Removing namespace IDs from leaves would have implications on the ability to verify Merkle proofs in the NMT, and thus erasure coding fraud proofs, that would be have to be...

>Note: Ostraka assumes a UTXO model. Understand if the architecture can be translated to an account model or if only a subset of the proposed sharding mechanisms make sense instead....

Did you run the command to start the console client while you were in the right directory (/chainspace/chainspacecore)?