3 ms·
in short: this is a strange wrapper over http using ecdsa as auth. why not use ECIES along with it to totally achieve privacy from requester to server? as i u
by longt1melurker 6y ago
in short:
this is a strange wrapper over http using ecdsa as auth.
why not use ECIES along with it to totally achieve privacy from requester to server?
as i understand, the vapor nodes save requests and replies, so these can be replayed.
this means heavy data bloat, when i look at nowadays apis we all run, saving all requests and answers fully... come on
- aleclarsoniv 6y agoIt's probably optional for Vapor nodes to save transactions. Most useful for auditing requirements, I guess. The more compelling use case is for clients to cache the receipts of particular transactions so they can replay them on other services. For example, if the user decides to migrate their data to a competing service. Also, the receipts act as proof of tampering (or lack thereof), since they are signed by the Vapor node.