Skip to content

Use one event identity per key-share/key-release message #699

@ylembachar

Description

@ylembachar

Change event-based decryption so each fired event identity is processed independently, with one identity per
decryption trigger, key-share message, and key-release flow. This avoids one event identity missing shares blocking unrelated identities, and avoids batch-signature divergence while service-level signatures are still present.

Tradeoff: this increases P2P messages from 1 batch with N identities to N single-identity messages. Message volume will be tested separately on Chiado.

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