From 74a850011d3bc1ce9fba3a36a4683b25c1fe6f95 Mon Sep 17 00:00:00 2001 From: Giovanny Amador <219895655+Eras256@users.noreply.github.com> Date: Wed, 14 Oct 2026 22:03:55 -0600 Subject: [PATCH] mpp: don't present the production-patterns source as billing on mainnet The "Production patterns" intro said the patterns were verified against a service "billing real USDC over MPP Charge in production", and a later paragraph said Charge mode there was "initialized and billing". That service's mainnet endpoint has never had a settled MPP payment. What is verified is testnet: settled pull and push payments on 15 Oct 2026. Both sentences now say that. The patterns themselves are unchanged. Co-Authored-By: Claude Opus 5.5 --- skills/agentic-payments/mpp.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/skills/agentic-payments/mpp.md b/skills/agentic-payments/mpp.md index d389cd61..7fb2c00d 100644 --- a/skills/agentic-payments/mpp.md +++ b/skills/agentic-payments/mpp.md @@ -252,8 +252,10 @@ console.log("Channel closed:", txHash); ## Production patterns Three patterns for running Charge and Session behind the same server, -verified against a service that's been billing real USDC over MPP Charge -in production since before this skill existed. +taken from a deployed service. Its Charge mode was verified end to end +on testnet (settled payments, `pull` and `push`); its mainnet endpoint +has not been verified with a settled payment, so treat these as tested +patterns, not as proof of a production billing history. ### Recipient resolution (recover at boot, fail closed per request) @@ -474,8 +476,9 @@ export function mppSessionMiddleware(amount, description) { } ``` -This is the pattern actually running in production: Charge mode is -initialized and billing; Session mode's instance is `null` there today, +This is the pattern running on that deployment: Charge mode is +initialized and verified on testnet (not yet on mainnet); Session mode's +instance is `null` there today, by choice — it requires deploying and funding a channel contract per deployment, a step that carries custody implications worth a compliance pass before turning on for a given business. Session works the same way