Crosshatch

Inject Crosshatch's x402 `HttpClient` into any Effect. On 402s, it decodes payment required, generates the payment payload, and retries exactly once. @CrosshatchDev

Working with stablecoins should not require merchants to reason about token contract addresses or decimals. Crosshatch abstracts over the noise. One asset identifier. One numeric amount. Chain- and token-specific precision handled automatically. @CrosshatchDev

RT @harrysolovay: Crosshatch now ships with a local mock facilitator: • x402-compliant responses • optional log export for local OTEL setu…

The simplicity of chain-agnostic types when expressed with Effect schemas: Validation, static inference of template literal types, nominal branding... All from one tiny definition. @CrosshatchDev

A powerful feature of x402 v2: There is an extension system, which lets merchants treat clients as if they are RPC endpoints… The merchant can ask for additional computations/data alongside payment. @CrosshatchDev ensures this extension system is strongly-typed, end-to-end.

Effect layers are an ideal way to model chain-agnostic payment capability. ERC-3009 payment payload creation requires an EIP-155 signer. Our EIP-155 signer layer requires a mnemonic. The composability is striking. @CrosshatchDev

High-frequency x402 micropayments over Effect RPC with @CrosshatchDev

This is cool. Swap in a layer to enable x402 payments on your api.

An Effect-ified x402 merchant endpoint. No accounts or API keys. Earns in USD-denominated stablecoins. Settles payments instantly. Built for agentic micropayments. @CrosshatchDev

Effect AND x402!! The ultimate nerdsnipe

Win gar dium levi ohhh sa