PlatformPlatform
Data, security, and observability
Schemas, persistence boundaries, security controls, logs, telemetry, and troubleshooting.
platformsecuritydataobservability
Data model
Challenge records, registry responses, broker jobs, GPU servers, and fallback weights are represented as typed schemas.
| Model | Purpose |
|---|---|
| ChallengeRecord | Stored challenge metadata plus token hash and hint. |
| RegistryChallenge | Validator-facing active challenge metadata. |
| BrokerRunRequest | Bounded Docker evaluation job requested by a challenge. |
| GpuServerRecord | Remote GPU capacity and health metadata. |
| FallbackWeights | Signed latest weights for resilience. |
Security controls
Platform separates public challenge traffic from private control-plane traffic.
- Admin endpoints require admin tokens.
- Internal challenge weights require per-challenge bearer tokens.
- Proxy strips sensitive headers and blocks internal paths.
- Clear challenge tokens are returned only once at creation.
- Broker and GPU endpoints are token-protected.
Troubleshooting
Common failures are usually auth, runtime readiness, proxy routing, or weight normalization issues.
| Symptom | Likely cause |
|---|---|
| 401 admin | Missing or wrong admin token. |
| 403 proxy | Public request targeted blocked internal path. |
| 404 proxy | Challenge is unknown or inactive. |
| 502 proxy | Challenge container is unavailable. |
| Empty weights | No positive known-hotkey weights returned by active challenges. |