feat(listing): storage + GPU capability fields (v0.2.0)#3
Merged
NetworkTheoryAppliedResearchInstitute merged 2 commits intoJul 13, 2026
Merged
Conversation
CapabilityListing gains first-class storage and GPU advertisement so
phones, TVs, and NAS nodes can join as storage/GPU contributors:
- WorkloadOptIn gains Storage (advisory, same SPEC 5.1 discipline as
Compute/Print; mirrors the coordinator's existing
compute/storage/printing opt-out trichotomy).
- Capacity gains StorageCommitMB: long-lived storage committed to the
network (shard hosting), deliberately distinct from DiskMB job
scratch. Encryption, sharding, and audit of stored data are
frontend/agent concerns outside the protocol; the wire never carries
stored content.
- New GPUs []GPUCapability{API, Model, VRAMMB}, mirroring Printers.
Advertising a GPU is the opt-in; API in {vulkan, nnapi, cuda, metal}.
- JobSpec.Workload doc comment admits "storage".
CanonicalBytes changes (GPUs after Printers; StorageCommitMB after
DiskMB; OptIn.Storage after OptIn.Print): a breaking v0 encoding
change while v0 is declared UNSTABLE. testdata/vectors.json
regenerated; testdata/reproduce_spec.py updated and passing 43/43
against the new golden file. Consumers (Cloudy, SoHoLINK) must bump
in lockstep; tag v0.2.0 at merge.
Signed-off-by: Jodson Graves <info@ntari.org>
This was referenced Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
CapabilityListinggains first-class storage and GPU advertisement so phones, Android TVs, and NAS boxes can join as storage/GPU contributor nodes (the Class B/C/D seam):WorkloadOptIn.Storage— advisory, same §5.1 discipline as Compute/Print; mirrors the coordinator's existing compute/storage/printing opt-out trichotomy (migration 014).Capacity.StorageCommitMB— long-lived storage the node commits to the network (shard hosting), deliberately distinct fromDiskMBjob scratch so a node can offer either without the other.GPUs []GPUCapability{API, Model, VRAMMB}— mirrors thePrintersrepeat pattern. Advertising a GPU is the opt-in;API ∈ {vulkan, nnapi, cuda, metal}.JobSpec.Workloaddoc comment admits"storage".Scope boundary (deliberate)
How stored data is encrypted, sharded, and audited is a frontend/agent concern outside the protocol — client-side encryption + erasure coding + proof-of-storage audits live above the thin waist. The wire never carries stored content; this PR only adds the capacity advertisement. A challenge/proof message pair is intentionally deferred until the audit protocol is spec'd.
Breaking change (allowed: v0 is UNSTABLE)
CanonicalBytesorder changes:GPUsafterPrinters;StorageCommitMBafterDiskMB;OptIn.StorageafterOptIn.Print. SPEC §4.1 updated.Verification
go build ./...,go vet ./..., fullgo test ./...green locally.testdata/vectors.jsonregenerated (go test ./vectors -update); listing vector now exercises 2 GPUs (repeat encoding), storage capacity, and the storage opt-in.testdata/reproduce_spec.pyupdated and passing 43/43 against the regenerated golden file — an independent (Python) implementation reproduces the new canonical bytes and verifies all signatures.After merge
Tag v0.2.0, then bump both consumers (Cloudy, SoHoLINK) in lockstep — no third-party consumers exist yet.
🤖 Generated with Claude Code