Gist 11b0affbc259955e4ee297b6324dde63

100%

Gist 11b0affbc259955e4ee297b6324dde63

✓ Published0🌍 Public

Last edited Jan 3, 2018

Created on Jan 3, 2018

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.

AI-generated description

Similar vizzes

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

94% 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

93% match

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

92% match

Loading thumbnail…

Gist d979149932bed51371f3a33349a4981d

This example shows a Keybase proof document that cryptographically links a GitHub account to a Keybase identity. The text lays out the user’s public key, a signed JSON object containing account details and a Merkle root, and the resulting signature. It also explains the verification workflow, including the `keybase id` command-line query. The presentation relies on plain Markdown code blocks for the JSON payload, signature, and bash command, with inline hyperlinks to the Keybase profile and public key.

RRestuta

92% 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

91% 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

90% match

Loading thumbnail…

Gist 70ec92554d96397f77c486178017fa4d

This example demonstrates a Keybase identity verification workflow, showing how a GitHub user proves ownership of their account through a signed cryptographic statement. The gist contains a Keybase proof file with a JSON payload, a signature, and instructions for verifying the identity via the Keybase command-line tool. It relies on the Keybase API and command-line program to validate the signature against the user’s public key, confirming the link between the GitHub and Keybase identities. The rendering is plain text, with no data visualization libraries involved.

Aandramalmen

90% match

Loading thumbnail…

Gist de38d64005a8c46715b22c5b4b4a6cc5

This example verifies a Keybase identity claim by presenting a signed JSON message and its PGP signature. It demonstrates how to prove ownership of a GitHub account through a public gist, using the Keybase API to fetch and display the cryptographic proof. The visualization shows the verification data in a raw, text-based format, highlighting the fingerprint, username, and signature blocks. The code relies on the `keybase` command-line tool and JSON parsing to validate the signed object, emphasizing the transparency of web service bindings. The rendering approach is plain-text oriented, making the cryptographic details immediately readable.

BBrideau

89% match