You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BCHD is praised for many of it's unique features. grpc is one of them however when trying to query using Python it seems like there are lack of documentation and examples.
When I was playing with it I was able to feed it a bitcoin cash address and get results but when doing the same with transaction id and token ids it seems like it needs special formats and it is not taking the usual tx id that is shown in wallets and explorers.
One of the errors I saw was, invalid hash length of 64, want 32","grpc_status":10
also errors about requiring bytes instead of string. Senior devs may be able to find their way around but for others they could get lost :)
If you provide the more info about when the usual format for address, tx id, token id and similar is not accepted and a way to convert it probably I might be able to help writing some simple examples.
The text was updated successfully, but these errors were encountered:
BCHD is praised for many of it's unique features. grpc is one of them however when trying to query using Python it seems like there are lack of documentation and examples.
When I was playing with it I was able to feed it a bitcoin cash address and get results but when doing the same with transaction id and token ids it seems like it needs special formats and it is not taking the usual tx id that is shown in wallets and explorers.
One of the errors I saw was,
invalid hash length of 64, want 32","grpc_status":10
also errors about requiring bytes instead of string. Senior devs may be able to find their way around but for others they could get lost :)
If you provide the more info about when the usual format for address, tx id, token id and similar is not accepted and a way to convert it probably I might be able to help writing some simple examples.
The text was updated successfully, but these errors were encountered: