Providers with declared capacity
Providers register capacity, regions, pricing, replication commitments, receipt keys, and stake. Consumers can evaluate the terms before opening a request.
Paid availability for off-chain artifacts
Keep the artifact. Account for its availability.
Sigil’s storage marketplace connects provider stake, pinning agreements, funded escrow, receipts, and sampled proofs for Weave and Weft artifacts.
Storage MarketplaceIllustrated study
Input / work / result
Work happens off-chain. Its agreement leaves a record.
01 / Built for a purpose
A commitment is useful when the bytes can be found.
Models, datasets, evidence bundles, and application assets can be too large for chain state. The storage marketplace keeps those bytes off-chain while recording the agreement to retain them and the proof material used for payment and challenges.
A pin request with escrow
The owner identifies an artifact with its Weft root and funds a request. A provider accepts it within the configured price, capacity, and replication constraints.
Receipts bound to the artifact
Settlement checks the provider signature, exact artifact and root binding, sampled chunk proofs, and available escrow before paying the provider.
Challenges with a defined outcome
A challenge selects proof material against the committed root. The supported resolution path can restore the contract or apply suspension, slashing, and challenger rewards.
Bytes stay outside consensus
Validators check deterministic commitments and proofs. They do not fetch arbitrary model files or datasets while executing a block.
02 / From intent to outcomeA clear path through
A clear path through
storage marketplace.
- 01
Prepare the artifact
Create the required identity-bound artifact commitment and Weft root.
- 02
Fund and accept
Open a pin request and match it with a provider under the supported terms.
- 03
Verify and settle
Submit receipts and sampled proofs, settle accepted work, and use challenges when the agreement is contested.
The details matterGood questions.
Good questions.
Clear answers.
Is this a hosted file-upload service?
The current surface is a headless protocol for provider records, pinning, settlement, and challenges. Client software and provider availability are separate parts of the end-to-end experience.
How is this different from Evidence Anchoring?
An evidence anchor records a digest and attribution. A storage contract adds a paid availability agreement, provider obligations, and proof-based settlement. An anchor alone does not pin the bytes.
Keep exploringOne capability.