<p>A well-known person imply that you are able to contact her by many different means (physically, digitally, other...) but also
that you know some who know her as well and can contact her as easily. Notably, if you don't know well her other certifiers it's
a strong sign that you don't know the person well and a certification made in this context will alert all the Ğ1 community.
In a case of insufficient knowledge then no certification should occur.</p>
<p>Never certify alone, but always with another member of the Web of Trust to avoid any software misuse. In case of any error,
immediately contact other community member of the Ğ1 WoT.</p>
<p>Verify that the future certified person master her account operations : a good way to verify it is to transfer some Ğ1 to the target account,
and to ask then a refund to your own account, it will assure you that the certified person master his private key.</p>
<p>Verify that your contacts have studied and understood the last version of the license.</p>
<p>If you are aware that an effective certifier or a future certifier of an account does not know the account owner, please alert immediately some
experts of the subject among your contacts in the Ğ1 WoT, for the procedure to be verified by the Ğ1 WoT members.</p>
<p>When you are a member of the Ğ1 WoT and you are about to certify a new account:</p>
<p><strong>You are assured:</strong></p>
<p><strong>1 -</strong> That you know well enough (not only "have seen" once) the person who declare to handle this public key (new account).
Look at the above advices about "know well".</p>
<p><strong>2 -</strong> To have personally verified with her that it is the good public key you are about to certify. (see advices above).</p>
<p><strong>3 -</strong> To have verified with the person that she has indeed generated his Duniter account revocation document file, which will enable her,
if necessary, to cancel his member status (in case of account theft, UID change, an incorrectly created account, etc.).</p>
<p><strong>4a -</strong> To meet her physically to make sure that it is this person you know who manages this public key.</p>
<p><strong>4b -</strong> Or to remotely verify the person <-> public key link by contacting the person via several different means of communication,
such as post mail + social network + forum + email + video meeting + phone (acknowledge voice). Because if you can hack an email account
or a forum account, it will be much harder to imagine hacking four distinct means of communication,
and mimic the appearance (video) as well as the voice of the person.</p>
<p>However, the <strong>4a</strong> is preferable to <strong>4b</strong>, whereas the <strong>1</strong>, <strong>2</strong> and <strong>3</strong> statements are always required in all cases.</p>
<p><strong>Abbreviated WoT rules:</strong></p>
<p>Each member has a stock of 100 possible certifications, which can only be issued at the rate of 1 certification / 5 days.</p>
<p>Valid for 2 months, certification for a new member is definitively adopted only if the certified has at least 4 other certifications after these 2 months,
otherwise the entry process will have to be relaunched.</p>
<p>To become a new member of the Ğ1 WoT therefore 5 certifications must be obtained at a distance <= 5 of 80% of the WoT sentinels.</p>
<p>A member of the Ğ1 WoT is sentinel when he has received and issued at least Y[N] certifications where N is the number of members of the WoT and
Y[N] = ceiling N ^ (1/5).</p>
<p>Examples:</p>
<ul>
<li>For 1024 < N ≤ 3125 we have Y [N] = 5</li>
<li>For 7776 < N ≤ 16807 we have Y [N] = 7</li>
<li>For 59049 < N ≤ 100 000 we have Y [N] = 10</li>
</ul>
<p>Once the new member is part of the Ğ1 WoT his certifications remain valid for 2 years.</p>
<p>To remain a member, you must renew your agreement regularly with your private key (every 12 months) and make sure you have
at least 5 certifications valid after 2 years.</p>