reward table slightly off compared to public block explorers like cardanoscan.io, adastat.net

[sacrelege]

OS
Your OS: Debian 12

Versions
cardano-node: cardano-node 10.5.0 - linux-x86_64 - ghc-9.6
cardano-db-sync: cardano-db-sync 13.6.0.5 - linux-x86_64 - ghc-8.10
PostgreSQL version: postgresql-15 15.13-0+deb12u1

Build/Install Method
downloaded pre-build binaries (tar.gz) from github

Run method
standalone

cardano-db-sync \
	--config config/db-sync-config.json \
	--socket-path ../db/node.socket \
	--schema-dir schema/ \
	--state-dir ledger-state/mainnet

Additional context
Getting different reward numbers from dbsync compared to public block explorers for almost every epoch for any random stake addr. After installing cardano-node 10.5.0 I dropped my cexplorer table and did a full resync using cardano-db-sync 13.6.0.4 (no snapshots used). I've just upgraded to 13.6.0.5 after the full sync was done.

Problem Report
example SQL I used:

   select reward.spendable_epoch,  reward.amount as lovelace
    from reward inner join stake_address on reward.addr_id = stake_address.id
    inner join pool_hash on reward.pool_id = pool_hash.id
    where stake_address.view = 'stake1u8wy7ld73z22n8yu9pt56gt0getqg43yxj4932td88alwcghh4x3t'
    order by earned_epoch desc;

screenshot shows the difference between my sql output and adastat.net for the stake addr in the SQL query above

[rdlrt]

Looks like an issue with your instance. Results for your SQL executed here:

 select reward.spendable_epoch, reward.amount as lovelace from reward inner join stake_address on reward.addr_id = stake_address.id inner join pool_hash on reward.pool_id = pool_hash.id where stake_address.view = 'stake1u8wy7ld73z22n8yu9pt56gt0getqg43yxj4932td88alwcghh4x3t' order by earned_epoch desc limit 10;
 spendable_epoch | lovelace
-----------------+----------
             570 |  7544531
             569 |  7584315
             568 |  7133079
             567 |  5502998
             566 |  8013253
             565 |  8499506
             564 |  9935747
             563 |  5790065
             562 |  6494349
             561 |  8355131
(10 rows)

[sgillespie]

Is there anything else that may be different in your installation? Have you tweaked your config? Did you get it from the Cardano Operations Book? When did you get it?

I wonder if using node 10.5.0 is a potential problem. It is pre-release version, which means it is not intended for general mainnet use.

[sacrelege]

yes config was based from cardano operations book. I used/using cardano db-sync in production since years, but without ledger state (so my rewards table was empty). So I cloned the whole VM, dropped whole database, installed all the new versions (including the pre-release of the node, since this cloned 2nd instance is just for testing) and enabled ledger state.

What possible configuration in db-sync could cause a slightly off reward amounts?! Main thing could really be cardano-node pre-release which would be actually bad (or good that I noticed it...).

I'll use the latest released version of the node, drop the blockchain and the dbsync database again and do a full resync of both - I'll report back