Contact
Start with the exact project state.
x402-hosting support is handled through the public source repository. Before opening a report, run the free status command from the affected project directory and note the project state, CLI version, Node.js version, and the step that failed. Never include a private key, wallet recovery phrase, raw payment signature, environment file, or the contents of a pending payment handoff in a public issue.
- Email dries@whaamed.com
- Technical support and bug reports
- Source code and implementation history
- Agent and developer documentation
Payment and deployment problems
If a payment tool reports an error, do not immediately repeat the paid command. The payment may have settled even when the client lost the response. Run npx x402-hosting@latest finalize from the same directory first; it reconciles the pending operation without creating a second charge. For a service incident, include timestamps and public operation or deployment identifiers when available.
Security-sensitive reports should begin with a minimal public issue that asks the maintainers for a private coordination channel and contains no exploit details or secrets. Ownership transfers and deletions are irreversible actions; support cannot recover a lost owner wallet or reverse a completed transfer from the former owner.