Open
Conversation
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d76b5-e92a-7588-87bc-4969a2f98a2d
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Co-Authored-By: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d76b5-e92a-7588-87bc-4969a2f98a2d
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d76b5-e92a-7588-87bc-4969a2f98a2d
Co-authored-by: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d76b5-e92a-7588-87bc-4969a2f98a2d
grandizzy
reviewed
Apr 10, 2026
src/pages/sdk/foundry/mpp.mdx
Outdated
| 2. **402 challenge** — The server responds with `402 Payment Required` and a `WWW-Authenticate: Payment` header describing the price. | ||
| 3. **Key discovery** — Foundry reads your signing key from `$TEMPO_HOME/wallet/keys.toml` (default `~/.tempo/wallet/keys.toml`) or the `TEMPO_PRIVATE_KEY` env var. | ||
| 4. **Channel open** — If no payment channel exists, Foundry opens one on-chain with a deposit (default: `100,000` base units). This is a one-time on-chain lockup — unused balance remains in the channel. | ||
| 5. **Voucher payment** — Foundry signs an off-chain voucher against the open channel and retries the request with an `Authorization: Payment` header. |
There was a problem hiding this comment.
worth mentioning that it automatically top up
grandizzy
reviewed
Apr 10, 2026
src/pages/sdk/foundry/mpp.mdx
Outdated
|
|
||
| 1. **First request** — Foundry sends a normal JSON-RPC request to the endpoint. | ||
| 2. **402 challenge** — The server responds with `402 Payment Required` and a `WWW-Authenticate: Payment` header describing the price. | ||
| 3. **Key discovery** — Foundry reads your signing key from `$TEMPO_HOME/wallet/keys.toml` (default `~/.tempo/wallet/keys.toml`) or the `TEMPO_PRIVATE_KEY` env var. |
There was a problem hiding this comment.
Let's add also the fact that if multiple payment challenges then will pick up the one for proper challenge and spending allowance
Co-Authored-By: 0xrusowsky <90208954+0xrusowsky@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d76b5-e92a-7588-87bc-4969a2f98a2d
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new page under Make Agentic Payments → Foundry integration documenting how tempo-foundry's built-in MPP transport works.
Changes
guide/machine-payments/foundry.mdxcovering setup, usage (cast/forge/anvil/chisel), configuration (deposit, key discovery, channel persistence), testnet, and troubleshootingReferences
Prompted by: rusowsky