phdargen

Hi @wuyahuang, thanks for your contribution! I would suggest to also rename `EvmMaxAtomicUnits` to sth like `MaxUint256Digits` to avoid confusion

Hi @souhailaS, thanks a lot for looking into this! We observed similar issues for the `express` and `flask` middlewares (https://github.com/coinbase/x402/pull/659, https://github.com/coinbase/x402/pull/693), so its possible that `fastapi` is impacted as well....

I also tested your new tests and they pass with the middleware unchanged. In any case, your added unit tests fill an important gap in coverage for the payment settlement...

Hi @juliangruber, thanks for your contribution! I tested your changes and there are still some build issues. I suggest to consolidate the nested `server/` and `client/` package.json files into the...

For the package.json in root you can use: ``` { "name": "browser-wallet-x402-example", "version": "1.0.0", "description": "Example of x402 payments with browser wallet integration", "private": true, "type": "module", "scripts": { "dev":...

This is tested and good to go @CarsonRoscoe

Hi @edevil, payTo info is included in the x-payment-response header that you can decode with the `decodeXPaymentResponse` function if payment successful. Otherwise you can find this info in the accepts...

Thanks a lot for the suggestion @giuseppecrj! The signature handling was improved in https://github.com/coinbase/x402/pull/713 and should cover this

Thanks for your contribution @yssf-io, looks good to me! @CarsonRoscoe I succesfully tested this with the following modification to the example/next api/weather route: ``` export const GET = withX402( handler,...