feat: add machineUSD funding flow - #93
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 177215fec7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| action: fundAction({ | ||
| credits: args.includes("--credits"), | ||
| crypto: args.includes("--crypto"), | ||
| machineUsd: args.includes("--machine-usd"), |
There was a problem hiding this comment.
When invoked in the normal command-first form, such as tempo wallet fund --machine-usd --network testnet (or -n testnet), handleCompatCommand intercepts the command but runFundCompat never passes the network to runFundingFlow. The flow therefore defaults to mainnet, bypasses the intended mainnet-only rejection, and opens a real mainnet purchase flow despite the explicit testnet selection. Forward both network option forms here as the sessions compatibility path already does.
Useful? React with 👍 / 👎.
Reverts #93 until the machineUSD wallet and backend rollout is ready.
1 participant
Why
CLI wallets need a direct handoff into the wallet-native machineUSD onramp and a reliable way to detect when mainnet MACHUSD arrives. This depends on machine-usd#44 and wallet#678.
What
tempo wallet fund --machine-usd.