@elisym/commerce 0.1.0 → 0.3.0

package/README.md

@@ -15,6 +15,7 @@ npm install @elisym/commerce @elisym/pay-core nostr-tools @solana/kit @solana-pr
 | Store profile       | 0                      | store         | `buildStoreProfileEvent`, `parseStoreProfile`                       |
 | Product             | 30402 (NIP-99, Gamma)  | store         | `buildProductEvent`, `parseProduct`, `priceInSubunits`              |
 | Orders, receipts    | 16 / 17 in a gift wrap | buyer / store | `buildOrderMessage`, `wrapOrderMessage`, `unwrapOrderMessage`       |
+| Payment reference   | -                      | -             | `deriveOrderPaymentReference`                                       |
 | Offer verification  | -                      | -             | `verifyOffer`, `evaluateOffer`, `isOfferPayout`                     |
 
 ## The one rule
@@ -33,6 +34,16 @@ if (!isOfferPayout(result.offer, caip19, challenge.payTo)) throw new Error('Not
 
 On a server, pass `verifyOffer` a `fetch` that refuses private addresses: the merchant's domain comes from the store's own profile.
 
+## The buyer side: `@elisym/commerce/buyer`
+
+The checkout widget and the elisym MCP buy through the same core. It covers:
+
+- loading and verifying the offer (`loadOffer` for a page, `loadOfferForAgent` for an agent);
+- placing the order and paying on Solana (`placeOrder`, `payWithSolana`);
+- following the store's answer (`watchSolanaPayment`, `listenForStatus`).
+
+Order records live behind an `OrderBackend`, a read-judge-write transaction for one product. Every money rule is judged in the core, never in a backend: one order is never paid twice, and nothing is paid before the store's inbox acknowledged the order. The backends are IndexedDB in the checkout, a locked and fsynced file in the MCP, and `MemoryOrderBackend` for tests.
+
 ## License
 
 MIT