Umi

# UMI

UMI develops ASL-to-English translation through endpoint competition and
reproducible public model contributions. Endpoint miners may keep their models
private. Contributors can submit licensed, runnable model bundles for evaluation
and promotion into successive public UMI baselines.

The longer-term protocol can expand to other directions and forms of human-machine
interaction only when each task has an independently useful output and a
reproducible, adversarially tested mechanism. Each later task requires a separate
protocol extension.

- [UMI whitepaper (PDF)](whitepaper/UMI-Whitepaper.pdf)
- [LaTeX publication source](whitepaper/main.tex)
- [Plain-text protocol source](whitepaper/README.md)
- [Open competition implementation and rehearsal](docs/OPEN_COMPETITION.md)
- [Historical version 0.1 specification](whitepaper/LEGACY_V0_1.md)
- [bitsign product MVP](roadmap/bitsign-mvp/README.md)
- [public observer API contract](docs/DASHBOARD_API.md)
- [what miners should run now](docs/CURRENT_MINER_OPERATION.md)
- [temporary live-miner policy and activation](docs/REGISTRATION_BRIDGE.md)
- [miner model integration](docs/MINER_MODEL_INTEGRATION.md)
- [Apple Silicon miner operator](docs/MACOS_MINER_OPERATOR.md)
- [Linux x86_64 validator operator](docs/PERMANENT_VALIDATOR_SUPERVISOR.md)
- [Apple Silicon validator operator](docs/MACOS_VALIDATOR_OPERATOR.md)
- [publisher batch operator](docs/PUBLISHER_BATCH_OPERATOR.md)
- [publisher availability operator](docs/PUBLISHER_AVAILABILITY_OPERATOR.md)
- [reference mirror and delivery service](docs/MIRROR_SERVICE_OPERATOR.md)
- [public validator audit-bundle publication](docs/AUDIT_BUNDLE_PUBLICATION_OPERATOR.md)
- [inactive live-shadow release operator](docs/SHADOW_CALIBRATION_OPERATOR.md)
- [inactive calibration launch checklist](docs/INACTIVE_LAUNCH_CHECKLIST.md)
- [seven-day bootstrap service-weight addendum](docs/BOOTSTRAP_WEIGHT_ADDENDUM.md)
- [shared-validator bootstrap supersession](docs/SHARED_VALIDATOR_BOOTSTRAP_SUPERSESSION.md)
- [bootstrap service-weight operator, historical](docs/BOOTSTRAP_WEIGHT_OPERATOR.md)
- [emergency direct-bootstrap cutover, historical](docs/EMERGENCY_DIRECT_BOOTSTRAP_CUTOVER_V1.md)
- [legacy validator transition hold](docs/LEGACY_VALIDATOR_TRANSITION.md)
- [first public post-reveal result deployment](deploy/first-public-result/README.md)

## Current status

The version 0.2 whitepaper defines the successor design. The code includes signed
submission intake, model preservation and promotion, evaluation and settlement,
and a separately authorized weight worker. The successor supervisor supports
per-round input updates and recovery from interrupted host upgrades.
The public competition service is not deployed, and the installed validators
still use their signed registration-bridge policy. No successor reward allocation
has been activated. See the
[implementation checklist](docs/OPEN_COMPETITION.md) for the tested scope and
remaining production work.

Historical guides that refer to whitepaper Section 14 describe
[version 0.1](whitepaper/LEGACY_V0_1.md), not the successor activation procedure.
The registration bridge has its own signed policy and retains the original sunset.

SN78 is active on mainnet, but UMI translation weights are not. The public-endpoint
pilot is closed. A signed [temporary registration bridge](docs/REGISTRATION_BRIDGE.md)
replaces its frozen two-miner reward rule with live-miner availability checks and
equal total weight per qualifying coldkey/IP/funding group. It retains the original bootstrap
sunset. Both UID 0 and UID 54 have finalized bridge rows. The
[September 12 activation readback](docs/REGISTRATION_BRIDGE_ACTIVATION_2026-09-12.md)
shows positive consensus and incentive for 16 miners from the initial row.
The [funding-cap readback](docs/REGISTRATION_BRIDGE_FUNDING_CAP_2026-09-13.md)
records the later policy, which also groups common pre-registration senders
bound in its signed snapshot. This is not proof of one person per group.
New registration checks are automatic; publishing new funding links still
requires a signed snapshot refresh.

Registered non-validator miners need a healthy chain-announced HTTPS `/healthz`
endpoint. No pilot, manual opt-in, or running model is required for the bridge.
It does not issue translation requests or measure model quality. See
[what miners should run now](docs/CURRENT_MINER_OPERATION.md) for the exact checks.
The old `/api/v1/bootstrap-service` endpoint describes the retired pilot and
cannot attest to this replacement's activation or eligibility.

There are four distinct executable paths:

```text
component test
validator hotkey
  -> canonical btauth/1 request
  -> POST /v1/translate
  -> bounded video fetch + configured model
  -> timelocked, miner-signed response
  -> Quicknet reveal
  -> exact CER/WER
  -> content-addressed local replay bundle

offline release and conformance rehearsal
canonical window evidence
  -> policy and runtime-pin verification
  -> pool quorum and deterministic selection
  -> assignment, request, and sealed-response roots
  -> canary, spent-state, rolling-score, and weight projection
  -> bounded seven-stage audit bundle
  -> no chain write

installed inactive live shadow
signed, hash-pinned release + private operator bindings
  -> owned smoldot finality + proof-verified chain reads
  -> certified mirror retrieval and authenticated miner delivery
  -> three finalized transcript anchors and live btauth/1 requests
  -> response and ground-truth timelock reveal
  -> persistent spent, publisher-fault, rolling-score, and monitoring state
  -> exact projected row + signed calibration or incident bundle
  -> no weight-call capability

temporary registration-bridge weights
signed bridge policy + hash-pinned release directive
  -> finalized registration, owner, permit, and serving roster
  -> bounded public HTTPS health checks and finalized roster recheck
  -> merge live UIDs by coldkey, HTTPS IP or signed funding link (ports ignored