# A directory of people and their keys: what changed in v1.1.0, sgit.ai > The changes to the article "A directory of people and their keys" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [A directory of people and their keys](../../a-directory-of-people-and-keys.md) / [Versions](../a-directory-of-people-and-keys.md) / v1.1.0 # A directory of people and their keys: what changed in v1.1.0 From v1.0.0 (2026-10-18, `928a4383e`) to v1.1.0 (2026-10-27, `db67c5ce1`), paragraph by paragraph. 0 paragraphs added, 0 removed, 2 changed in place, 54 unchanged. About 0 words added and 131 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../a-directory-of-people-and-keys.md) 2 unchanged paragraphs !shot pk-flow.webp | images/ | From a passkey to a message.message:Aregistering,person registerspublishing a passkeykey,onevidence,pki.sgit.ai,verification,which opens their vault; makes or imports a key pair, with the private keys kept in the vault; publishes the public half; adds evidence (a website, GitHub, a DNS record); is verified by Dinis, who signs it,links, and confirms that from their side; and links with others, each link counting only when both confirm. Then anyone in the register can be sent a secret assentaby QR code that opens in their browser and is read with their vault.code. | architecture 32 unchanged paragraphs, under In short {#in-short}, Why now {#why}, Is there really nowhere? {#prior-art}… !shot pk-two-way.webp | images/ | Two ways, or not at all.all:Onthe 2019 signing model on the left, 2019: anyone could append a signature to anyone's key, and nothing could be deleted, so keys were flooded until they broke. On the right, the rule here:here, each person writes onlywriting to their own record. A vouches for B in A's record; B confirms in B's record; the link exists only when both do. A vouch that nobody confirms stays a claim in the voucher's own record, and each record has a size limit. | concept 20 unchanged paragraphs, under Degrees of separation {#degrees}, Invitations by QR code {#qr}, What it is for {#for}… [all versions](../a-directory-of-people-and-keys.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/a-directory-of-people-and-keys/v1.1.0.html)*