missing transactions for address index

[jlopp]

I've run into a number of addresses that don't seem to have their transactions indexed and was wondering if this is a known issue or if there might be an explanation. Examples (testnet):

curl http://127.0.0.1:18332/tx/address/tb1q7payj0epr8r98293s2hydrgs5045gh72gfnrn6
[]
curl http://127.0.0.1:18332/tx/address/2N846L41qya6WB2Mc5v2hALy2X2B87MFnGc
[]
curl http://127.0.0.1:18332/tx/address/2N9FY2fckLiZtdUEWSMYPe5Zrs1baHX7foG
[]

[pinheadmz]

I think this is the same issue as #733, there is a known issue requesting history for addresses with too many transactions

[jlopp]

Maybe, though I filed this one differently because bcoin doesn't seem to be running into a resources / exhaustion issue. Rather, the above queries return instantly.

[braydonf]

This result is possible if the sync has not completely finished. Those addresses also have many transactions, as similar to the other issue posted, so it could still be related to #733 and #589.

[braydonf]

I'm getting the same result with a testnet node that is completely synced.

[braydonf]

@jlopp Have you verified that indexTX and indexAddress are enabled for testnet? If the indexes are not enabled, these endpoints will return an empty result, instead of throwing an error.

In my case, I had thought that the base ~/.bcoin/bcoin.conf would be loaded in the case that ~/.bcoin/testnet/bcoin.conf was not available, that had the indexes enabled, however that is not the case. Having added a ~/.bcoin/testnet/bcoin.conf with the indexes enabled I'm receiving results for p2sh addresses, and have verified that such getHashes of TX will get the hash for the above addresses, so there shouldn't be an issue with indexing those.

[braydonf]

Indeed, this triggers the issue in #733 and #589:

curl http://127.0.0.1:18332/tx/address/2N9FY2fckLiZtdUEWSMYPe5Zrs1baHX7foG

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

[braydonf]

The endpoints that require indexes should likely through an error if the option is not enabled, instead of returning empty results, or disable the endpoints if the config is not enabled.