
Research
Node.js Fixes AsyncLocalStorage Crash Bug That Could Take Down Production Servers
Node.js patched a crash bug where AsyncLocalStorage could cause stack overflows to bypass error handlers and terminate production servers.
@space-meridian/x402-next
Advanced tools
Next.js middleware integration for the x402 Payment Protocol. This package allows you to easily add paywall functionality to your Next.js applications using the x402 protocol.
pnpm install x402-next
Create a middleware file in your Next.js project (e.g., middleware.ts):
import { paymentMiddleware, Network } from 'x402-next';
export const middleware = paymentMiddleware(
"0xYourAddress",
{
'/protected': {
price: '$0.01',
network: "base-sepolia",
config: {
description: 'Access to protected content'
}
},
}
);
// Configure which paths the middleware should run on
export const config = {
matcher: ['/protected/:path*'],
runtime: "nodejs",
};
The paymentMiddleware function accepts three parameters:
payTo: Your receiving address (0x${string})routes: Route configurations for protected endpointsfacilitator: (Optional) Configuration for the x402 facilitator servicepaywall: (Optional) Configuration for the built-in paywallSee the Middleware Options section below for detailed configuration options.
The middleware supports various configuration options:
type RoutesConfig = Record<string, Price | RouteConfig>;
interface RouteConfig {
price: Price; // Price in USD or token amount
network: Network; // "base" or "base-sepolia"
config?: PaymentMiddlewareConfig;
}
interface PaymentMiddlewareConfig {
description?: string; // Description of the payment
mimeType?: string; // MIME type of the resource
maxTimeoutSeconds?: number; // Maximum time for payment (default: 60)
outputSchema?: Record<string, any>; // JSON schema for the response
customPaywallHtml?: string; // Custom HTML for the paywall
resource?: string; // Resource URL (defaults to request URL)
}
type FacilitatorConfig = {
url: string; // URL of the x402 facilitator service
createAuthHeaders?: CreateHeaders; // Optional function to create authentication headers
};
For more on paywall configuration options, refer to the paywall README.
type PaywallConfig = {
cdpClientKey?: string; // Your CDP Client API Key
appName?: string; // Name displayed in the paywall wallet selection modal
appLogo?: string; // Logo for the paywall wallet selection modal
sessionTokenEndpoint?: string; // API endpoint for Coinbase Onramp session authentication
};
To use the official Coinbase facilitator package (@coinbase/x402) in your Next.js project:
pnpm install @coinbase/x402
// middleware.ts
import { paymentMiddleware } from "x402-next";
import { facilitator } from "@coinbase/x402";
export const middleware = paymentMiddleware(
"0xYourAddress",
{
"/protected": {
price: "$0.01",
network: "base",
// other config options
},
},
facilitator // Use the Coinbase facilitator
);
# .env
CDP_API_KEY_ID=your-cdp-api-key-id
CDP_API_KEY_SECRET=your-cdp-api-key-secret
Note: Onramp integration is completely optional. Your x402 paywall will work perfectly without it. This feature is for users who want to provide an easy way for their customers to fund their wallets directly from the paywall.
When configured, a "Get more USDC" button will appear in your paywall, allowing users to purchase USDC directly through Coinbase Onramp.
Add sessionTokenEndpoint to your middleware configuration. This tells the paywall where to find your session token API:
export const middleware = paymentMiddleware(
payTo,
routes,
facilitator,
{
sessionTokenEndpoint: "/api/x402/session-token", // Enable onramp functionality
cdpClientKey: "your-cdp-client-key",
appName: "My App",
}
);
Important: The sessionTokenEndpoint can be any path you choose - just make sure it matches where you create your API route in the next step. Without this configuration, the "Get more USDC" button will be hidden.
Create an API route that matches the path you configured above:
// app/api/x402/session-token/route.ts
export { POST } from "x402-next";
That's it! The x402-next package provides the complete session token implementation.
Add your CDP API keys to your environment:
# .env
CDP_API_KEY_ID=your_secret_api_key_id_here
CDP_API_KEY_SECRET=your_secret_api_key_secret_here
Once set up, your x402 paywall will automatically show a "Get more USDC" button when users need to fund their wallets.
"Missing CDP API credentials"
CDP_API_KEY_ID and CDP_API_KEY_SECRET are set"Failed to generate session token"
API route not found
sessionTokenEndpoint configurationexport { POST } from "x402-next";sessionTokenEndpoint: "/api/custom/onramp", create app/api/custom/onramp/route.tsFAQs
x402 Payment Protocol
We found that @space-meridian/x402-next demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
Node.js patched a crash bug where AsyncLocalStorage could cause stack overflows to bypass error handlers and terminate production servers.

Research
/Security News
A malicious Chrome extension steals newly created MEXC API keys, exfiltrates them to Telegram, and enables full account takeover with trading and withdrawal rights.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.