Churning results to weird destination address
See original GitHub issueWhen churning (sweep_all
) from main address to main address the destination address shown in Ledger is not the real one you’re churning from/to. Also the amount is “0”.
I had no balls to proceed and see where it goes.
Churning to different address/subaddress works ok - the destination and amount is legit.
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Why you should not begin churning - V3.0 - Reddit
Churning, in the basic sense, is the action of repeatedly signing up for the same credit card bonuses for points (or miles) in...
Read more >How to Implement Customer Churn Prediction [Machine ...
Churn rate is a critical metric of customer satisfaction. ... It includes a target label indicating whether or not the customer left within...
Read more >OSPF external routes churn - Cisco Community
I am observing some strange behaviour related to the routing table, almost all external routes and some inter-area routes are getting refreshed every...
Read more >Churning Zcash for maximum anonymity and privacy - General
Try to get ZEC from someone else's shielded address in the first place, not from a transparent address. Otherwise, churn it twice initially ......
Read more >What is Churn Rate? How to Calculate Customer Churn ...
You're charging too much. Price is a tricky topic, always. Price is a common reason why someone might churn and it really comes...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@cslashm what about address confirmation when using
sweep_all
to the same main address? The destination confirmation is shown on Ledger. But with completely different address. Don’t even know where it comes from. This looks misleading… as it seems like you’re sweeping all your XMR to that random address.Correct. There is no problem for the outcome.
I’m just saying that this looks a bit misleading… Especially when you’re a new user and don’t know this whole workflow you mentioned. At first glance it feels like you’re sweeping all your XMR to that, and only one, destination address you have to confirm on your ledger.
But maybe it’s just me. Feel free to close this issue or keep it if you think that too. ☮️