Off-chain data and Base integration
How Weave connects peer-to-peer data and work to on-chain escrow and settlement.
Weave’s composable data abstractions organize and share data off-chain. Optional Base contracts connect selected economic agreements to on-chain state. Using Strand, Lens or Locus does not require MINT, a Life account or a blockchain transaction.
What crosses the boundary
| Off-chain work | On-chain role | Evidence needed |
|---|---|---|
| Cores compute request, execution and result artifact | Escrow, settlement and timeout/refund rules | Matching job identity, verified result, contract state and canonical settlement receipt. |
| Cores storage and retrieval of encrypted content | Funded lease, verification deadlines and refund/settlement rules | Correct content and lease identity, actual retrieval, verification state and payment receipt. |
| Outlets work agreement, submission and review | Work escrow and payment state machine | Authorized participants, matching terms, submission/review outcome and canonical payment state. |
| MINT or another explicitly supported asset | Transfer/payment according to the selected contract | Exact chain, token address, decimals, allowance, amount, recipient and receipt. Token support is contract-specific. |
A content hash can bind an agreement to bytes; it does not prove that work was done, remains available or is authorized. A signed message is not a payment receipt. Track off-chain delivery, contract submission, inclusion and final settlement separately.
Current integration status — 15 October 2026
Retained Cores evidence includes a paid CPU computation and encrypted storage recovery on Base Sepolia. Outlets has a Sepolia escrow deployment and prior authenticated headless tooling evidence; the complete hire-to-payment flow is not yet verified. Its latest bounded service restart encountered an image-registry access error. Nods has a qualified authorization/evidence-boundary source candidate, but its legacy anchor format does not establish Base support.
These observations do not establish mainnet deployment. Base Sepolia uses chain ID 84532; Base mainnet uses 8453. Existing economic clients and contracts include testnet restrictions. Do not replace a chain ID or reuse a testnet address and call it a mainnet release. A mainnet release requires the exact supported contracts, runtime code, addresses, custody, funding rules and real end-to-end evidence.
Application flow
An application identifies the permitted resource and current terms, prepares the exact unsigned contract action, and uses a separately authorized protected wallet. Preserve the operation ID and reconcile uncertain transactions before retrying. Keep keys outside model context. A discovered peer, connected wallet or loaded skill does not grant transfer authority.
Data and artifacts remain under their off-chain confidentiality and access rules. Store only the commitments and contract state required by the agreement on-chain. Do not publish private prompts, file contents, credentials or hidden task state in transaction data.
Weft can distribute immutable artifacts used by a Cores job or another application. That is a composition opportunity, not proof that Weft itself includes a deployed payment or storage-guarantee contract. Read composable data abstractions and the selected service’s current contract before connecting the two.
