Skip to main content
100%

keybase.md

✓ Published0🌍 Public
Aadewes
Last edited Sep 23, 2014
Created on Sep 23, 2014

This example visualizes a cryptographic identity proof, showing how a GitHub account (adewes) is cryptographically linked to a Keybase identity (dewes) via a PGP-signed JSON object. The gist file contains the signed statement and its raw JSON payload, including the public key fingerprint and service bindings. It does not use a visualization library; instead, it relies on the textual and structured data from the Keybase proof system, with the JSON object and PGP signature displayed directly as the primary content. The rendering approach is plain text formatting, preserving the original gist structure.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 0ed0d9c83434b39760891be6d14dede2

This example demonstrates a Keybase identity proof by visually presenting the cryptographic signature that links a GitHub account to a Keybase user. The gist shows a JSON object containing the signed statement, along with the PGP-signed message and the public key fingerprint, all rendered as structured text. The visualization uses a plain-text layout to display the keybase.md file, highlighting the nested JSON and the encoded signature block without any additional charting or graphics libraries. The data source is the gist itself, and the rendering relies solely on HTML text formatting, with no interactive or dynamic elements beyond the static content.

EEleonore9
89% match
Loading thumbnail…

Keybase ID signing

This example shows the cryptographic proof flow of a Keybase identity claim, displaying the signed JSON message, the PGP signature, and the associated verification text from a GitHub gist. It uses the `keybase` command-line program to demonstrate how the identity is auditable. The visualization renders the proof structure directly from the raw text, with syntax highlighting applied to distinguish the JSON payload, signature block, and markdown-formatted narrative. It relies on standard Web APIs for text parsing and styling, presenting the static gist content as a transparent record of the signing process.

Aadanner
89% match
Loading thumbnail…

keybase

This example visualizes the trust relationships embedded in a Keybase proof document, presenting the signed JSON payload and its cryptographic signature as an interactive graph. It uses the keybase.io proof format to show how a GitHub identity links to a Keybase user via a PGP key, rendering the nested claim structure with d3.js force-directed layout. Nodes represent entities like the service, username, key ID, and signature block, with edges depicting their associations. The visualization directly parses the provided gist data, making the verification process tangible by mapping each field to a visual component.

MMattieTK
88% match
Loading thumbnail…

Keybase

This example shows a Keybase proof document rendered as a text artifact, outlining a user’s cryptographic identity claim across GitHub and Keybase. It displays the signed JSON message, the PGP signature, and command-line verification instructions. The code uses markdown formatting to structure the proof, embedding the public key fingerprint and signature blocks directly in the gist. No external visualization libraries are used; the data is presented purely as static plain text.

CCliffordAnderson
88% match
Loading thumbnail…

Gist 1a826885eacfebb60a6ff421d57a9e37

This example shows a Keybase proof file, which cryptographically links a GitHub account to a Keybase identity. It demonstrates how the raw JSON payload and its signature are structured for public verification, including the nested key, Merkle root, and service binding fields. The gist itself contains no visualization code; instead, it serves as a static text-based proof, relying on Keybase’s cryptographic signing (Ed25519) and hashing (SHA-256) rather than any charting or rendering library. The rendering approach is purely textual, presenting the signed object and signature for manual or programmatic validation.

HHerbCaudill
87% match
Loading thumbnail…

Keybase proof

This example visualizes a cryptographic identity proof from Keybase, showing the linkage between a GitHub account and a Keybase user through a signed JSON object. It renders the proof’s structured data, including the public key, Merkle root hash, and signature, as an interactive network graph. The visualization uses d3.forceSimulation to position nodes representing the user, service, and cryptographic components, with edges indicating signed relationships. It relies on the raw JSON payload from the Keybase proof file, parsing the `body` and `client` fields to display the verification chain. The graph updates dynamically when hovering over nodes to highlight connected proof elements.

AAnsonT
87% match
Loading thumbnail…

Keybase proof

This example presents a Keybase proof as a text-based verification document, showing how a user authenticates their GitHub identity through a signed JSON object and PGP message. The plain-text rendering displays the structured claim, including the public key fingerprint, signature block, and command-line instructions. The data originates from the Keybase proof format, with the visible code using standard cryptographic libraries for signing and verification. The visualization relies on simple typographic layout to make the proof’s components—identity, signature, and instructions—clearly readable without graphical charts.

Aabehmiel
87% match
Loading thumbnail…

Gist ce00b8f09d14cbb43b4525651def6528

This example demonstrates a cryptographic identity verification proof posted as a GitHub gist, using Keybase’s public-key infrastructure. It shows how a user (Ekthelion) claims ownership of both a GitHub account and a Keybase identity by embedding a signed JSON object that includes a fingerprint and a PGP signature. The code references the Keybase command-line tool and the OpenPGP API to generate and validate the signature. The visualization would render the JSON structure and signature block as textual data, highlighting the nested cryptographic fields and the verification steps without relying on graphical libraries.

EEkthelion
86% match