Service Scope
Define services (pinning, replication, gateways), technical interfaces (HTTP API, IPFS daemon endpoints), permitted content types, and quotas or limits on storage and bandwidth.
A clear, well-drafted IPFS Service Contract reduces operational risk, defines expectations for uptime and content persistence, and sets financial and liability boundaries between parties. Proper terms protect intellectual property, address takedown or content-dispute procedures, and limit exposure for data loss or unavailability. For U.S.-facing agreements, electronic execution is generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA statutes where adopted, but some exceptions and consumer-disclosure rules may apply.
The IPFS Service Contract is used by a variety of entities that store or publish distributed content and need formal service, liability, or compliance terms.
The contract also fits vendors offering pinning-as-a-service, CDN integrators, and customers requiring contractual remedies, where clearly defined SLAs and exportability provisions are essential.
An officer or executive with corporate signing authority (CEO, COO, CFO) typically signs for the organization. Where corporate bylaws require delegation, attach an authorization certificate or board resolution showing delegated authority for the named signer.
Procurement managers, general counsel, or an assigned contract administrator may sign operationally if the organization’s internal authorization policy grants them signature authority for service agreements up to defined dollar thresholds.
Define services (pinning, replication, gateways), technical interfaces (HTTP API, IPFS daemon endpoints), permitted content types, and quotas or limits on storage and bandwidth.
Specify uptime or availability targets, measurement method, scheduled maintenance windows, and remedies such as service credits for missed SLAs.
Address retention, deletion requests, content takedowns, export formats for CIDs, and whether provider maintains off-chain manifests or backups.
Clarify ownership of content, license grants for storage/serving, DMCA takedown procedures, and indemnity for IP infringement claims.
Limitations on damages, indemnification scope, caps on liability, and carve-outs for gross negligence or willful misconduct.
Encryption at rest and in transit, breach notification timelines, data segregation, and obligations for regulatory compliance where applicable.
| Field | Configuration |
|---|---|
| Signing Order | Set sequential or parallel signing depending on internal approvals. |
| Authentication | Use email link or SMS code; enable stronger methods for high-risk contracts. |
| Required Fields | Make party name, date, and signature required; lock key clauses to prevent edits. |
| Audit Trail | Capture IP, timestamp, and events for each signer for admissibility. |
Choose a signing platform that meets authentication, audit, and retention needs for the contract.
Confirm the platform supports enforceability standards (ESIGN/UETA), audit trails, exportable signed PDFs, and secure long-term storage before execution.
Date when the contract obligations commence; enter as MM/DD/YYYY.
When provider begins pinning/replication activities; may differ from Effective Date.
Specify notice window to renew or decline (commonly 30–60 days before term end).
Required advance notice for termination without cause (commonly 30 days).
Define invoice terms (e.g., Net 30) and late fee calculation.
Final terms agreed and redlines accepted by both sides.
Legal teams confirm indemnities, IP language, and regulatory clauses.
Contract is signed by authorized representatives and date-stamped.
Provider performs technical onboarding, API keys issued, and test pins validated.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
A venture-backed data platform required guaranteed replication windows
A property manager used IPFS for static property documents