Skip to content

Do not follow the same treasure map twice with cached frags #934

@KPrasch

Description

@KPrasch

Starting in PR #874 -> When joining a policy, bob follows the treasure map, then checks if the capsule already has attached frags. I propose we do this in the opposite order when cache=True in order to avoid unnecessary network traffic.

see: https://github.com/nucypher/nucypher/pull/874/files#diff-a1320afcd2301567f40adfe049e2616cR567

Metadata

Metadata

Assignees

No one assigned

    Labels

    Bob 👨‍💼Effects the "Bob" development areaEnhancementNew or improved features

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions