Admit as owner

Claim one PCoC object as the key it names. Stage the object here, sign the challenge with that key, and the bench runs the same split as Verify object: checks (did the walk verify?) beside policy (does this instance accept it?). A policy reject is not a broken check.

Only the holder of the private key behind the object's public_key can finish this. Holding the file is not enough, and finishing grants no login, cookie or badge — the result is a signed submission and a JSON receipt. Just checking a file, or trying a public fixture? That is Verify object. The posted fixtures grew from a leftover u64 fill salt, so they cannot be claimed here.

1 · Stage the object

One .cbor, at most 2 MiB. It must carry a 32-byte public_key and a 32-byte seed tip, with terrain grown from public_key ∥ that tip: produce it with pcoc produce --pubkey-hex … (or --npub clothing). Legacy fill-salt objects are burned for admit.

Drop one .cbor file here, or pick one.

Choose PCoC file

2 · Sign it with the owner key

Scan this with the signer that holds the key. The code carries only the challenge id; the signer loads the payload from the bench and sends back a signature — never the secret, and never the file again.

Signing on this machine instead? The payload below is the exact byte string to sign: BIP-340 over its SHA-256.

Bench

Verify API base URL

The page is static; staging, signature checking and the walk all run on the bench. Production default is https://verify-api.pcoc.app. Point this at a local one with ?api=http://127.0.0.1:8787 when running the service yourself.

No signer on hand? scripts/gl-admit-lane-b.sh in the repository walks the same four calls from a shell. Verify object checks a file without claiming it — fixtures live there.

Admit as owner

1 · Stage the object

2 · Sign it with the owner key

Measurements

Policy

Bench