Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TX Output missing in GetAddressUnspentOutputs #492

Open
Ekliptor opened this issue Nov 8, 2021 · 6 comments
Open

TX Output missing in GetAddressUnspentOutputs #492

Ekliptor opened this issue Nov 8, 2021 · 6 comments

Comments

@Ekliptor
Copy link
Contributor

Ekliptor commented Nov 8, 2021

I have an address with valid outputs: https://blockchair.com/bitcoin-cash/address/qpkajruupllffkut5ly690r35nvzwll64szqrgk0vf

Yet all BCHD nodes do not have any outputs for this address:

grpcurl -d '{"address": "bitcoincash:qpkajruupllffkut5ly690r35nvzwll64szqrgk0vf"}' bchd.greyh.at:8335 pb.bchrpc/GetAddressUnspentOutputs 
{
  
}
curl -X POST "https://bchd3.prompt.cash:2053/v1/GetAddressUnspentOutputs" -H  "accept: application/json" -H  "Content-Type: application/json" -d "{  \"address\": \"bitcoincash:qpkajruupllffkut5ly690r35nvzwll64szqrgk0vf\",  \"include_mempool\": false,  \"include_token_metadata\": false}"

{
  "outputs": [],
  "token_metadata": []
}

I checked BestHeight already and the 2 nodes above are at a height > 712,780 and therefore should have the TX.
Assuming I'm not missing something, this should eventually fork BCHD off the network? (unless bug in API layer)

edit.:
and I can confirm both TX hashes are also missing on the GetTransaction() API call

66b1167575fdb40d632bdd94114fccdfa10e1ec28fec767ce7bf44dc507475ce
867fc01be92ce90c8d51ee2f8f5ee9b372049505eb477e734b7d71d5c787044b
@Ekliptor
Copy link
Contributor Author

Ekliptor commented Nov 9, 2021

After some digging I found that the node of imaginary username is the only one recording all TX currently. Talking with him to figure out why.

grpcurl -d '{"address": "bitcoincash:qpkajruupllffkut5ly690r35nvzwll64szqrgk0vf"}' bchd.imaginary.cash:8335 pb.bchrpc/GetAddressTransactions

Worst case we have to bootstrap from his local DB

@zquestz
Copy link
Contributor

zquestz commented Nov 9, 2021

After some digging I found that the node of imaginary username is the only one recording all TX currently. Talking with him to figure out why.

grpcurl -d '{"address": "bitcoincash:qpkajruupllffkut5ly690r35nvzwll64szqrgk0vf"}' bchd.imaginary.cash:8335 pb.bchrpc/GetAddressTransactions

Worst case we have to bootstrap from his local DB

I see the same number of transactions on all nodes... All have 2 confirmed transactions for that address...

@zquestz
Copy link
Contributor

zquestz commented Nov 9, 2021

@alexanderramos89
Copy link

alexanderramos89 commented Nov 9, 2021 via email

@Ekliptor
Copy link
Contributor Author

Ekliptor commented Nov 9, 2021

I didn't know about the BCHD explorer. Great thx!

The electroncash node doesn't have my last TX (that imaginary username has), but because its behind from chain tip:

grpcurl -d '{"address": "bitcoincash:qpkajruupllffkut5ly690r35nvzwll64szqrgk0vf"}' bchd-mainnet.electroncash.de:8335 pb.bchrpc/GetAddressTransactions

These errors have been starting about 2 days ago on prompt.cash and manual inspection showed each time that the TX was indeed not recorded at that time.

Will monitor it more, but for now we conclude its only long delays for now?

@alexanderramos89
Copy link

alexanderramos89 commented Nov 9, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants