UMI is accepting registered SN78 miners for a public endpoint interoperability pilot.
The pilot sends one btauth/1 request with a known public ASL clip to the HTTPS
endpoint in the miner's finalized SN78 serving record. UMI verifies the miner's
signed, timelocked response and publishes the request, response or bounded failure,
revealed references, exact score trace, finalized chain observation, coordinator
attestation, and immutable replay bundle at:
https://api.umi.vision/api/v1/pilots
This is deliberately component_test_no_weight. It proves public endpoint and
protocol interoperability. It is not a production scoring window, model-quality
ranking, activation gate, validator input, weight result, or promise of rewards.
The known clip's score has no leaderboard meaning. UMI translation weights remain
inactive.
Enrollment is open to every registered SN78 miner hotkey without a validator permit that passes the finalized-chain checks. UMI does not assign exclusive pilot slots. Opening an issue starts no request traffic or case timer. Do not start a case or change an axon merely because the issue was opened.
After UMI verifies the enrollment and posts the active coordinator and pinned
revision, the miner may reply READY FOR CASE whenever it can remain online
through reveal. UMI then creates one fresh timed case after the coordinator signer
passes the local possession check. Load the case, publish and verify the finalized
axon, then reply READY TO ISSUE. The coordinator sends at most one request after
that second reply.
Each miner may complete one pilot in this campaign. The coordinator processes ready miners within its resource limit. Several ready miners may wait briefly in reply order, but their eligibility is not reserved or denied while they wait.
-
Read the immutable operator runbook:
-
Open the public enrollment form:
https://github.com/Umi-BitSign/umi/issues/new?template=public-miner-pilot.yml
-
Post your SN78 UID, public SS58 hotkey, host platform, inference device, and lowercase SHA-256 model revision. Never post a seed phrase, key, wallet file, password, private model URL, or credential.
The miner must control a registered SN78 hotkey without a validator permit. Its
serving record must announce a stable, globally routable literal IP and explicit
port. That origin must serve valid Web PKI HTTPS and forward only to the loopback
UMI pilot service. Publishing serve-axon is signed by the miner hotkey; it does
not require the subnet-owner key.
Release CI covers Linux x86_64 and Apple Silicon macOS. Linux arm64 uses the same Python protocol service but is not release-tested in CI. Miners may use their own async translator or private Unix-socket model sidecar. The public S1 r2 reference model is an optional Linux backend, not a requirement.
The active campaign coordinator is:
5GsPXiSyzpK3rRoeAmjT4F5Cqa1RmP1CyBvNpwNDsDejyNZ4
The initial expired cases were bound to this historical coordinator hotkey:
5EstEFVxTFM6pm71GM8Y18DDAa1ro7C1e2w9pCsrwFhWT2n5
Those archives have expired and must not be reused. Each new case must match the active coordinator and pinned UMI revision posted on its enrollment issue. UMI will not silently substitute another signer.
Each fresh case is bound to its announced coordinator and one miner. UMI resolves the endpoint again from finalized Finney state and has no URL override. Once a request may have been issued, the case is never rerun. A signed error or bounded request failure is still published when the remaining reveal and publication steps complete; an exceptional later failure leaves a verified non-feed attempt journal on the public issue.
After UMI confirms receipt, restore any previous production axon or clear the temporary pilot record. Serving writes are rate-limited, so record the old endpoint and plan that maintenance window before enrolling.