You publish an offer naming a price, an asset, terms and deliverable hashes and three time windows. A buyer proposes an agreement against it and you accept. From there the agreement walks eight states from proposed to resolved, driven by 13 activity types, with commitments, signed execution attestations, progress reports, deliveries and disputes recorded as kernel state. The module never moves money: escrow, a spend budget or a send does that, and the agreement only names the escrow.

What it does

The service module of the LayerX agent domain records offers, agreements, task commitments, execution attestations, progress reports, deliveries, outcomes and disputes as kernel state. A provider publishes an offer naming a price, an asset, a terms hash, a deliverable specification hash, a delivery deadline, an acceptance window, a dispute window and an expiry; a buyer proposes an agreement against that offer, and the provider accepts it. From there the agreement walks an eight-state machine: proposed, formed, committed, delivered, accepted, rejected, disputed and resolved. 13 activity types drive it, from 0x00050001 to 0x0005000d. The module never touches balances: money moves separately through escrow, a spend budget or a send, and the agreement only names the escrow identifier.

Key capabilities

• Offers carry price, asset, terms hash, deliverable hash, three time windows and an expiry.
• Agreements bind a buyer and provider to one offer and one matching terms hash.
• Providers commit to a task hash with a deadline and a resource bound.
• Signed tool-execution attestations record input and output commitments and resource units.
• Progress reports are monotonic in basis points, with 10000 marking complete.
• Rejection names contested deliverable hashes; either party can then open a dispute.

Differentiators

The module is structurally barred from moving value: any attempt to mutate a balance returns LXP_ERR_MODULE_MAY_NOT_WRITE_BALANCE, and an effect audit runs after every service activity and fails the batch if a transfer or any monetary effect was produced. Timeouts resolve rather than hang: unaccepted deliveries past the acceptance window are closed by the offer's default outcome, accept (1) or reject (2), and reported as event type 14.

Outcomes

• Agree terms, deadline and dispute window before any work starts.
• An unaccepted delivery closes on the offer's default outcome, not a stall.
• An effect audit fails the batch if a service activity moves value.

Technical notes

• Records are fixed-width: offer 252 bytes, agreement 247 bytes plus 16 contested-hash slots, commitment 220 bytes, execution 416 bytes, attestation preimage 344 bytes, delivery 138 bytes, progress 245 bytes. LX_SERVICE_MAX_DELIVERABLES is 16 and bounds deliverables, contested hashes and evidence hashes alike.
• Errors are specific: AGREEMENT_STATE (-706), OFFER_UNAVAILABLE (-723), TERMS_MISMATCH (-724), INVALID_ATTESTATION (-725), DELIVERABLE_MISMATCH (-726), DELIVERY_DEADLINE_PASSED (-727), UNAUTHORIZED_DISPUTANT (-728).
• Every delivered item's hash must equal the offer's single deliverable_specification_hash, and each item needs a non-zero size and availability reference.
• Dispute resolution is recorded by either party to the agreement; it sets a ruling, a provider share in basis points and an escrow resolution identifier. There is no separate arbiter service in the repository.
• The compute and data marketplace above the registry is one program crate, layerx-programs-market, plus a reference application under platform/examples/marketplace. It registers staked capacity offers, opens leases, commits metered usage and settles after a challenge window, with three declared verification models: bonded, attested and fraud-provable. Its handlers build for wasm32 only. Leases run against sandbox activity 0x00090009, whose call context exposes five slots: lease id, escrow account, asset, fee destination and expected lease digest.
• Not yet implemented: delivery-reputation scoring, capacity underwriting and a portable reputation record. The 13 service activities are reachable through the kernel activity surface; no SDK or CLI wrapper for them exists yet. Each one is a LayerX activity and costs 1/10 of a cent.

import { Client, parseAmount } from "layerx-sdk";

const offer = await client.serviceOfferPublish({
  offerId, assetId, termsHash, deliverableSpecificationHash,
  price: parseAmount("2500000000000000000"),
  deliveryDeadline: 1764547200000n,
  acceptanceWindow: 86400000n,
  disputeWindow: 172800000n,
  defaultOutcome: "accept",
  offerExpiry: 1764460800000n,
});

More in LayerX agent domain