@SpendBCH and I conducted some tests yesterday to validate balances being reported by the different SLP indexers.
The method we used was to look at old mainnet SLP tokens that have small numbers of transactions (a small DAG). For instance, here the genesis TXID for a token with only 2 addresses holding balances and only three transactions:
By using tokens like this, we were able to manually verify the results we were getting from SLPDB queries, the block explorer, and the Java Indexer. I asked Simple Ledger if they had developed any automated tests like this, that could be used to validate the data coming back from fully-synced SLPDB instances. They said there were no tests like this.
The scope of this issue is to create a series of Integration tests that can be run against SLPDB and the Java SLP Indexer to verify accurate balances for specific tokens where the balances can be validated manually.
@SpendBCH and I conducted some tests yesterday to validate balances being reported by the different SLP indexers.
The method we used was to look at old mainnet SLP tokens that have small numbers of transactions (a small DAG). For instance, here the genesis TXID for a token with only 2 addresses holding balances and only three transactions:
By using tokens like this, we were able to manually verify the results we were getting from SLPDB queries, the block explorer, and the Java Indexer. I asked Simple Ledger if they had developed any automated tests like this, that could be used to validate the data coming back from fully-synced SLPDB instances. They said there were no tests like this.
The scope of this issue is to create a series of Integration tests that can be run against SLPDB and the Java SLP Indexer to verify accurate balances for specific tokens where the balances can be validated manually.