Get started
Current authorized tip: checking the signed index…. Until index verification succeeds, this page approves no build. Revoked releases stay withdrawn. GitHub and IPFS are byte transports; authenticate the expected digest and compare SHA-256 locally.
Platform-specific launch guidance appears only after the signed current tip verifies. A matching hash establishes byte integrity against that authenticated digest, not software safety.
- Prefer the authenticated three-file handoff when the operator issues one; otherwise use the signed Pages tip shown on Download and verify its SHA-256 on Verify.
- Two channels carry releases: GitHub Releases and IPFS. They are signed against the same release index, but a given build may publish the package to one and only signed metadata to the other — Download says which is which. Whichever you use, the SHA-256 you verify is the same.
- Confirm the pinned channel-index fingerprint locally; the webpage alone is not the trust root.
- Verify filename, bytes, and SHA-256 before running anything.
- Storage stays off until you deliberately opt in inside the desktop app.
This page never auto-downloads packages and never silently switches mirrors. IPFS-first signed artifacts plus an independently authenticated handoff are the authority.
Tester Network path
The signed tip enables two distinct workers, real Kubo, multi-block PoA, and 100 valueless test credits exactly once per accepted proof. Replay awards zero; restart and revocation are part of acceptance.
Standalone card (Forever Drive + voluntary pins)
When the verified current manifest authorizes standalone storage, the intended path is:
- Download the current tip
checking the signed index…from Download (or operator handoff), verify SHA-256, and launch. - Opt in Forever Drive at 20% inside the app.
- Browse → pin videos you choose. Voluntary pins share the same 20% quota; Forever Drive reservations keep priority. No compute, Brain, Neura, or paid rewards are claimed from local pins alone.
Joining the shared pool is not available yet
Pool assignment needs a private enrollment packet issued against a live HTTPS coordinator, and no such coordinator is published today. Until the operator announces one and issues you a packet, the tray's Copy Enrollment Request and Import Private Enrollment items have nothing to register against and will fail closed rather than pretend. That is expected, not a fault in your setup.
readyForPool stays truthful throughout — embedded-only mode is deliberately not pool-ready, and the app will keep saying so until a real coordinator assigns work.
When enrollment opens, identity is established only by an operator-issued authenticated packet bound to the tester. A username displayed on Pages would not imply access or reservation, so none is published here.
If the app does not open
Storage Preview only recovers a verified owned leftover on its local port. A healthy foreign or unverifiable listener is never force-killed. If an older Storage Preview window is already open, use the system-tray icon — a second double-click focuses that window.
If another unrelated program blocks the local preview port, close that program and open Storage Preview again.