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

Blinded ID's algorithm #221

Open
li0ard opened this issue Aug 16, 2024 · 6 comments
Open

Blinded ID's algorithm #221

li0ard opened this issue Aug 16, 2024 · 6 comments

Comments

@li0ard
Copy link

li0ard commented Aug 16, 2024

Could you please tell us how the blinded ids algorithm works?

Especially this condition, because it doesn't work correctly

if kA[31] & 0x80:
    return kA[0:31] + bytes([kA[31] & 0x7F])

In code

@li0ard
Copy link
Author

li0ard commented Aug 16, 2024

And when is the migration to the new algorithm planned?

@VityaSchel
Copy link

+1

@jadnast
Copy link

jadnast commented Aug 17, 2024

same question

@KeeJef
Copy link
Collaborator

KeeJef commented Aug 19, 2024

Hoping to support blinded 25 IDs server side once this is merged #220 , 25 blinded IDs are supported in libsession, but still require client upgrades. i'll try to get some additional info to you on current 15 blinded IDs soon.

@VityaSchel
Copy link

How will client know when to send 25 prefixed id and when to send legacy 15 id? Currently we have "blinding" capability in sogs to switch between 05 and 15 session ids

@li0ard
Copy link
Author

li0ard commented Aug 29, 2024

Hoping to support blinded 25 IDs server side once this is merged #220 , 25 blinded IDs are supported in libsession, but still require client upgrades. i'll try to get some additional info to you on current 15 blinded IDs soon.

@KeeJef

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

No branches or pull requests

4 participants