Batch submission
Submit one or more hashes in a single API call. Provncloud aggregates them into a Merkle tree and settles the root on Solana. Individual proofs remain independently verifiable within the batch.
Integration guide
How to Integrate Provncloud for Automated Solana Timestamping
Provncloud provides a hosted API for batch timestamping on Solana. This guide walks through authentication, batch submission, verification, and production deployment patterns so teams can move from a manual proof workflow to an automated pipeline.
ProvesThat a hash existed at a specific Solana slot
Does not proveTruth or authorship of the document itself
Best forAudit trails, artifact provenance, compliance receipts
NetworkSolana — economy (~1hr) or priority (<2s)
Overview
What Provncloud does
Provncloud accepts data, computes a Merkle root hash across submitted batches, and settles that root on Solana. The result is a timestamp proof that anyone can verify independently without relying on a Provncloud server.
Three settlement tiers
Economy (free, ~1 hour finality), Standard ($19/mo, ~10 seconds), and Priority ($149/mo, less than 2 seconds). Choose based on whether your workflow needs fast settlement or can tolerate delayed finality.
Independent verification
Once settled, the proof can be verified using the Solana block explorer or Provncloud's verification endpoint. No API key is needed to verify — only to submit.
Step 1
Authentication
Provncloud authenticates requests via API key passed in the X-API-Key header. Keys are issued per account and tier.
Generate a key
Log in to your Provncloud dashboard, navigate to the API keys section, and create a new key. Scoped keys are recommended for production deployments so each service uses a key with minimal permissions.
Pass it in requests
Every API call must include X-API-Key: your-key in the header. The API also supports JWT bearer tokens for server-to-server authentication where API key rotation is handled by an identity provider.
Step 2
Submitting a batch
Submit one or more hashes to the /v1/batches endpoint. The API accepts a list of SHA-256 hashes and returns a batch ID that you can use to track settlement status.
Request format
POST https://provncloud-production.up.railway.app/v1/batches
{ "hashes": ["sha256hash1", "sha256hash2"], "mode": "standard" }
The mode field accepts "economy", "standard", or "priority" depending on your tier.
Response
{ "batch_id": "uuid", "root_hash": "merkle-root", "status": "pending", "mode": "standard" }
The root hash is the combined Merkle root of all hashes in the batch. This is what gets settled on Solana.
After submission, poll the /v1/batches/{batch_id} endpoint to check when the root hash has been confirmed on Solana. Status transitions from pending to confirmed once the transaction is finalized.
Step 3
Verifying a proof
Anyone can verify a timestamp proof without authentication. The verification endpoint accepts a hash and a batch ID, and returns whether the hash is included in the settled batch.
Verification API
GET /v1/verify?hash={sha256}&batch_id={batch_id}
No API key required. The response includes the Solana transaction signature, slot number, and Merkle proof path.
Independent verification
The Solana transaction signature can be looked up on any Solana block explorer. The Merkle proof path lets you verify inclusion without trusting the API server.
Deployment
Production patterns
Batch aggregation
Accumulate hashes over a time window (5 minutes, 1 hour, daily) and submit them as a single batch. This reduces cost and Solana transaction overhead while still providing per-hash timestamps.
Retry with idempotency
Use a unique idempotency key for each batch submission. If the request times out, retry with the same key — the API returns the existing batch instead of creating a duplicate.
Monitor settlement status
Set up a webhook or polling job that checks batch status every 30 seconds for priority mode, or every 10 minutes for economy mode. Alert on failed or stuck batches.
Which tier fits your workflow?
Economy (Free)
Best for non-critical timestamping where settlement within an hour is acceptable. Good for development, testing, and internal audit trails where immediate finality is not required.
Standard ($19/mo)
Best for production workflows that need sub-minute settlement. Suitable for compliance receipts, artifact registries, and user-facing verification features.
Priority ($149/mo)
Best for high-throughput or time-sensitive workflows. Settlement within seconds. Suitable for financial transactions, real-time verification, and high-volume batch processing.
Deploy a timestamping pipeline today
The Provncloud API is live and accepting submissions. Start with the free tier, then scale up as your verification needs grow.