There has been discussion of setting a limit to how many certifications a member of a community can publish. I do not know if this has been implemented as of yet.
However, if it is implemented, it could be catastrophic to @cgeek s Proposal to Change the Distance Rule.
I say this because, in order for the proposal to work, one must certify many others once they are a member of a community in order to keep the community healthy. If we limit how many certification a person may publish, we are limiting the proximity of any one node to every other node.
By allowing a member to revoke a certification, we save him from having to wait for the certification to expire before being allowed to release a new certification (if his allotted certification stock has been filled).
Another benefit of allowing certifications to be revoked is that members of a community can quickly respond to any malignant members of their community. That has the potential to greatly increase the security and speed of threat-diversion in the community.
I have added an issue on the ucoin GitHub repo. If I put it on the wrong repo, please feel free to move it. (I’m confused as to which repo belongs to which part of the project.)