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

Deny search for DsQxuVRvS4eaJ42dhQEsCXauMWjvopWgrVg #358

Closed
chappjc opened this issue Feb 23, 2018 · 4 comments
Closed

Deny search for DsQxuVRvS4eaJ42dhQEsCXauMWjvopWgrVg #358

chappjc opened this issue Feb 23, 2018 · 4 comments

Comments

@chappjc
Copy link
Member

chappjc commented Feb 23, 2018

This is the sstxchange address for 0 value outputs in ticket purchases. It's used all the time, but never has a balance (unless someone sent money there)

@raedah
Copy link

raedah commented May 7, 2018

Be sure to include the proper explanation of why the search will now show when returning the msg to the user.

@chappjc
Copy link
Member Author

chappjc commented May 7, 2018

I was thinking about this again some time ago, and I'm not totally sure we should block it anymore. There is nothing preventing someone from sending actual DCR to the address, and it would be a shame to hide such a txn.

@raedah
Copy link

raedah commented May 7, 2018

We can still display an informative msg at the top since this is a special address, and just not block the display of the transactions.

@chappjc
Copy link
Member Author

chappjc commented Jun 30, 2018

There was good progress in PR #466, but it didn't quite make it. I'd like the task to be resumed, from scratch, with one hint:

zeroed := [20]byte{}
address, err := dcrutil.NewAddressPubKeyHash(zeroed[:], params, 0)

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

Successfully merging a pull request may close this issue.

2 participants