What problem does your feature solve?
when horizon forward ingestion starts up, it checks history db first, if there are ledgers present the new ingestion process will attempt to catchup from the latest ledger on history rather than just starting from network's latest ledger. In this case horizon won't validate the ledger chain between last history ledger on db to the PreviousLedgerHash of newly ingested ledger from network(captive core).
What would you like to see?
during horizon forward mode ingestion startup, if any ingested history ledgers exist, perform ledger chain validation from latest history ledger on db to PreviousLedgerHash of next ledger from live network ingestion and log a WARN message to avoid making this too intrusive as a starting point, or consider treating this detection as ERROR level and stop the process?
Relates to:
What alternatives are there?
What problem does your feature solve?
when horizon forward ingestion starts up, it checks history db first, if there are ledgers present the new ingestion process will attempt to catchup from the latest ledger on history rather than just starting from network's latest ledger. In this case horizon won't validate the ledger chain between last history ledger on db to the PreviousLedgerHash of newly ingested ledger from network(captive core).
What would you like to see?
during horizon forward mode ingestion startup, if any ingested history ledgers exist, perform ledger chain validation from latest history ledger on db to
PreviousLedgerHashof next ledger from live network ingestion and log aWARNmessage to avoid making this too intrusive as a starting point, or consider treating this detection asERRORlevel and stop the process?Relates to:
What alternatives are there?