From ee77c0f2ca46f6b18a07b9a788f44da51702f6e1 Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Mon, 11 May 2026 16:48:51 -0400 Subject: [PATCH 1/4] =?UTF-8?q?=F0=9F=93=9D=20Add=20transcript=20follow-up?= =?UTF-8?q?s?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meeting-notes/2026-05-07.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/meeting-notes/2026-05-07.mdx b/meeting-notes/2026-05-07.mdx index b045a071d..66604e24a 100644 --- a/meeting-notes/2026-05-07.mdx +++ b/meeting-notes/2026-05-07.mdx @@ -95,3 +95,15 @@ Concrete examples worth thinking about: - **AI auditing tools** — auditing a Soroban contract for vulnerabilities, with the caveat that no AI auditor should be the only thing standing between a project and mainnet. - **Agent service marketplaces** — agents paying agents per-call, with MPP as the settlement layer. - **Usage-based infrastructure** — anything where the cost shape is "metered, often, small." + +## Q&A and Follow-Ups + +The live questions mostly centered on how to choose between charge mode and channel mode, how MPP relates to sponsored transactions, and how to give agents access to Stellar wallets safely. + +For mode selection, the answer comes back to cost shape: if a service has an obvious per-request cost, charge mode is enough. If the service has a metered cost that accumulates quickly — tokens, data stream updates, repeated analytics calls, or another high-frequency unit — channel mode is the better fit. + +Sponsored transactions are separate from MPP, but they can be used alongside it. MPP defines the payment challenge, receipt, and settlement model for paid access. Fee sponsorship lets another wallet or relayer cover transaction fees so the user does not have to hold XLM just to complete the interaction. + +For agent wallets, the simplest testnet path is still to use Stellar CLI keys while prototyping. For production-oriented work, the meeting pointed builders toward OpenZeppelin policy-based smart accounts, where a wallet can express rules such as requiring human approval above a certain transaction threshold. + +The meeting closed with two possible follow-up topics: the Yardstick protocol upgrade and secure wallet/key-management patterns for autonomous agents. There was also interest in a one-page version of the demo and in future coverage of Stellar Tools and Lobstr Cash. From f414d8cd70fab2f925d7105c4dbcabd1721b47fe Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Mon, 11 May 2026 16:49:40 -0400 Subject: [PATCH 2/4] =?UTF-8?q?=F0=9F=93=9D=20Title=20MPP=20meeting=20note?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meeting-notes/2026-05-07.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meeting-notes/2026-05-07.mdx b/meeting-notes/2026-05-07.mdx index 66604e24a..26a08a9f9 100644 --- a/meeting-notes/2026-05-07.mdx +++ b/meeting-notes/2026-05-07.mdx @@ -1,5 +1,5 @@ --- -title: "2026-05-07" +title: "Machine Payments Protocol Deep Dive" authors: kaankacar tags: [developer] --- From 93d73f7beaf687d4791a77fc202cc5cdc09131f7 Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Mon, 11 May 2026 16:51:34 -0400 Subject: [PATCH 3/4] =?UTF-8?q?=F0=9F=93=9D=20Remove=20meeting=20note=20fo?= =?UTF-8?q?llow-ups?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meeting-notes/2026-05-07.mdx | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/meeting-notes/2026-05-07.mdx b/meeting-notes/2026-05-07.mdx index 26a08a9f9..1a36753f2 100644 --- a/meeting-notes/2026-05-07.mdx +++ b/meeting-notes/2026-05-07.mdx @@ -95,15 +95,3 @@ Concrete examples worth thinking about: - **AI auditing tools** — auditing a Soroban contract for vulnerabilities, with the caveat that no AI auditor should be the only thing standing between a project and mainnet. - **Agent service marketplaces** — agents paying agents per-call, with MPP as the settlement layer. - **Usage-based infrastructure** — anything where the cost shape is "metered, often, small." - -## Q&A and Follow-Ups - -The live questions mostly centered on how to choose between charge mode and channel mode, how MPP relates to sponsored transactions, and how to give agents access to Stellar wallets safely. - -For mode selection, the answer comes back to cost shape: if a service has an obvious per-request cost, charge mode is enough. If the service has a metered cost that accumulates quickly — tokens, data stream updates, repeated analytics calls, or another high-frequency unit — channel mode is the better fit. - -Sponsored transactions are separate from MPP, but they can be used alongside it. MPP defines the payment challenge, receipt, and settlement model for paid access. Fee sponsorship lets another wallet or relayer cover transaction fees so the user does not have to hold XLM just to complete the interaction. - -For agent wallets, the simplest testnet path is still to use Stellar CLI keys while prototyping. For production-oriented work, the meeting pointed builders toward OpenZeppelin policy-based smart accounts, where a wallet can express rules such as requiring human approval above a certain transaction threshold. - -The meeting closed with two possible follow-up topics: the Yardstick protocol upgrade and secure wallet/key-management patterns for autonomous agents. There was also interest in a one-page version of the demo and in future coverage of Stellar Tools and Lobstr Cash. From 80bf4313735c13f9c619e8f1f891e79342f25e0a Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Mon, 11 May 2026 16:53:54 -0400 Subject: [PATCH 4/4] =?UTF-8?q?=F0=9F=93=9D=20Replace=20meeting=20video=20?= =?UTF-8?q?embed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Codex --- meeting-notes/2026-05-07.mdx | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/meeting-notes/2026-05-07.mdx b/meeting-notes/2026-05-07.mdx index 1a36753f2..a1d81d47f 100644 --- a/meeting-notes/2026-05-07.mdx +++ b/meeting-notes/2026-05-07.mdx @@ -4,13 +4,9 @@ authors: kaankacar tags: [developer] --- - +import YouTube from "@site/src/components/YouTube"; + + ## Machine Payments Protocol: A Deep Dive