Status and FAQ
The client is open source. The server is a hosted service operated by TLAY — cloning the SDK does not give you a server to run.
What ships#
| Capability | Status |
|---|---|
| Hash and content submission | Shipped |
| Merkle-batch status and portable receipts | Shipped |
| Offline inclusion verification | Shipped |
| x402 V2 settlement on EVM via Circle Gateway and USDC | Shipped — the first concrete payment integration, not the definition of the product |
| MPP / Tempo | In the hosted server; not exposed by the SDK |
| Other payment networks and assets | Roadmap |
Who runs what#
| Part | Delivered as |
|---|---|
| Client SDK | Apache-2.0, TypeScript, Node.js 18+ or any runtime with fetch. Installed from a pinned Git tag. |
| Server | Proprietary, multi-tenant, operated by TLAY. No self-hosting path; the SDK can point at another compatible deployment with baseUrl. |
| Anchoring chains | The managed deployment advertises Polygon (default), Base and BNB Smart Chain today. Ask getChains(). |
FAQ#
Does my data go on-chain?#
No. One Merkle root goes on-chain for a whole batch. If you submit a hash you computed yourself, only those 32 bytes reach the service; anchor() is the convenience path that sends the content for the service to hash.
How long until a record is anchored?#
On the managed deployment batches close every 15 minutes, so a first record typically reaches anchored in 15–20 minutes. Until then the receipt endpoint correctly returns 404.
Does a receipt prove a reading is true?#
No. It proves these exact bytes were in a batch whose root was anchored no later than a given block. Who produced the record comes from a device signature; whether the reading was accurate depends on the sensor.
What does it cost?#
There is a self-serve free plan with a monthly hash quota and per-key rate limits. Verification and receipt lookups are public and need no key.
Can I use it without the rest of TLAY?#
Yes. It is useful anywhere a record will later be questioned by someone who did not keep it — IoT logs, maintenance and calibration records, energy and carbon data, supply-chain milestones, reconciliation.