You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, end-to-end encryption is implemented on the ad hoc basis for RPC, e.g. in BlockProductionInterface the functions that accept sensitive data and which can be called via RPC (the "_e2e" ones) have to handle encryption explicitly. Now we'd like to be able to send sensitive data over the wallet PRC as well (#1748) and it's getting ugly. We need to implement e2e encryption for all RPC calls via a tower middleware and get rid of the ad hoc solution.
The text was updated successfully, but these errors were encountered:
Currently, end-to-end encryption is implemented on the ad hoc basis for RPC, e.g. in
BlockProductionInterface
the functions that accept sensitive data and which can be called via RPC (the "_e2e" ones) have to handle encryption explicitly. Now we'd like to be able to send sensitive data over the wallet PRC as well (#1748) and it's getting ugly. We need to implement e2e encryption for all RPC calls via atower
middleware and get rid of the ad hoc solution.The text was updated successfully, but these errors were encountered: