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

🚀[Release v1.0.0] Merge into Main #30

Merged
merged 31 commits into from
Mar 29, 2023
Merged

🚀[Release v1.0.0] Merge into Main #30

merged 31 commits into from
Mar 29, 2023

Conversation

kcw-grunt
Copy link

@kcw-grunt kcw-grunt commented Mar 28, 2023

Hero merge

  • Adds fpRate (False Positive Rate)
  • Accepts fpRate for the BloomFilter to modulate the sync time for the user
  • User can balance privacy vs sync time
  • Last major update to the library

Test Process

  • Update the git submodule for litewallet-android
  • Verify litewallet-ios is not adversely unaffected
  • Update the git submodule for litewallet-ios
  • Verify litewallet-ios is not adversely unaffected

LiteBit and others added 30 commits September 27, 2017 11:21
make sure to call balanceChanged callback whenever balance is updated
Bech32 support on Litewallet Android
* Updated the checkpoints

* only 1 checkpoint added

* Added Testnet checkpoint
fpRate: false positive rate for the bloomfilter
@kcw-grunt kcw-grunt changed the title Release/v1.0.0 🚀[Release v1.0.0] Merge into Main Mar 28, 2023
@kcw-grunt kcw-grunt added this to the v1.0.0 milestone Mar 28, 2023
@kcw-grunt kcw-grunt marked this pull request as ready for review March 28, 2023 18:14
Copy link

@josikie josikie left a 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?

@kcw-grunt
Copy link
Author

Wow...thanks so much for the look @josikie
Really needed it. We are in panic mode.

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 ?

@kcw-grunt kcw-grunt merged commit 4d2d088 into main Mar 29, 2023
@josikie
Copy link

josikie commented Mar 29, 2023

Thank you for the answer! @kcw-grunt That's make sense. Are the potential addresses a fake address?

@kcw-grunt
Copy link
Author

Thank you for the answer! @kcw-grunt That's make sense. Are the potential addresses a fake address?
Well they are valid ltc addresses. The idea, @josikie , is the node cannot distinguish between your address that you care about and other addresses

@josikie
Copy link

josikie commented Mar 30, 2023

Oh that's good! @kcw-grunt

@kcw-grunt kcw-grunt deleted the release/v1.0.0 branch April 6, 2023 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants