Skip to main content
BASE routes miner traffic. Artifact format, post-submit evaluation, and scoring are challenge-owned. This page only describes common proxy and identity patterns. After you pick a challenge, that pack is authoritative.

Upload endpoints (proxy patterns)

Many challenges accept traffic through:
Agent Challenge production miners should follow the challenge-local signing string documented in the Agent Challenge pack. That singular string may differ from the subnet-level platform-upload-v1:... bridge string used on some /v1/... bridge routes. Always match the path you actually call.

Bridge upload sketch

When using the bridged ZIP path, the proxy typically:
  1. Checks body size against the configured max (order of millions of bytes; agent ZIPs are often capped lower inside the challenge at 1 MiB)
  2. Verifies miner signature headers
  3. Forwards a verified identity set to the challenge internal bridge

Common signature headers

Canonical bridge message construction for BASE proxy uploads:
Details: Authentication.

Agent Challenge note

After Agent Challenge upload, production scoring is not complete until miner Phala self-deploy finishes attested review and eval. Host-only env PUT / launch flows are legacy offline relative to TEE production. Use the Agent Challenge pack.

Next