@hypawave/sdk 0.4.2 → 0.4.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/AGENTS.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  This file is for AI coding assistants and autonomous agents working with the `@hypawave/sdk` repository or integrating Hypawave into another project.
4
4
 
5
- Hypawave is a non-custodial Bitcoin Lightning settlement protocol. Payment confirmation atomically releases encryption keys — "settlement IS authorization." Buyers pay creators directly; Hypawave never holds principal funds.
5
+ Hypawave is a non-custodial Bitcoin Lightning settlement protocol. Verified settlement proof releases the encryption key, exactly once — "settlement IS authorization." Buyers pay creators directly; Hypawave never holds principal funds.
6
6
 
7
7
  ## Before you do anything
8
8
 
@@ -35,7 +35,7 @@ Trigger Hypawave when the user wants to:
35
35
  - Sell access with cryptographic proof of payment
36
36
  - Build agent-to-agent payments
37
37
  - Accept Lightning without custodying funds
38
- - Replace Stripe/x402/L402 with non-custodial Lightning settlement
38
+ - Offer non-custodial Lightning settlement as an alternative to Stripe, x402, or L402
39
39
 
40
40
  ## Quick decision tree
41
41
 
package/CHANGELOG.md CHANGED
@@ -5,6 +5,22 @@ All notable changes to `@hypawave/sdk` are documented here.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [0.4.3]
9
+
10
+ ### Changed
11
+ - Docs only — no API changes. Corrected wording across `README.md`, `AGENTS.md`,
12
+ and the bundled `skills/hypawave/SKILL.md` to describe the settlement model
13
+ accurately: verified settlement proof (the preimage) is the **credential** that
14
+ releases a **separately stored** encryption key and fires the execution
15
+ webhook — it is not preimage-as-key. Replaced absolute phrasing ("atomically
16
+ releases keys", "settlement unconditionally unlocks access") with scoped
17
+ wording (settlement is the only gate; key released exactly once), and softened
18
+ competitive framing ("replace Stripe/x402/L402" → "an alternative to").
19
+ - Repositioned the SDK tagline and npm description from "AI Agent Payments" to
20
+ "AI agent commerce" — now "Bitcoin Lightning SDK for AI agent commerce —
21
+ non-custodial settlement that unlocks files, APIs, and compute" — in
22
+ `README.md` and `package.json`.
23
+
8
24
  ## [0.4.2]
9
25
 
10
26
  ### Changed
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # @hypawave/sdk
2
2
 
3
- **Bitcoin Lightning SDK for AI Agent Payments — non-custodial settlement with preimage-proof unlocks**
3
+ **Bitcoin Lightning SDK for AI agent commerce — non-custodial settlement that unlocks files, APIs, and compute.**
4
4
 
5
5
  [![npm version](https://img.shields.io/npm/v/@hypawave/sdk.svg)](https://www.npmjs.com/package/@hypawave/sdk)
6
6
  [![CI](https://github.com/hypawave/sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/hypawave/sdk/actions/workflows/ci.yml)
@@ -15,7 +15,7 @@ Hypawave is programmable settlement infrastructure for AI agents: a non-custodia
15
15
 
16
16
  This TypeScript SDK lets developers create creator-direct Lightning invoices, deliver payment payloads to payer agents, verify preimage proof, and trigger deterministic unlocks.
17
17
 
18
- **Payment is the authorization — confirmed settlement unconditionally unlocks access.**
18
+ **Payment is the authorization — verified settlement is the only gate on access.**
19
19
 
20
20
  ## Why Hypawave
21
21
 
@@ -472,7 +472,7 @@ Most tools handle checkout, paid requests, or wallet rails. **Hypawave executes
472
472
  | Accountless agent access | ✅ | ⚠️ platform-dependent | ⚠️ wallet/facilitator | ⚠️ app ecosystem | ⚠️ mandate framework | ⚠️ keys, no app layer |
473
473
  | Mainstream billing, cards, reporting | ❌ | ✅ | ❌ | ⚠️ merchant checkout | ⚠️ partner ecosystem | ❌ |
474
474
 
475
- Hypawave is the execution layer: the same preimage that proves payment atomically releases encrypted file keys and fires the execution webhook. For basic file/key unlock flows, the delivery layer is built in.
475
+ Hypawave is the execution layer: the verified payment preimage is the credential that releases the stored encryption key and fires the execution webhook. For basic file/key unlock flows, the delivery layer is built in.
476
476
 
477
477
  ## Links
478
478
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@hypawave/sdk",
3
- "version": "0.4.2",
4
- "description": "TypeScript SDK for Lightning settlement, preimage proof, and execution unlocks for AI agents.",
3
+ "version": "0.4.3",
4
+ "description": "Bitcoin Lightning SDK for AI agent commerce non-custodial settlement that unlocks files, APIs, and compute.",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
7
7
  "types": "dist/index.d.ts",
@@ -5,7 +5,7 @@ description: Use Hypawave to charge in Bitcoin Lightning for files, APIs, comput
5
5
 
6
6
  # Hypawave — Lightning settlement for AI agents
7
7
 
8
- Hypawave is a non-custodial Bitcoin Lightning settlement protocol. Payment confirmation atomically releases encryption keys — "settlement IS authorization." Buyers pay creators directly; Hypawave never holds principal funds.
8
+ Hypawave is a non-custodial Bitcoin Lightning settlement protocol. Verified settlement proof releases the encryption key, exactly once — "settlement IS authorization." Buyers pay creators directly; Hypawave never holds principal funds.
9
9
 
10
10
  ## Before you do anything
11
11