-
Notifications
You must be signed in to change notification settings - Fork 219
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
feat: remove ablity to send 1-sided tx #6367
feat: remove ablity to send 1-sided tx #6367
Conversation
Test Results (CI) 3 files 120 suites 44m 37s ⏱️ Results for commit e22dfca. ♻️ This comment has been updated with latest results. |
Test Results (Integration tests) 2 files + 2 1 errors 9 suites +9 12m 8s ⏱️ + 12m 8s For more details on these parsing errors and failures, see this check. Results for commit e22dfca. ± Comparison against base commit 97b5128. ♻️ This comment has been updated with latest results. |
c2fdb6c
to
95218cb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about the one-sided code in the transaction service and scanning service? Maybe it should be removed in this PR as well.
I want to keep that in for now, until we know exactly how we want to work with exchanges, they want want to use it. So for now I am only removing the front end calling |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
95218cb
to
a13f3f0
Compare
Description
Removes the ability to send one-sided transactions from the CW, preferring to only send stealth one-sided
Motivation and Context
There is no benefit for sending normal one-sided, only negatives in regard to privacy