Skip to content

featreq: multisig e2e encryption #1527

@n0izn0iz

Description

@n0izn0iz

If we want to push multisig, I think we need to consider implementing end-to-end encryption at some point, to avoid having to worry about database confidentiality and remove a target from our backs.
For example, the data is encrypted client-side with the public keys of all multisig members, and only ciphertext is stored in the transaction list on the backend.
As a first step, we could push further to minimize metadata.

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