Options accepted by the MPP token mint: everything X402TokenOptions
takes except tokenVersion.
MPP and x402 stopped sharing a token version ladder (nvm-monorepo#3266). MPP
signs one struct and names no version for it, because its single-use unit is
the challenge, not the token — one MPP access token is presented across
many challenges by design, so an x402 v3 per-token nonce would reject every
buyer's second challenge. The backend refuses ANY tokenVersion on an MPP
mint with BCK.MPP.0007, 2 included, so the field is omitted from the type
rather than accepted and ignored.
Options accepted by the MPP token mint: everything X402TokenOptions takes except
tokenVersion.MPP and x402 stopped sharing a token version ladder (nvm-monorepo#3266). MPP signs one struct and names no version for it, because its single-use unit is the challenge, not the token — one MPP access token is presented across many challenges by design, so an x402 v3 per-token nonce would reject every buyer's second challenge. The backend refuses ANY
tokenVersionon an MPP mint withBCK.MPP.0007,2included, so the field is omitted from the type rather than accepted and ignored.