Participate
Comment on the specification§
Open an issue in the project repository (to be published at sanad-protocol/sanad) or write to contact@sanadprotocol.org. A comment period of 14 days applies before any decision. Please say which section and which rule you mean, and what you would change.
Implement it§
Build a verifier, an issuer, an attestor, a log or an indexer. Run the public vectors, publish your results and tell the project. A second and a third independent implementation are the most valuable contributions at this stage.
Become an attestor§
Anyone may attest by publishing a decentralised identifier and signing. Nobody vets attestors for the protocol: each verifier chooses by policy. Independence is not enforced by the protocol: it rests on declared conflicts of interest, blind marking and the verifier's policy (for example, attestors from different institutions). Declare every conflict of interest.
Contribute§
Contributions are signed off under the Developer Certificate of Origin (a line "Signed-off-by: Name
Standardisation§
The planned route is a public draft, a reference implementation, a conformance suite, at least three independent implementers, then a W3C Community Group (creation is free and needs five supporters) and later a Working Group or an equivalent. Sanad does not declare itself a standard; adoption does.
Security§
Report vulnerabilities in the specification or in reference code to security@sanadprotocol.org. See the security page for scope, response times and the measures of this website.
Contact§
contact@sanadprotocol.org. See also Contact.