## Test indexing
`ninja check-functional`
## Database upgrade
1. Build bitcoind on master
2. Run it for a few blocks (e.g. 100000), with `-chronik`
3. Stop the node
4. Build bitcoind on this diff
5. Running the node on the same datadir will now upgrade the database and then continue syncing normally:
```
2024-02-27T14:11:10Z Chronik has version 11, DB has version 10
2024-02-27T14:11:10Z Upgrading Chronik DB from version 10 to 11...
2024-02-27T14:11:10Z Upgrading Chronik UTXO set for script_utxo. Do not kill the process during upgrade, it will corrupt the database.
2024-02-27T14:11:10Z Upgraded 0 of 9428 (estimated)
2024-02-27T14:11:10Z Upgraded 10000 of 9428 (estimated)
2024-02-27T14:11:10Z Upgraded 20000 of 9428 (estimated)
2024-02-27T14:11:10Z Upgraded 30000 of 9428 (estimated)
2024-02-27T14:11:10Z Upgraded 40000 of 9428 (estimated)
2024-02-27T14:11:10Z Upgraded 50000 of 9428 (estimated)
2024-02-27T14:11:10Z Upgrade for script_utxo complete
2024-02-27T14:11:10Z Upgrading Chronik UTXO set for token_id_utxo. Do not kill the process during upgrade, it will corrupt the database.
2024-02-27T14:11:10Z Upgrade for token_id_utxo complete
2024-02-27T14:11:10Z Successfully upgraded Chronik DB from version 10 to 11.
```
Note that the UTXO set size is based on what RocksDB estimates for us, and may be off (as in my example).
Running the master version again now gives us the expected error: `Chronik outdated: Chronik has version 10, but the database has version 11. Upgrade your node to the appropriate version`