@smartledger/bsv 4.2.1 → 4.5.0

package/CHANGELOG.md

@@ -5,6 +5,85 @@ All notable changes to SmartLedger-BSV will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [4.5.0] - 2026-06-09
+
+### Added — declarative covenant DSL + stack debugger
+
+- **`SmartContract.policy()` — a declarative covenant DSL.** Describe a spending
+  policy and compile it to a verified OP_PUSH_TX locking script, no opcodes:
+  ```js
+  const c = bsv.SmartContract.policy()
+    .payTo(aliceAddr, 9500)   // the spend MUST create this output...
+    .lockUntil(800000)        // ...with nLockTime >= 800000
+    .compile()
+  // c.lock, c.outputs, c.unlock(spendTx, satoshis)
+  ```
+  Clauses AND together (each compiles to one preimage-field check on a single
+  OP_PUSH_TX authentication). `payTo` pins outputs via `hashOutputs`; `lockUntil`
+  checks the `nLockTime` field. The compiled `unlock()` grinds the OP_PUSH_TX
+  nonce *from the locktime floor upward* so it never collides with a `lockUntil`
+  constraint. Shortcuts: `policy.perpetual(fee)`, `policy.token(fee, ownerHash)`.
+- **`SmartContract.trace()` — a covenant stack debugger.** Step-traces a
+  locking/unlocking pair and records the stack + alt-stack after every opcode, so
+  you can watch an OP_PUSH_TX covenant build its signature and enforce its
+  constraints. `SmartContract.Debugger.format(result)` pretty-prints it.
+- **TypeScript types** for the full covenant suite in `bsv.d.ts`
+  (`SmartContract.{PushTx,PELS,Token,Locks,CovenantHelpers,policy,Policy,trace,
+  Debugger}` + `enableGenesis`/`verifyScript`/`perpetualCovenant`/…).
+
+New mocha suite `test/smart_contract/dsl_debugger.js` (7 specs). Full suite
+4199 → 4206 passing. Lint clean; `bsv.d.ts` type-checks.
+
+## [4.4.0] - 2026-06-07
+
+### Added — BSV string opcodes OP_SUBSTR / OP_LEFT / OP_RIGHT
+
+- **Implemented the re-enabled BSV (Chronicle) string opcodes in the script
+  interpreter.** They were declared in the opcode map (`0xb3`/`0xb4`/`0xb5`) but
+  unimplemented — executing one returned `BAD_OPCODE`. Now they evaluate with the
+  original Satoshi semantics:
+  - `OP_LEFT  (in n -- out)` — the first `n` bytes.
+  - `OP_RIGHT (in n -- out)` — the last `n` bytes (`OP_RIGHT 0` ⇒ empty, not the
+    whole string).
+  - `OP_SUBSTR (in begin size -- out)` — `in[begin : begin+size]`.
+  Out-of-range lengths clamp to the string length; negative arguments fail with
+  `SCRIPT_ERR_INVALID_NUMBER_RANGE`. New test: `test/script/string_ops.js`.
+
+### Changed
+
+- **Covenant field-extraction now uses these opcodes**, shrinking the scripts
+  further: perpetual covenant 429→**421 B**, ownership token 493→**482 B**, value
+  covenant 428→**424 B** (vs. the verbose `OP_SIZE/OP_SUB/OP_SPLIT/OP_NIP` form).
+
+Full mocha suite 4190 → 4199 passing, 0 failing. Lint clean.
+
+## [4.3.0] - 2026-06-07
+
+### Changed — mainnet hardening of OP_PUSH_TX covenants
+
+- **Canonical low-S signatures.** The OP_PUSH_TX grind now requires `s <= n/2`,
+  so the in-script signature is canonical (low-S) and non-malleable, and the
+  covenant verify path enforces `SCRIPT_VERIFY_LOW_S`. This makes the produced
+  spends standard for mainnet relay/mining. Cost: zero extra script bytes — the
+  constraint is satisfied by the spender's grind, not by added opcodes.
+  (`SmartContract.PushTx.sFromPreimage`, `CovenantHelpers.flags`.)
+- **Smaller scripts (−22 bytes per covenant).** `pushTxCore` now shares a single
+  `Gx` push between the DER signature's r-value and the `02||Gx` public key
+  (parked on the alt-stack) instead of embedding the 32-byte constant twice.
+  Authenticator 404→382 B, value covenant 450→428 B, perpetual 451→429 B,
+  ownership token 515→493 B.
+
+### Notes
+
+- The remaining ~382-byte floor is intrinsic to OP_PUSH_TX on BSV: ~248 B is the
+  two mandatory 32-byte endianness reversals (big-endian hash ↔ little-endian
+  script arithmetic ↔ big-endian DER), the rest is fixed secp256k1 constants and
+  the DER template. There is no single-opcode byte reverse on BSV —
+  `OP_REVERSEBYTES` is a Bitcoin Cash opcode, not part of the BSV opcode set, so
+  the `OP_SPLIT`/`OP_SWAP`/`OP_CAT` reversal gadget is the correct approach.
+- New test: `test/smart_contract/covenants.js` proves the grind yields low-S
+  signatures enforced under `SCRIPT_VERIFY_LOW_S`. Full suite 4189 → 4190.
+
 ## [4.2.1] - 2026-06-07
 
 ### Docs