Tomas Zemanovic

Results 194 issues of Tomas Zemanovic

Because we chose to separate the merkle tree from the data storage (and more specifically account storage sub-spaces), we don't have data sharing that is implied by merklelized storage. In...

question
spec

* Do we want to use the same addresses on different chains (fractal scaling, protocol upgrades) or distinguish them? * Would be better if an address from one chain is...

question
spec

set `#![warn(missing_docs)]` and add any missing doc strings in crates: * [x] shared * [ ] vm_env + vm_macro * [ ] apps * [ ] tests ┆Issue is synchronized...

documentation
refactor / code quality

consider using https://github.com/rust-lang/miri and possibly integrating in the CI ┆Issue is synchronized with this [Asana task](https://app.asana.com/0/1201757896515792/1201762933103389) by [Unito](https://www.unito.io)

prio:low
CI

Add fuzz tests for encodings and ledger inputs, perhaps using honggfuzz with https://medium.com/tezedge/how-we-utilized-fuzzing-to-improve-security-in-the-tezedge-node-and-created-an-open-source-ci-tool-92ffbd804db1 ┆Issue is synchronized with this [Asana task](https://app.asana.com/0/1201757896515792/1201763009668485) by [Unito](https://www.unito.io)

ledger
prio:low
testing

depends on #351. Delegators should be able to override the votes of the validators that they delegate to. The default validators VP should implement some logic that allows their delegators...

ledger
prio:low

The tx host environment read-only functions could re-use the logic from `vp_env` reads from posterior storage. Because VPs use a different gas meter type, it will need to be parameterized....

enhancement
ledger

We use specific storage key paths for common data types (e.g. public keys, token balances). It would be nice to come up with a way to prevent or at least...

question
spec

#417 implemented the `--stdout` option. Next, we should add a way to submit an intent from a file, e.g. something like: ```shell 1. # write a signed intent into a...

prio:low
cli
UX

Consider versioning the DB schema. Currently the RocksDB storage tree is: ```rust //! The current storage tree is: //! - `chain_id` //! - `height`: the last committed block height //!...

storage
ledger