Store and count the total number of outputs traversed when building the index

[raphjaph]

I'm unsure about how to properly store a single value persistently in the database. In its own table? What should the key be? Or I make a table HEIGHT_TO_NUM_OUTPUTS that tracks how many outputs there are per block and then I just add up those values in the info command?

#487

[raphjaph]

If you search for an outpoint that has been spent you get the following error message on the website

https://ordinals.com/output/969d68907f0e2aeacb8b17979fa48ea3b817cc5bfc92b1675326b3c170991c88:0
Output unknown. (maybe change to Output already spent so it contains no Ordinals)

Which makes sense. So the final database is an index of all UTXOs to ordinal ranges not an index of all outpoints to ordinal ranges. Maybe we should make that clearer in the code and also on the website.

Is this correct?

All UTXOs are outpoints but not all outpoints are UTXOs

[casey]

Mostly looks good! We should create a general statistics table, with a dedicated enum as the key.

[raphjaph]

Just ran this on signet:

blocks indexed: 108159
utxos indexed: 1370410
outputs traversed: 3801139
tree height: 5
free pages: 268249225
stored: 89.54 MiB
overhead: 10.73 MiB
fragmented: 561.19 MiB
index size: 2.5 GiB

Bitcoin-cli tells me that signet only has 1.24mil utxos. Are we maybe counting something wrong? Unspendable outputs?

 bitcoin-cli -chain=signet gettxoutsetinfo
{
  "height": 108160,
  "bestblock": "0000002321f73b11485d4b642535bd7fd0d349fc2e2f0dc2223e50c096dd5e28",
  "txouts": 1243877,
  "bogosize": 99780304,
  "hash_serialized_2": "f03a81c527f80b7527bb6f3e312dc9cde360f35ed2cb7c9bf892c97fc4522579",
  "total_amount": 5407999.99984400,
  "transactions": 1223288,
  "disk_size": 98571150
}