Crucible coordinates training on L1.
Crucible anchors run state, rollout batch commitments, verifier attestations, reward pools, slashing records, weight roots, and artifact roots. Training payloads and model checkpoints stay off-chain behind verified Weft/MARS-style commitments.
Run
Rollouts
Rewards
Weights
Policy gate
explicit
Payload bytes
off-chain
Live mode
coord-signed
anchored record
The chain stores roots, commitments, attestations, slash records, and balance movements. Rollout traces and model checkpoints stay in artifact storage.
Run open
policy + pool
Rollout commit
batch roots
Reward attest
signed policy
Weights publish
model root
Slash
evidence root
Close
refund or done
Run open
The L1 opens coordination, not training.
A coordinator funds the reward pool and commits the objective, policy, verifier mode, and off-chain artifact root. Public networks require explicit policy activation before transactions execute.
Rollout batch
Batches enter as roots and metadata.
Workers produce payloads off-chain. The chain accepts only batch ids, sample counts, rollout roots, metrics roots, environment commitments, and artifact commitments.
Verifier attestation
Rewards wait for deterministic verifier policy.
Coordinator-signed mode can settle today from the coordinator's signed attestation. Redundant, TEE, ZK, or lineage modes fail closed unless their concrete integrations are enabled.
Weight root
Checkpoints are anchored by root continuity.
A publisher can advance the model head only when authorized and when previous_root matches the current head. The model bytes never enter consensus.
Slashing
Bad actors leave evidence, not blobs.
Invalid commitments, stale rollouts, policy violations, equivocation, invalid weights, and false attestations are recorded as typed slash records with evidence commitments.
Close
Runs finish under explicit close rules.
Completed runs require no remaining pool. Cancelled and expired runs refund the remaining pool to the coordinator. All state remains durable and queryable.
Launch posture
Executable when policy enables it.
Crucible is implemented as live system-contract metadata plus a native transaction family. Canary and Mainnet do not activate it by default; explicit policy configuration can run coordinator-signed training flows now, while unavailable verifier and lineage modes stay fail-closed.
Boundary
No rollout blobs. No model bytes. No fallback proofs.
Consensus accepts verified artifact commitments, roots, metadata, and balance movements. If TEE, ZK, redundant verification, or lineage reward integration is unavailable, the executor rejects the transaction instead of downgrading trust.
An anchor for distributed training, not a training runtime.
Crucible keeps the chain responsible for coordination, accounting, and accountability while artifact storage carries the large payloads.