Skip to content

Maintain cache of blinded IDs #16

@jagerman

Description

@jagerman

Right now Session can struggle a bit with dynamically calculating unblinded IDs*, but libsession-util ought to be able to computing the blindings of known contacts quite easily and maintain either a semi-persistent (calculated on startup) or fully persistent (dumped to DB) cache of them to provide fast looking to Session clients.

* - specifically, to figure out if a given blinded ID maps to a known contact. You can't go blinded -> session ID, but given all your known session IDs, you can go from them to their blinded versions for each server pubkey and see if anything matches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions