Skip to content

Add Proof of Human (PoH) credential documentation#121

Open
eaypek-tfh wants to merge 3 commits into
mainfrom
ertugrulaypek/pop-3807-update-poh-credential-documentation
Open

Add Proof of Human (PoH) credential documentation#121
eaypek-tfh wants to merge 3 commits into
mainfrom
ertugrulaypek/pop-3807-update-poh-credential-documentation

Conversation

@eaypek-tfh
Copy link
Copy Markdown
Contributor

@eaypek-tfh eaypek-tfh commented May 15, 2026

Change

  • Completes the credential documentations by adding the missing PoH Credential page
  • Uses exported PoH credential thumbnail from Figma and eye icon

Visuals

image
image

@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 15, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
world 🟢 Ready View Preview May 15, 2026, 4:54 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Comment thread world-id/credentials/1.mdx Outdated
Use the PoH Credential when you need a strong guarantee that you are interacting with a unique, live human. It is the right choice for:

- **Sybil resistance**: enforcing one account per human for airdrops, voting, rewards, or rate limiting.
- **High-assurance authentication**: gating sensitive actions where document-level uniqueness (NFC) is not enough.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

superior uniqueness isn't the right argument for high-assurance authentication. I think the right argumenet is something about being really confident (thanks to biometrics) that you're interacting with the correct human.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alright, how about "gating sensitive actions where you need biometric confidence that you're interacting with the correct, unique human."?

Comment thread world-id/credentials/1.mdx Outdated
<td className="whitespace-nowrap">
<code>expires_at</code>
</td>
<td>Unix timestamp three years after the most recent issuance.</td>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The definition of "expires_at" isn't really three years - that could change or be flexible. it's something like "When the credential expires. This currently is three years after the most recent issuance"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

alright, will update to "Unix timestamp when the credential expires. This is currently three years after the most recent issuance"

Comment thread world-id/credentials/1.mdx Outdated

## Credential Renewal

Users can renew their PoH credential to extend its validity as long as the Orb capture is deemed fresh by the issuer. Each renewal produces a credential with `expires_at = now + 3 years` while `genesis_issued_at` remains constant.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does renewal produce a credential? This implies kinda there is now two credentials. In my mind it updates the existing credential.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeap, that'd be better. will update to "Each renewal updates the credential with ..."

@eaypek-tfh eaypek-tfh requested a review from paolodamico May 15, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants