Frequently Asked Questions

A proof is a tamper-evident record that links a cryptographic hash (SHA-256) to an on-chain Solana transaction. It enables independent verification that the same content (matching that hash) existed at or before the transaction time and has not changed since.

No. BirthPlace AI does not store your raw files on-chain. We generate a SHA-256 fingerprint and inscribe that fingerprint plus small metadata on Solana. Your original file remains on your device unless you store it elsewhere.

BirthPlace AI inscribes a compact provenance JSON payload that includes the SHA-256 hash and minimal metadata (for example, filename, size, content type, protocol version, network, and timestamps). The server enforces a small payload size cap to keep inscriptions efficient.

The public proof page shows the proof ID, SHA-256 hash, timestamps, network, and the Solana transaction link. It may also display a sanitized provenance payload and verification helpers designed for audits and citations.

It proves integrity and anchoring: a specific SHA-256 hash was anchored on Solana at the referenced transaction. It does not, by itself, prove authorship, legal ownership, or the truthfulness of the underlying content—only that content matching that hash existed and can be verified against the on-chain anchor.

Anyone can edit a file, but they cannot alter the proof. If the data changes, its hash changes and it will no longer match the proof. Alterations are detectable by recomputing the SHA-256 hash and comparing it to the proof.

Immutability means the on-chain provenance record cannot be changed or backdated once written. It does not mean your original file is frozen; it means the on-chain anchor cannot be rewritten without detection.

Compute the SHA-256 hash of the original file locally and compare it to the SHA-256 shown on the proof. Then open the Solana explorer link and confirm the transaction corresponds to the proof’s on-chain anchor.

You can verify locally in the browser (hashing never requires uploading your file). If you choose “Verify & record”, BirthPlace AI stores a durable verification status for that proof (match or mismatch) along with a timestamp. This helps teams and auditors see the most recent verification result without repeating the workflow.

“Verified at” indicates the most recent time a verification was recorded for a proof. For clarity across timezones, timestamps may be shown in a friendly format and/or as ISO-8601 UTC (ending in “Z”).

Datasets are labels used to group related proofs for dashboards, filtering, and exports. You can keep proofs unassigned or assign a dataset name. The app can also list dataset names for dropdowns and integrations without needing to load all proofs.

Organizations let multiple wallets collaborate. An org dataset is a shared container within an organization that proofs can be attached to. Access is governed by membership roles (viewer/editor/owner), and attachment typically requires editor or owner privileges.

Yes. You can create API keys from your account and use them for automation via a simple REST API. API keys are scoped and can be revoked. Common use cases include creating proofs server-side, listing proofs, listing datasets, and recording verification results.

The REST API supports: creating proofs (server-side inscription), listing proofs (with pagination and filters), listing datasets, and recording verification results (match/mismatch). API requests authenticate using an API key in the Authorization header.

API keys are shown only once at creation time and are stored server-side as hashes (not plaintext). If you believe a key is exposed, revoke it and create a new one. Keys also have scopes so you can restrict what an integration is allowed to do.

No. BirthPlace AI handles the on-chain inscription process on your behalf. You sign in with your wallet for identity and access control, but you do not need to manage SOL just to create provenance proofs (subject to plan limits and system policies).

BirthPlace AI pays the on-chain transaction fees on your behalf as part of the service. Subscription tiers may include different monthly allowances for proof creation, and the app may display measured network fee spend for transparency.

Yes. Public proof links are designed to be shareable and read-only. Anyone with the link can view the proof and verify it using the hash and the Solana transaction. Private areas of the app remain protected behind authentication.

Some features (exports, citation formats, verification badges) may be gated by the tier under which the proof was created. This helps keep proofs consistent and audit-friendly by treating entitlements as a snapshot at creation time.

Public outputs are designed to be privacy-preserving. If a provenance payload contains identifiers, BirthPlace AI may sanitize them in public views. The public proof page still shows the minimum metadata needed for verification.