ruffiano89 commented 2 years ago

I would like to rise this issue to the team members to share their opinions on the following issue.

Morever, since this question is more related to the fula app use cases, kindly ask you to pay attention [@keyvan-m-sadeghi, @ehsan6sha , and @farhoud].

In a previous team meeting, @masih came up with the idea of making a relation between a did-id and a peer-id, and I started working on that. So far, I have started working on two solutions. Relation between did-id and peer-id. But we will have to choose one of these.

[ ] 1 st method of generating peer-id can be based on did-id.
[ ] 2 nd, both can be independent of each other. Still, we can mapping them in the did-doc.

Note: Please also look at this issue: #59

  graph TD;
      DID-id-->Peer-id;

1st method we can generate a single peer-id based on a one unique did-id. One-to-One (One user can have one peer-id with one did-id).

  graph TD;
      DID-doc-->DID-id;
      Peer-id-1-->DID-doc;
      Peer-id-2-->DID-doc;
      Peer-id-3-->DID-doc;
      Peer-id-n-->DID-doc;;

In Method 2, you can generate a single did-id and multiple peer-ids. One-to-Many (A single user can have multiple peer-ids for each devices).

I would love for you to share your thoughts.

ehsan6sha commented 2 years ago

@ruffiano89 my only concern on number 2 is where we keep the DID-doc? And what happens if someone can access it or it is lost?

ghorbani-m commented 2 years ago

@ruffiano89 my only concern on number 2 is where we keep the DID-doc? And what happens if someone can access it or it is lost?

These concerns are for both cases, so I think the solution is DID providers.

farhoud commented 2 years ago

@ruffiano89 I my view it's more about work we have to done:

peerId exist at least in 5 programing language
in libp2p you can access and validate it everywhere.
lot of existing protocol and libraries exist

If you can manage a way to handle access control with peerId it is more reusable.

if we go with first option can we map multiple did to a single did as parent?

@ehsan6sha @ghorbani-m We can use

ION Look like we have to run some nodes and pay transaction fees for our user to give them free identity. We can reuse box owner resource next but RPI does not have half of resource these kind of node runs on.

ehsan6sha commented 2 years ago

@ruffiano89 I my view it's more about work we have to done:

peerId exist at least in 5 programing language

in libp2p you can access and validate it everywhere.

lot of existing protocol and libraries exist

If you can manage a way to handle access control with peerId it is more reusable.

if we go with first option can we map multiple did to a single did as parent?

@ehsan6sha @ghorbani-m We can use

ION Look like we have to run some nodes and pay transaction fees for our user to give them free identity. We can reuse box owner resource next but RPI does not have half of resource these kind of node runs on.

agree on peerid. hardware requirements is too high for ION

ruffiano89 commented 2 years ago

Q: if we go with first option can we map multiple did to a single did as parent? A: @ehsan6sha, yes we can map multiple dids to root did.

ruffiano89 commented 2 years ago

13.07.2022. In the last sprint meeting we come up use case design as follows:

One did per user. Group sharing identity with one group did.

Ruffiano commented 2 years ago

259 extended issue is related here.

functionland / fula-archived

Relation between did-id and peer-id #236

259 extended issue is related here.