@integraledger/lcp-binding-evm-mpp 0.9.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @integraledger/lcp-binding-evm-mpp
 
+## 0.10.1
+
+**0.10.0 was staged and withdrawn before approval; this is that release, re-cut.** The conformance corpus
+was re-sealed after 0.10.0 was staged — its root moved `32fa90a6…` → `28bbf4ef…` when the vector tree was
+brought inside the prose gates — so the staged `lcp-conformance` tarball carried a seal that no longer
+matched the repository. The seal is what proves corpus authenticity to an independent implementer, and a
+published version cannot be replaced, so the whole set was rejected and re-cut rather than shipping one
+package that disagreed with its own source. No version 0.10.0 exists on the registry.
+
+Released as part of a flat `0.10.1` across the whole suite. One number describes the set that was built,
+tested and sealed together, so a consumer never has to work out which combination of versions was verified.
+
+This package has no source change of its own in this release. What moved across the suite: three exported
+names were corrected before anyone depends on them — `USDC_DECIMALS` became rail-qualified after it was
+found to mean 6 on three rails and 7 on Stellar under one name, `VISA_TAP_PLACEMENT_TIER_A` lost the tier
+it had baked into an identifier, and the memo codecs were named for the carrier they encode. Two wire
+identities were respelled to match the vocabulary they are written into. Five gates were added or widened,
+and a large number of documentation claims were corrected against the host specifications at HEAD.
+
 ## 0.9.0
 
 First public release.

package/README.md

@@ -83,7 +83,8 @@ Read against the host protocol's own live specifications, not LCP's Appendix C.
 
 **Two drifts found, recorded rather than smoothed over.**
 
-- **The core draft's identifier.** LCP v1.37 §C.1 and the completion plan both cite
+- **The core draft's identifier.** (Discharged: v1.38 §C.1 now records both identities and cites
+  `draft-httpauth-payment-00` as the family's own publication.) LCP v1.37 §C.1 cited
   `draft-ryan-httpauth-payment-01` (the IETF individual submission). paymentauth.org's own document index
   publishes the core scheme as **`draft-httpauth-payment-00.html`**. Both were read for this gate; they agree
   on §5.1.1 and on the seven slots. Treat the paymentauth.org copy as the live one — it is the family's own
@@ -168,7 +169,8 @@ from it, never occupied by it.
 ## Provenance
 
 Cut against `draft-evm-charge-00` and the core `Payment` scheme at paymentauth.org, gate discharged
-2026-07-30, and reconciled against LCP v1.37 §C.1 and §8.3.5 the same day. The derivation oracles in
+2026-07-30, and reconciled against LCP v1.37 §C.1 and §8.3.5 the same day; re-read against **v1.38 §C.1** on
+2026-08-12, which adopted the identifier finding below. The derivation oracles in
 `vectors/binding/mpp-evm-id-reuse.json` were produced by two independent keccak-256 implementations
 (pycryptodome and Foundry `cast keccak`), and `abi.encodePacked`'s string semantics were confirmed against
 Foundry's own encoder — neither of them the implementation under test.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integraledger/lcp-binding-evm-mpp",
-  "version": "0.9.0",
+  "version": "0.10.1",
   "description": "Welds an LCP record into an MPP settlement on EVM by Id-Reuse (LCP §8.3.5).",
   "keywords": [
     "lcp",
@@ -43,9 +43,9 @@
   "homepage": "https://github.com/IntegraLedger/integra-protocol/tree/main/packages/binding-evm-mpp#readme",
   "dependencies": {
     "viem": "2.55.11",
-    "@integraledger/lcp-binding-core": "0.9.0",
-    "@integraledger/lcp-binding-evm-common": "0.9.0",
-    "@integraledger/lcp-kernel": "0.9.0"
+    "@integraledger/lcp-binding-core": "0.10.1",
+    "@integraledger/lcp-kernel": "0.10.1",
+    "@integraledger/lcp-binding-evm-common": "0.10.1"
   },
   "devDependencies": {
     "@types/node": "24.13.3",