Live data from Hacker News

Monetization Gateway: Charge for any resource behind Cloudflare via x402

blog.cloudflare.com

211–220 of 273 posts

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#211
post #182

With payments the complexity is not only in accepting a payment, but largely in doing so legally. Someone makes a request to my company's paid service, I return 402 and get a stable coin back. Who do I invoice for this revenue? What value added tax do I apply to the invoice? If someone makes 10k paid requests within one month, do I have means of generating one invoice for them for all the usage, or is every request t…

I definitely wouldn't want to implicitly join an economic nexus by virtue of such a payment solicitation. The last thing I want is being subject to EU DSA and limitless other nonsensical legislation.

The US doesn't extradite to Europe for DSA violation

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#212
post #165
post #35

We need standards and protocols, not another megacorp inserting itself between people. Micropayments should be part of the HTTP protocol.

x402 is the standard.

Which RFC number?

I had a look at their website, it relies on every HTTP request creating a separate blockchain transaction, which is a volume of requests that blockchains can't possibly handle - even the layer-2s. It also makes the requests take a long time.

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#213
post #118

X402... I was not aware, I had this idea of making HTTP connection depend on a monero transaction, the monero transaction should take around 3 secs of the average computer/cellphone... once you have paid that you can access the resource. You wanna crawl the whole internet non stop, you pay non stop, 3 secs is probably the same as we pay in ads for those without adblockers and then content generators can start getting…

Monero target block interval is 2 minutes. You have to wait for 2-3 blocks because Monero does regularly have reorgs.

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#214
post #33

Earlier quoted context omitted.

I'm old-man-yelling-at-the-clouds here. Everyone just uses Cloudflare, which is not a bad thing by itself. But do they _have_ to? Is managing your own edge really that terrifying?

> Is managing your own edge really that terrifying? It's about convenience, not fear. Cloudflare is free for most companies until you need more advanced features.

What's more convenient about Cloudflare in front of your server than just your server? I think people use Cloudflare because of the fear of DDoS.

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#215
post #80
post #33

Earlier quoted context omitted.

I'm old-man-yelling-at-the-clouds here. Everyone just uses Cloudflare, which is not a bad thing by itself. But do they _have_ to? Is managing your own edge really that terrifying?

It would be economically impossible for me to run a small personal website without Cloudflare thanks to the sheer quantity of badly behaved automated traffic on the Internet in 2026.

What happened when you tried?

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#216

So, the snake oil salesman in me immediately wonders if this will become the new landscape for spam....It might go something like the following... 1. Establish domain names and relevant cloudflare account including the monetization gateway (associated rules, etc.). 2. Then host a ton of crap content across a wide swath of topics...not even decent quality...merely a step above old school style SEO keywords...just enou…

"host a ton of crap content across a wide swath of topics.." But how will anybody know it's there?

That part is describing Google SEO spam. I don't know how it works but it clearly does work if you've used Google lately.

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#217

I am surprised that Cloudflare went and made their own implementation of L402/x402? There are already a bunch of working implementations: * https://www.l402.org/ * https://docs.lightning.engineering/the-lightning-network/l40... There is even an index with a long list of services that already support this tech: * https://l402index.com/

Since the protocol is just returning a crypto address and a payment amount in JSON format and then waiting for a request with the transaction ID, why wouldn't they implement it themselves?

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#218

I’m curious about the decision to “aim for sub second transaction times”, rather than using something cryptography-based, such as a verifiable oblivious pseudorandom function. That is, - as a client I could obtain a bunch of credits/tokens from my payment processor - these tokens have the cryptographic property of being verifiable (ex: “that’s definitely a stripe-verified token worth $0.001”) - these tokens also have…

I heard GNU Taler is something like this

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#219
post #36

Can the agents use debit cards? Stablecoins doesn't make sense here and prefer not to use crypto at all.

Debit cards have to pay too many people. The acquiring bank, the receiving bank, the network, all take their fees. Stripe and their minimum $.30 per transactions leave no room for $0.01 API calls.

Crypto transfer fee is worse. Can be up to $30.00 on Ethereum for that $0.01 API call.

Re: Monetization Gateway: Charge for any resource behind Cloudflare via x402

#220

Earlier quoted context omitted.

It is You’re 10 years late x402 not required just segregated addresses acting as individual market participants paying for your service if you ever want your state’s currency (which is a big IF in the crypto world), then you use your segregated address to pump the price of a token that your clean and KYC’d addresses hold, sell into liquidity for a more liquid crypto, sell that crypto on an exchange. you look like a g…

"pump the price of a token" seems like the complex part that you're hand-waving. Either this token has a bunch of other traders (in which case, it's not trivial to simply "pump" its fair-market price by your own effort), or your alt wallets are themselves most of the liquidity (in which case, you're really just transacting with yourself, which is trivial to trace)

yes, there are always a bunch of traders on every launch so this is easy and has been streamlined for years with pump.fun + bundlers, and similar services on other networks

bots hop in everything, and the bundler is the creator who has lots of alts, market can bear this

in this case the bundler would be all processed tainted money, or the tainted money is another trader later

and your clean KYC'd money would be one of the traders that showed up

you bought at launch, and it pumped. hurray. reiterating that you have to sell into liquidity - we're talking about liquidity pools onchain here, no exchange companies - and then moving the proceeds to an exchange.

with the groups of addresses being unlinked this whole time, the only other thing to consider is connecting to an RPC server under different IP addresses, or connecting to your own node onprem. it doesn't matter if you assume, you have to prove for it to matter, and assuming incriminates everyone that actually picked the right token and had nothing to do with anything. there are plenty of people making 10,000%+ gains in random crypto tokens, amongst those taking losses, you're just another one.

yes, some people money launder successfully. you'll find out decades later while the attorney general exclusively parades around outdated and misapplied methods that failed

Post reply on HN