Certify & Verify Workspace
Two boxes, one device. Left: add a document to certify it — images receive a visible GreenQubyte logo plus an invisible watermark, and every file gets an Ed25519-signed receipt. Right: drop any file to authenticate it against the ledger and scan it for the watermark. Files are hashed and processed entirely in your browser — nothing is uploaded.
Account
Signing in makes your stamps account-verified: the signed receipt names your GitHub account by its permanent numeric id. GreenQubyte reads only your public profile and keeps no GitHub token.
Plan & billing
API keys for pipelines
For GitLab CI, GitHub Actions, n8n or the Python CLI. A key is shown once — GreenQubyte keeps only its hash. Templates: GitLab CI · GitHub Actions · n8n · Python CLI
My documents
Loading…
Certify & watermark
Establish proof of existence. The fingerprint is anchored to RFC 3161 + OpenTimestamps and bound into a signed receipt; images also carry the dual GreenQubyte watermark.
Drop a file to certify
sha256(file) computed client-side · 0 bytes of content transmitted
Verify & authenticate
Drop a file to re-hash it, check the ledger, and scan images for the visible + invisible GreenQubyte watermark. The SHA-256 ledger match is the authoritative proof.