{"file":"docs/seed/Credential_Payload.txt","start":75,"end":93,"lines":[{"number":75,"text":"3. Authorship keypair"},{"number":76,"text":"K_author_private"},{"number":77,"text":"K_author_public"},{"number":78,"text":""},{"number":79,"text":"Algorithm: Ed25519"},{"number":80,"text":""},{"number":81,"text":"Purpose:"},{"number":82,"text":""},{"number":83,"text":"Sign authored objects."},{"number":84,"text":"Sign credentials or statements."},{"number":85,"text":"Sign versions and amendments."},{"number":86,"text":"Co-sign collaborative objects."},{"number":87,"text":"Establish provenance."},{"number":88,"text":""},{"number":89,"text":"A publication API call should normally require both:"},{"number":90,"text":""},{"number":91,"text":"K_auth signature + K_author signature"},{"number":92,"text":""},{"number":93,"text":"Compromise of only the authorship key would therefore not let an attacker submit forged material through the live CRE8 API."}]}