Quantifier
Quantifier
Our current database schema consists of 80 column families. The naming conventions and encoding/decoding mechanisms for these column families lack consistency and type safety. This inconsistency makes it difficult to...
Example: `"missingStakingLedgers": [17, 18, 19]` ``` { "blockchainLength": 99999, "chainId": "5f704cc0c82e0ed70e873f0893d7e06f148524e3f0bdae2afb02e7819a0c24d1", "circulatingSupply": "350083645.840039233", "dateTime": "Sat, 15 Jan 2022 19:51:00 GMT", "epoch": 20, "slot": 3517, "globalSlot": 146317, "lockedSupply": "535677087", "minWindowDensity": 19,...
We write a lot of `format!("{}", hash.0)` when we can write the cleaner `format!("{hash}")`
- staged ledgers - `/ledgers/{state hash}` - `/ledgers/{ledger hash}` - `/ledgers/height={height}` - staking ledgers - `/staking/{ledger hash}` - `/staking/epoch={epoch}` - user commands - `/user-commands/{state hash}` - `/user-commands/{txn hash}` - `/user-commands/height={height}`...
Currently, for each block in the witness tree, we store a copy of its ledger diff in a hash map called `diffs_map: HashMap`. This map is maintained with the witness...