Gist 34c691fbbd4b922d00ce15d7815201b4

100%

Gist 34c691fbbd4b922d00ce15d7815201b4

✓ Published0🌍 Public

Last edited Jan 24, 2018

Created on Jan 24, 2018

This gist demonstrates a Keybase identity proof, binding the GitHub account `andrewwitherspoon` to the Keybase user `awitherspoon88`. It contains a signed JSON object with cryptographic details, including the public key, Merkle root, and a signature, all formatted for verification. The proof is presented as a Markdown file with embedded JSON and a command-line instruction for lookup. The code uses no data-visualization libraries, serving solely as a static authentication document.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist f34132c889978856c7cb9d6ad1bf62b5

This example demonstrates a Keybase identity proof, showing how a GitHub account is cryptographically linked to a Keybase user through a signed JSON object. The gist displays the signature payload, including the user’s public key, merkle root, and service binding details, alongside the resulting signature in ASCII-armored format. The code uses Keybase’s command-line client and API to generate and verify the proof, with the JSON object structured for web service binding. The rendering is plain text, preserving the exact signature and metadata for public auditability.

Aalexfinnarn

90% match

Loading thumbnail…

Gist 1135e63dbabffa7f17fbe707874655d8

This example demonstrates a Keybase identity proof, cryptographically linking the GitHub user andrewthornton to the Keybase account thor5551. It shows the signed JSON statement and its validation via a posted gist. The visualization relies on the Keybase API and command-line tool to verify the public key signature, confirming ownership of both accounts. The code references the Keybase Go client for signing and the `keybase id` command for auditability.

Aandrewthornton

89% match

Loading thumbnail…

Gist 84c19b830de7ca18d8bc432ac5de9737

This example demonstrates a cryptographic identity verification workflow, showing how a GitHub user proves ownership of their account through a signed Keybase statement. The visual focus is on the structured JSON payload, which contains the user’s public key, service binding details, and a Merkle root hash. The code uses the `crypto` module for signature validation and `JSON.stringify` to format the payload for display. It also references Keybase’s command-line interface and the public API for fetching identity data, with the rendered output emphasizing the signature’s provenance and auditability.

Aandrewxhill

89% match

Loading thumbnail…

Gist 11b0affbc259955e4ee297b6324dde63

This example presents a Keybase proof file, showing the JSON structure and signature used to cryptographically link a GitHub account to a Keybase identity. The gist displays the plain-text claim, the signed JSON object, and the command-line verification steps. It relies on the Keybase API’s signing and hashing functions to generate and validate the Merkle root and signature, demonstrating the web service binding process for identity attestation.

Aapburnes

89% match

Loading thumbnail…

Gist 798db6d676e01a7de3d83bdcd2c91ee6

This example shows a Keybase proof-of-identity gist, presenting a signed JSON document that cryptographically links a GitHub username to a Keybase identity. It demonstrates how the keybase.io command-line client generates and verifies a web-service binding, using the `keybase id` tool to audit the claim. The visualization highlights the structured signature payload, including the merkle root hash, public key, and encrypted signature block, rendered as readable text. It relies on the Keybase API and command-line interface to expose the verification workflow, with no custom charting or data-processing libraries involved.

Aabernier

88% match

Loading thumbnail…

Gist 80bb43be3501065d066a79e9882d6df2

This example uses a Keybase proof document to verify a GitHub account identity, displaying the signed JSON payload and its cryptographic signature. The gist contains the proof text, a public key link, and command-line instructions for lookup. It relies on Keybase’s API for identity verification and GitHub’s gist hosting to publish the proof, with the data rendered as plain text and code blocks. The visualization shows the structure of the signed object, including timestamps, hashes, and the signature itself, demonstrating the audit trail.

Aakollegger

88% match

Loading thumbnail…

Gist 648424dcb16c212d5f16a474109afbce

This gist contains a Keybase proof, a JSON-signed statement that cryptographically links a GitHub account to a Keybase identity. The document includes the user’s public key fingerprint, a signed payload, and the generated PGP signature. It also provides the command-line verification steps using the Keybase program, along with a link to the user’s public profile for auditing. The example is a plain-text, procedural artifact rather than a data visualization, and it does not employ any charting libraries or graphical rendering techniques.

TTBD

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

88% match