About BirthPlace AI
BirthPlace AI is a provenance layer for AI datasets and digital artifacts. It anchors cryptographic proofs on Solana so you can demonstrate integrity, authorship, and auditability—without uploading private files.
What it is
A practical workflow for creating provenance proofs you can verify later—locally and on-chain.
BirthPlace AI computes a SHA-256 hash locally and writes a compact, deterministic provenance record on Solana. The proof contains the minimum required data to support long-term verification, while the original file stays with you.
- Timestamped creation and protocol metadata
- Network + transaction signature (Solana) with explorer link
- SHA-256 digest and optional file metadata (name/type/size)
- Verification status and optional verification event history
- Exports for audit workflows (CSV/JSON) and proof sharing controls
What’s improved
The product has expanded beyond single-proof uploads.
- Batch uploads with queueing and durable processing for large sets of files.
- API keys + v1 REST API for server-to-server integrations (proof creation, listing, verification).
- Datasets for organizing proofs, filtering, and export workflows.
- Audit packet exports to generate structured evidence bundles (proof lists + metadata + verification history).
- Plan gating + usage allowance enforced server-side and reflected in the dashboard.
Organizations & teams
Shared workspaces and access control for Business plan users.
Business tier unlocks organizations, role-based access (owner/editor/viewer), shared dataset namespaces, and org-scoped proof visibility.
- Personal scope: wallet-owned proofs with personal dataset grouping.
- Org scope: proofs attached to org datasets for shared visibility and collaboration.
- Server-enforced entitlements: org routes and org attachments are gated to Business plan.
How it works
High-level flow.
- You select a file (or submit a structured payload via API). BirthPlace AI computes a SHA-256 digest locally in the browser (or server-side for API usage).
- A compact provenance JSON record is written on Solana (transaction signature + explorer link), and proof metadata is stored in Supabase for dashboards, filtering, and exports.
- Proofs can remain private (wallet-gated) or be shared via controlled public links (read-only).
- Anyone can verify later by hashing the original artifact and comparing it with the proof record.
Who it’s for
Teams that need proof without friction.
- AI labs, dataset publishers, and data vendors
- Researchers and academic institutions
- Enterprises with audit and compliance obligations
- Builders who need tamper-evident logs and attestations