forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Include p2pk into addressindex #1767
Labels
Comments
UdjinM6
pushed a commit
that referenced
this issue
Jan 9, 2018
* Add simple test for p2pk script refs #1767 * Add p2pk transaction addresses indexing Addresses from p2pk transaction are now indexed by transations pubkeys hashes. Even if it isn't strict behavior and the p2pk are rare and obsolete, it is transaction that should be able to be looked up. fixes #1767 * Add p2pk script checking tests refs #1767
I believe this has been added to the |
Yep, #1839 fixed this I believe. Closing. |
andvgal
pushed a commit
to energicryptocurrency/gen2-energi
that referenced
this issue
Jan 6, 2019
* Add simple test for p2pk script refs dashpay#1767 * Add p2pk transaction addresses indexing Addresses from p2pk transaction are now indexed by transations pubkeys hashes. Even if it isn't strict behavior and the p2pk are rare and obsolete, it is transaction that should be able to be looked up. fixes dashpay#1767 * Add p2pk script checking tests refs dashpay#1767
CryptoCentric
pushed a commit
to absolute-community/absolute
that referenced
this issue
Feb 26, 2019
* Add simple test for p2pk script refs dashpay#1767 * Add p2pk transaction addresses indexing Addresses from p2pk transaction are now indexed by transations pubkeys hashes. Even if it isn't strict behavior and the p2pk are rare and obsolete, it is transaction that should be able to be looked up. fixes dashpay#1767 * Add p2pk script checking tests refs dashpay#1767
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See bitpay#17
Example:
https://insight.dash.org/insight/tx/f770f05d2b1c63b71b2650227252da06ef226661982c4ee9b136b64f77bbbd0c
vs
https://insight.dash.org/insight/address/XoLTipv6ryWECYu94vbkmDjntAXqNgouTW
The text was updated successfully, but these errors were encountered: