Right now we have two main `crypto` APIs: `iroha::crypto` and `ursa`.

Main entities of both APIs:

  • Private and Public Keys
  • Signatures

We already have an abstraction over some `ursa` entities. Proposal is to encapsulate everything under `iroha::crypto` do not exposing `ursa` related entities outside this module.

It means that new methods for generating keypairs and signature verification would be added to `iroha::crypto` with wrapper entities (Public/PrivateKey).

  • No labels

2 Comments

  1. Salakhiev Kamil

    Proposal makes sense. 

    With that approach it would be very easy to replace crypto algorithm that is currently used

  2. Makoto Takemiya

    It makes sense to me. We just need to make it easy for people to access Ursa capabilities.