-
Notifications
You must be signed in to change notification settings - Fork 46
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
🚀[Release v1.0.0] Merge into Main #30
Conversation
Fix 0 change output
make sure to call balanceChanged callback whenever balance is updated
Fix litecoin testnet
…used for chain params
Bech32 support on Litewallet Android
* Updated the checkpoints * only 1 checkpoint added * Added Testnet checkpoint
fpRate: false positive rate for the bloomfilter
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.
Nice! Both changes on BRPeerManager.c and BRPeerManager.h. What is bloomFilter used for?
Wow...thanks so much for the look @josikie The Bloom Filter in short is a way to send a bunch of potential addresses to a node so the node doesn't know which ones you care about. The more false positives we send to the node the less likely the node knows which addresses are actually mine. In the extreme, I can just send the node just my addresses only which means the random litecoin node can track what addresses are mine and it puts a spotlight on me. So, there is no privacy for me as a Litewallet user. What we are trying to do is let the Litewallet user make sync as quick as possible without telling every node "Hey look at all my addresses and all my Litecoin!" Make sense @josikie ? |
Thank you for the answer! @kcw-grunt That's make sense. Are the potential addresses a fake address? |
|
Oh that's good! @kcw-grunt |
Hero merge
Test Process
litewallet-android
litewallet-ios