Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,8 +43,15 @@ every live submit:
X-Lium-Api-Key: <your Lium API key>
```

The key is held only in master memory for that submission (never stored in the
DB, never logged). Missing key on live → `400 missing_lium_api_key`.
The key is held in master memory for that submission and may also land in a
**short-TTL encrypted seal file** on the master host (never in Postgres, never
logged) so a control-plane restart can still stop your pod. Missing key on
live → `400 missing_lium_api_key`.

If the challenge process restarts mid-run, your submission is marked failed
promptly with `control_plane_restart` / `harness_detached`. Stop the Lium pod
if it is still billing, then resubmit with `X-Lium-Api-Key`. Poll
`GET /v1/submissions/{id}/events` and `GET /v1/submissions/{id}/logs?since=`.

## Telemetry hooks (still required)

Expand Down
17 changes: 13 additions & 4 deletions docs/prism.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,10 +67,19 @@ every live submit:
X-Lium-Api-Key: <your Lium API key>
```

The key is held only in master memory for that submission (never stored in the
DB, never logged). Missing key on live → `400 missing_lium_api_key`. Cost
guardrails (`max_price_per_hour`, lifetime) still apply so a bad key cannot
rent unbounded SKUs through the orchestrator.
The key is held in master memory for that submission and may also land in a
**short-TTL encrypted seal file** on the master host (never in Postgres, never
logged) so a control-plane restart can still stop your pod. Missing key on
live → `400 missing_lium_api_key`. Cost guardrails (`max_price_per_hour`,
lifetime) still apply so a bad key cannot rent unbounded SKUs through the
orchestrator.

If the challenge process restarts mid-run, your submission is marked failed
promptly with `control_plane_restart` / `harness_detached` (not left `running`
for hours). When the seal is missing, stop the pod yourself on Lium, then
resubmit with `X-Lium-Api-Key`. Poll `GET /v1/submissions/{id}/events` and
`GET /v1/submissions/{id}/logs?since=` for live stage heartbeats and harness
tails while the run is healthy.

## Submit

Expand Down
1 change: 1 addition & 0 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@
| Score 0 after review | `Copied` / high-confidence `Suspicious` (≥0.9, non-trope) | Similarity on **your delta**; rewrite unique hunks; tropes alone are not plagiarism |
| `similar: true` on precheck | Would hit intake copy gate | Change the patch vs prior champions; starting from the operator pin is fine |
| `429 precheck_quota_exceeded` | 3 prechecks/coldkey/UTC day used | Wait until next UTC day; rotating hotkeys does not reset |
| `control_plane_restart` / `harness_detached` | Challenge process restarted mid-pod | Stop the Lium pod if still billing; resubmit with `X-Lium-Api-Key` |
| `400 missing_lium_api_key` | Live path needs miner-funded Lium | Pass `X-Lium-Api-Key` (your Lium account); see [Submit](submit.md) |
| `403 hotkey_not_in_metagraph` | Hotkey not registered | Check the hex (64 lowercase, no `0x`) |
| `409 submission_gated` | 1-max slot already used | One accepted patch per hotkey; identical pin+patch is idempotent |
Expand Down
Loading