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
I could see my taproot address ltc1pa3rcf5wm8mf9lxuvx6ytzjn8anrjlxhh485apwxjj6szw02we99qvahx8f (ltc1p-vahx8f for short): https://blockchair.com/litecoin/transaction/013f1e21d086cca4d59ae593c7967fb07e64d559c08727fb23b64953422af38f
I had just received a payment from a friend ltc1qng3m49mzt0m9lea58hxajphwwpe03jxpx5v2ds (ltc1q2ds) for short, that we can indeed see in tx 013f1e21d086cca4d59ae593c7967fb07e64d559c08727fb23b64953422af38f.
Because he used litescribe, his change address is themself, but the receiving address is... ltc1pa3rcf5wm8mf9lxuvx6ytzjn8anrjlxhh485apwxjj6szw02we99qep82zt (ltc1p-ep82zt) and clicking on it gives an address with absolutely no transaction history 🤯
Even stranger, I tried using the API to request information about my account, and to my surprise:
https://api.blockchair.com/litecoin/dashboards/address/013f1e21d086cca4d59ae593c7967fb07e64d559c08727fb23b64953422af38f (ltc1p-vahx8f) => no results
https://api.blockchair.com/litecoin/dashboards/address/ltc1pa3rcf5wm8mf9lxuvx6ytzjn8anrjlxhh485apwxjj6szw02we99qep82zt (ltc1p-ep82zt) => exact same balance, tx history as the one shown by the online explorer for ltc1p-vahx8f
From there, I wanted to understand why my wallet address ending in vahx8f was converted to ending in ep82zt and realized it was only those endings that differed!
It seems something must go wrong somewhere within blockchair that wrongly interprets the end of taproot LTC addresses?
The text was updated successfully, but these errors were encountered:
Using the API, I ran into a very odd behaviour:
I could see my taproot address
ltc1pa3rcf5wm8mf9lxuvx6ytzjn8anrjlxhh485apwxjj6szw02we99qvahx8f
(ltc1p-vahx8f
for short):https://blockchair.com/litecoin/transaction/013f1e21d086cca4d59ae593c7967fb07e64d559c08727fb23b64953422af38f
I had just received a payment from a friend
ltc1qng3m49mzt0m9lea58hxajphwwpe03jxpx5v2ds
(ltc1q2ds
) for short, that we can indeed see in tx013f1e21d086cca4d59ae593c7967fb07e64d559c08727fb23b64953422af38f
.Because he used
litescribe
, his change address is themself, but the receiving address is...ltc1pa3rcf5wm8mf9lxuvx6ytzjn8anrjlxhh485apwxjj6szw02we99qep82zt
(ltc1p-ep82zt
) and clicking on it gives an address with absolutely no transaction history 🤯Even stranger, I tried using the API to request information about my account, and to my surprise:
https://api.blockchair.com/litecoin/dashboards/address/013f1e21d086cca4d59ae593c7967fb07e64d559c08727fb23b64953422af38f
(ltc1p-vahx8f
) => no resultshttps://api.blockchair.com/litecoin/dashboards/address/ltc1pa3rcf5wm8mf9lxuvx6ytzjn8anrjlxhh485apwxjj6szw02we99qep82zt
(ltc1p-ep82zt
) => exact same balance, tx history as the one shown by the online explorer forltc1p-vahx8f
From there, I wanted to understand why my wallet address ending in![Screenshot 2024-09-12 at 3 35 27 PM](https://private-user-images.githubusercontent.com/4267223/366925176-a4c7fd44-85be-44c0-a7f5-33a6f6ef31d7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NTg1MDYsIm5iZiI6MTczOTU1ODIwNiwicGF0aCI6Ii80MjY3MjIzLzM2NjkyNTE3Ni1hNGM3ZmQ0NC04NWJlLTQ0YzAtYTdmNS0zM2E2ZjZlZjMxZDcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTRUMTgzNjQ2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ODMzOWM1N2U5ZDgzYTQ5YWNjYzFkNzVlYTAxM2UyNjlkZWVkNWYwYjI1N2ZmM2M1YjJjNjllZjM1NGM5YzgzMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.e88Ho3fsJ6sXCSpIPOE45IQgTSuvZkcoybgyolhuAD0)
vahx8f
was converted to ending inep82zt
and realized it was only those endings that differed!It seems something must go wrong somewhere within blockchair that wrongly interprets the end of taproot LTC addresses?
The text was updated successfully, but these errors were encountered: