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
Bitcoin cash introduced a CashAddrs in 2018. Its a new encoding (only userfacing) for their addresses to avoid mistakes (by introducing checksums and better distinguishability from BTC addresses) (ref 1, ref 2)
Our backend only knows legacy addresses thus entering a CashAddr yields no results. Since it is only an encoding cash addresses can be converted to the legacy format.
I propose to convert CashAddr entered in the search field and other queries on the REST level to support CashAddrs.
Code for the conversion can taken from this tagpack-tool issue.
The text was updated successfully, but these errors were encountered:
regarding the convertion to the legacy format, recently bch introduced a new address format (P2SH32) which is not yet supported by the cashaddress library. We introduced a quick and dirty fix in the gslib (graphsense/graphsense-lib@17c6b3f) which is probably also relevant for this issue.
Bitcoin cash introduced a CashAddrs in 2018. Its a new encoding (only userfacing) for their addresses to avoid mistakes (by introducing checksums and better distinguishability from BTC addresses) (ref 1, ref 2)
Our backend only knows legacy addresses thus entering a CashAddr yields no results. Since it is only an encoding cash addresses can be converted to the legacy format.
I propose to convert CashAddr entered in the search field and other queries on the REST level to support CashAddrs.
Code for the conversion can taken from this tagpack-tool issue.
The text was updated successfully, but these errors were encountered: