mppx@0.4.9

Patch Changes

• d9b651d: Added Store.redis() adapter for standard Redis clients (ioredis, node-redis, Valkey) with BigInt-safe serialization.
• b69bbee: Fixed Express middleware hanging by constructing a Fetch Request directly from Express's req API.
• 7da6cfd: Fixed SSE header normalization.
• a2c6cc9: Skipped route amount/currency/recipient validation for topUp and voucher credentials. These POSTs carry no application body so the route's request hook may produce a different amount than the challenge echoed from the original request. The on-chain voucher signature is the real validation.

mppx@0.4.8

Patch Changes

• 99920d0: Updated validation.

mppx@0.4.7

Patch Changes

• 2a0b88e: Fixed cooperative close to sign the server-reported spent amount instead of the high-water mark (cumulativeAmount), preventing overcharging when actual usage was below the pre-authorized voucher amount.

mppx@0.4.6

Patch Changes

• 281005c: Added support for feePayer as a URL string on tempo method.

mppx@0.4.5

Patch Changes

• bbd4b3f: Updated Moderato (testnet) escrow contract address to 0xe1c4d3dce17bc111181ddf716f75bae49e61a336.

mppx@0.4.4

Patch Changes

• b09a35a: fix: update getChannel ABI field order to match new escrow contract
• c520705: Fixed Client.getResolver to inject Tempo serializers onto clients missing them, preventing the default serializer from rejecting Tempo-specific transaction fields.
• b09a35a: chore: update mainnet escrow contract address

mppx@0.4.3

Patch Changes

• 7f8d103: chore: update mainnet escrow contract address

mppx@0.4.2

Patch Changes

• c089da5: Added CLI config via mppx.config.(js|mjs|ts). Allows for extending mppx CLI to support non-built-in methods.

mppx@0.4.1

Patch Changes

• f2bc051: Support keychain V2 (0x04) signatures via ox 0.14 upgrade

mppx@0.4.0

Minor Changes

• 143ebc9: Support handler function refs in compose().

  • [mppx.tempo.charge, { amount: '1' }] syntax — compose() now accepts handler function references (e.g. mppx.tempo.charge) as the first element of entry tuples, in addition to Method.AnyServer objects and "name/intent" string keys.
  • _method metadata on nested handlers — nested handler functions are tagged with their source Method.AnyServer, enabling compose() to resolve the correct handler.

Patch Changes

• db2033c: Set feeToken during server co-sign and simulation for fee-payer transactions.

  When the client sends a fee-payer (0x78) envelope, feeToken is intentionally omitted. The server must set it at co-sign time, but previously never did — causing "Fee token spending limit exceeded" errors. Now resolves feeToken from the deserialized transaction or falls back to the chain's default currency.