E05-LP: Yes
Rationale
Pinata identifies Spinamp as an actual customer using its IPFS nodes to store and distribute music in an October 2024 account. Its operational documentation describes its nodes retrieving content directly from customer IPFS Desktop peers. IPFS documentation identifies libp2p as its peer networking layer. Together these support external practical adoption of libp2p through Pinata-operated IPFS infrastructure; the component mapping is a documentary inference.
Assessment method
Primary operator evidence and explicit component mapping under revised E05
Source context
Pinata operator/customer account (7 October 2024), Matt Ober operational documentation (1 August 2023), and IPFS libp2p documentation
Outstanding qualification
Pinata is the credited network operator; a listener reaching an HTTP gateway is not thereby a libp2p endpoint. The provider-authored customer account is commercial evidence, not an independent uptime audit. Transport, library versions, QUIC-only operation, migration and post-quantum settings of the selected column are not attested. IPFS content semantics and Pinata service guarantees are not attributed to libp2p. No new network transaction was performed.
Public sources
- https://pinata.cloud/blog/how-spinamp-doubled-developer-efficiency-by-outsourcing-ipfs-hosting-to-pinata-2/
- https://knowledge.pinata.cloud/en/articles/5508876-how-to-use-ipfs-desktop-with-pinata
- https://docs.ipfs.tech/concepts/libp2p/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round641.html