Christopher Goes comments

Results 299 comments of


                                            Christopher Goes

Code coverage audit, rework to obtain coverage w/o large E2E tests

Hmm - in that case @batconjurer or @mariari can you clarify the concern here?

refactor WASM memory data passing with strict provenance

@tzemanovic do you know the status of this?

CI: check that there are no artifacts after e2e tests run

@tzemanovic what is the status of this?

After some epochs inflation is 0

Is that the first epoch, or some epoch in the middle?

Add more randomness to address generator

Does this need to be secure randomness? Can it be local randomness? What is the usage of these addresses?

Better logging during shielded transfers

partial duplicate of https://github.com/anoma/namada/issues/586 😁

`init-network` should be able to optionally bundle wasm files along with the network config files

Most importantly, we should check the WASM hashes against the expected ones when starting the node.

`init-network` should be able to optionally bundle wasm files along with the network config files

https://github.com/anoma/namada/pull/3119 is sufficient for the time being.

`init-network` should be able to optionally bundle wasm files along with the network config files

> shouldn't we include the wasms in the chain tar.gz? and remove the download functionality from the ledger? Otherwise we have to host infrastructure I don't think so, we can...

Governance proposals for SE

> Are we going to include NAAN in the shielded set rewards? What would we want the max inflation and target amount to be if so? @cwgoes @adrianbrink @batconjurer Yes....