Trevor Bernard

> So, [@Isaac-DeFrain](https://github.com/Isaac-DeFrain), you're saying that there's a new "transaction" type? (Is it an internal command?) And that new type will appear in some block, and we should parse it...

There are many ways we can handle the hard-fork. The precomputed blocks staged ledger diffs will converge to empty after the stop txn global slot. So we don't explicitly need...

> How do others create the genesis block? Does the Mina node not create one from genesis ledger and constants? (If not, where did the genesis block come from?) @robinbb...

This is my work around. This exists in the root of the rust directory: ```bash #!/usr/bin/env bash BLOCKS_DIR=~/.mina-indexer/blocks STAKING_LEDGERS_DIR=~/.mina-indexer/staking-ledgers GENESIS_LEDGERS_DIR=~/.mina-indexer/genesis-ledgers DATABASE_DIR=~/.mina-indexer/database IDXR="$(pwd)"/target/release/mina-indexer DOMAIN_SOCKET_PATH="$(pwd)"/mina-indexer.sock mina-indexer() { "$IDXR" "$@" } mina-indexer server...

Proposal: we just ingest the 2 known bad genesis accounts and assign `0.000001000` to the genesis block winner after parsing the genesis mainnet ledger. Alternatively, we might want to ingest...

An update: I've allowed the 2 known bad public keys into the genesis ledger and I've accounted for the genesis block winner in the genesis ledger.

The total supply is simply the foldl sum account.balance. A good test would be to compare the calculated total supply at a given height and compare the total supply value...

https://github.com/Granola-Team/mina-indexer/blob/3d41a221a95bd46ca6f8812afc7a2dd2ae824580/rust/src/ledger/mod.rs#L36 This is resolved

I'm not sure how we're going to test this. We should discuss what behaviour we want the indexer to exhibit when we hit this error. IMHO, I think we should...

One possible solution is to return a specific error code and we test for that