balancesForAddress does not reflect balance for several minutes

[m4ktub]

A token was sent to an address and the explorer presented the validity of the token transfer immetiatly:

• https://explorer.bitcoin.com/bch/tx/d4ea12959dcb476e4e9149095300572ef9f88e88ca5e901320ecb2f674c6a8e3#o=1

Nevertheless both the explorer and the REST services reported "no balance" for several minutes:

• https://explorer.bitcoin.com/bch/address/1H4iZcMnaJWGgkYVfqqdSHtDx2gyeSGgSV
• https://rest.bitcoin.com/v2/slp/balancesForAddress/simpleledger:qzcrtar0uj83gme5rckr6ug5jk6fymcsxv4czmypeh

Note: The balance is now correctly reported.

Since most of the time time balances are correctly reported after a few seconds and another times after a few minutes a seemingly reasonable 1 minute interval is not enough to ensure a result.

Is there an "official" latency, that must be assumed, between broadcasting the transaction and the update of balances?

[christroutner]

I think this is a case of things being in flux. Minor bugs are still being ironed out in SLPDB and rest.bitcoin.com. Validation methods between SLPDB, slpjs, SLP-SDK, and rest are not fully aligned at present.

Please keep an eye on this failure mode. If you find a way to consistently reproduce it, please share it with us.

I really appreciate you taking the time to report these issues.