The protocol declares GetPublicMeta and PosChallenge, but the shipped Starshine facade exposes only Put/Get/Delete and the upload path assigns fixed starshine-api:node-XX provider labels.
For a deployment to use Starshine as an encrypted evidence/archive replica, an independent verifier needs:
- supported JS APIs (or a documented CLI) for metadata and proof retrieval;
- an interoperable verifier and test vectors;
- an authenticated statement of actual provider/node identities and their independent operators;
- durability/replication and failure-domain semantics; and
- clear language distinguishing availability/proof-of-storage from append-only ledger inclusion.
Could the project publish this as a versioned storage-proof profile? The current protocol declaration is useful, but it is insufficient to audit a real deployment from the SDK alone.
The protocol declares GetPublicMeta and PosChallenge, but the shipped Starshine facade exposes only Put/Get/Delete and the upload path assigns fixed starshine-api:node-XX provider labels.
For a deployment to use Starshine as an encrypted evidence/archive replica, an independent verifier needs:
Could the project publish this as a versioned storage-proof profile? The current protocol declaration is useful, but it is insufficient to audit a real deployment from the SDK alone.