New feature: better know the requirements to join

Here is the new API method: /wot/requirements/[pubkey]

This method will inform, for each identity matching given pubkey, what the identity lacks to become a member, i.e. what are its requirements.

  "identities": [
      "uid": "aaa",
      "meta": {
        "timestamp": 1443121769
      "outdistanced": [
      "certifications": 0,
      "membershipMissing": true

Note 3 things:

  • certifications returns the number of certifications of the identity, it has to be compared with sigQty parameter
  • membershipMissing informs only if the node has a join membership, it does not tell if it has expired for example
  • outdistanced returns the public keys of members that are too far from identity

This method has been made to help newcomers understand what they need left to become members.


Great !
May be it should be more useful to have the pubkeys of the members that are at the good distance to certify the identity. Then the client can propose this list to ask for certifications.

And the list of “in the distance” members is shorter than the “outdistanced” ones (the rest of the network).

And, by the way, could we have UIDs with pubkeys. More useful to humans.

1 Like

Yes, but finding potential paths should be a higher level service, because it supposes:

  • for each outdistanced member
    • find the members that are distance 1 from him
    • find the members that are distance n from him
    • where n = max - 1.

So the result will be almost anyone (only one distance is substracted). I don’t think it is worth a computation for uCoin. Maybe higher services will be interesting, however, if it had to find potential members in a given area, for example that lives in our city.


1 Like