groundinglab gate: sign-in log
Every sign-in this gate has decided, newest at the top.
Each entry says who signed in, when, the key numbers, and whether it was accepted. The log only grows; entries are never edited.
- Quick check (a few seconds): the gate checks the Bitcoin blocks the PCOC names, how many of its waypoints are anchored, and how fast it was made. Passing signs you in, but nothing unlocks yet.
- Deep check (about a minute): the gate checks a few legs drawn at random from across the whole hike. The exact count is set by this service's policy. If they match, the sign-in is accepted and claims unlock. If one does not match, the check did not match; this gate revokes the key.
- Signed in again: a key coming back with a PCOC this gate has already accepted. No new check is needed.
Sign in again when you are ready. That sign-in starts from the beginning.
Loading.
Sign-ins
The rules at this gate
What the gate is running
Endpoints
GET /v1/health,GET /v1/policy,GET /latest.jsonGET /log/{YYYY-MM-DD}.jsonl,GET /log/{YYYY-MM-DD}/{seq}POST /v1/sign-in,GET /v1/sign-in/result/{nonce}POST /v1/verify,GET /v1/verify/{job_id}POST /v1/flush/challenge,POST /v1/flush
How to check this log yourself
The gate publishes each day's entries at /log/YYYY-MM-DD.jsonl (UTC dates). Entry numbers start at 0 and never repeat. Each entry carries prev_event_hash, a fingerprint of the entry before it, so nobody can edit or remove an entry without breaking the chain.
To check it: the earliest entry's prev_event_hash is the SHA-256 of the ASCII bytes pcoc-gate-log-v1 genesis followed by one newline. Every later one is the SHA-256 of the ASCII bytes pcoc-gate-log-v1, one newline, and the previous entry's raw JSON object (the newline after the object is not hashed). Split the file on JSON objects, not on line breaks. The last fingerprint must equal last_event_hash in /latest.json.