Erik.eth

@programmer

183 Following

804 Followers

yuga.eth pfp

Even in the age of AI, we humans just cannot escape the urge to poast. That, and much more, in the latest episode of CDPod - Coinbase's technical deep dive with top onchain builders in crypto and beyond. Featuring Farcaster's very own @v !

1 reply

3 recasts

10 reactions

Erik.eth pfp

Full episode is now live where ever you get your podcasts! https://www.youtube.com/watch?v=RWdFGxB4iUE https://open.spotify.com/episode/6YHt0xoMg8CfdLh2ECHlkA

0 reply

2 recasts

4 reactions

Erik.eth pfp

Tomorrows episode with @v is a banger 👀👀

0 reply

3 recasts

11 reactions

Erik.eth pfp

- client can skip 1 if they already know what the payload is, but can't skip 3 (signatures are consumed when used, so much be created per payment) - 402 with the `error` field of the standard x402 response object describing the issue - imo may be prescriptive but potentially interesting for a future version. A server can always implement dynamic pricing themselves (reject request containing overpayment in their API), but the advantage of what you're saying would be allowing the customer to skip 1 aggressively in a more standard way. Feels like one to wait on demand for rather than premept.

0 reply

0 recast

1 reaction

Erik.eth pfp

I'll be speaking about x402 tomorrow at Eth Vancouver https://x.com/EthVancouver/status/1930410249418354881

2 replies

0 recast

21 reactions

Erik.eth pfp

I think that would require a way to make the x402 payment as part of the cast action, but if that was unlocked it'd totally work

0 reply

0 recast

2 reactions

Erik.eth pfp

What to do for each tuple (chain, scheme) is defined in the spec, and clients implement the spec That x402 isn't opinionated on, the rest is up to the HTTP server accepting x402. Any part of http or standards on top of http (OpenAPI, MCP, HTML) are valid in the response to the request making payment

0 reply

0 recast

0 reaction

Erik.eth pfp

I can help here! x402 standardizes a response that describes how to const payment, and a header the includes a payment. The client creates the X-Payment payload based on the response body. There are other details like delegating settlement to the facilitator, but broadly thats it for the http exchange.

1 reply

0 recast

2 reactions

Erik.eth pfp

Does no tax on tips apply to farcaster tips??

0 reply

1 recast

6 reactions

Steve pfp

@stevedylandev.eth

We got Pay2Pin via x402 before GTA 6 😭

3 replies

8 recasts

22 reactions

Erik.eth pfp

x402 is an extension of 402. Would love to enshrine it as a formal w3c standard but gotta start somewhere. Facilitators perform kyt, kyc isn’t required because the facilitator never holds funds. Facilitator is a documented standard, there’s an oss example one in our repo, anyone can deploy. Consumer validation is now, CDP has seen demand for a way for agents to seamlessly pay via our project agentkit and other places, but the time is now to see if this is the right approach.

1 reply

0 recast

2 reactions

Erik.eth pfp

Happy to chat in dms or at the eth Vancouver meetup. Agree on hype which is why x402 works live in production today

0 reply

0 recast

2 reactions

Erik.eth pfp

They’re unrelated. That standard focuses on merchant payments for e-commerce. X402 is lower level, arbitrary payments over http

1 reply

0 recast

4 reactions

Erik.eth pfp

Great question, I suspect because the Base team tests increases before they hit mainnet but @jessepollak @aneri would know best

1 reply

0 recast

2 reactions

yuga.eth pfp

Today, we're launching a new payments protocol that enables developers and AI agents to access and pay for APIs without API keys. x402 gets its name from HTTP Status Code 402 (Payment Required), and is built onchain. The new era of the internet will be powered by crypto. Read more at x402.org.

3 replies

17 recasts

95 reactions

rish pfp

We think agents will make independent decisions on what developer tooling to use when building software. As a result, all Neynar APIs now accept micro crypto payments. No need to - create a developer account - create API key - give API key to LLM agent If building on Farcaster or Base, any LLM agent with a crypto wallet can now ping our APIs, send USDC on @base and get back an API response. More in this blog post: https://neynar.com/blog/agents-frames-and-the-future-of-farcaster-neynar-s-vision-for-x402 s/o @quazia @programmer @nemild

12 replies

13 recasts

61 reactions

Erik.eth pfp

x402 lets you accept payments without API keys or credit cards, today. Open source, Open standard. https://github.com/coinbase/x402

2 replies

2 recasts

11 reactions

Erik.eth pfp

https://x402.org

0 reply

0 recast

1 reaction

Erik.eth pfp

Technically: - x402 lives as standardized response body + status code (402: Payment Required) - payments are signature based, encoded as a header (meaning no gas for the payer, if you've got usdc in your @farcaster wallet, you can buy stuff) - servers don't need RPC or a wallet online, they can delegate onchain actions

1 reply

0 recast

3 reactions

Erik.eth pfp

Over at @coinbasedev we just dropped @x402, an open standard for payments on the internet. Why does this matter? - Paying for things on the internet sucks - API keys are terrible UX for AI agents - fees are too high x402 makes paying 3 clicks, kills API keys via pay per request, and has 0 fees.

1 reply

3 recasts

10 reactions