Hugging Face's logo

Spaces:
Pittro
/
tttps-proof-explorer
Running

App Files Community
tttps-proof-explorer
File size: 2,169 Bytes
6d42092
09a8425
 
 
6d42092
 
 
 
 
09a8425
 
2e5a071
e782def
2e5a071
09a8425
 
 
 
 
 
 
 
 
 
 
 
e782def
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
09a8425
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
---
title: TTTPS Proof Of Time Explorer
emoji: ⏱️
colorFrom: gray
colorTo: green
sdk: static
pinned: false
---

# TTTPS Proof-of-Time Explorer

[![TTTPS Verified](https://img.shields.io/badge/TTTPS-Verified_Roughtime-blue?style=flat-square)](https://huggingface.co/spaces/Pittro/tttps-proof-explorer)
[![TTTPS](https://img.shields.io/endpoint?url=https://kpp.kenosian.com/v1/badge/status.json)](https://kpp.kenosian.com/verify.html)

Live demo of the TTTPS (Time-Token Transport Protocol Suite) self-sealing
provenance API at [kpp.kenosian.com](https://kpp.kenosian.com/tttps-api.html).

Type text, hash it client-side (sha256, in your browser), anchor the hash to
get a cryptographic timestamp receipt, then independently verify that
receipt. This page talks directly to the live public API over CORS —
there is no backend for this demo.

This is a proposal specification, not a ratified standard. A receipt attests
*when*, *order*, and *tamper-evidence* for a content hash — explicitly
not correctness of the content itself.

## No SDK needed

```bash
curl -X POST https://kpp.kenosian.com/v1/keys \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com","use_case":"trying tttps"}'

sha256sum myfile.txt
curl -X POST https://kpp.kenosian.com/v1/anchor \
  -H 'Content-Type: application/json' -H 'X-API-Key: <your api_key>' \
  -d '{"content_hash":"<the 64-hex digest>"}'

curl 'https://kpp.kenosian.com/v1/verify?receipt_id=<your receipt_id>'
```

Eight agent frameworks have an integration. Which of them are installable
right now, with the exact install command for each, is published in one place
and not duplicated here:
[the integration status table](https://kpp.kenosian.com/tttps-api.html#integrations).

Note: an earlier Gradio version of this demo was prototyped and verified
locally, but this HF account is not on a paid plan and HF Spaces now requires
a PRO subscription to host Gradio/Docker Spaces on `cpu-basic`. Static Spaces
are free for everyone, and since the TTTPS API has open CORS
(`access-control-allow-origin: *`), the same live anchor/verify roundtrip
works directly from the browser with no backend at all.