I did not get it how it could be used for a _static blog_.
>…the paywall fetches the content behind the scenes, and since our response is JSON rather than HTML it has nothing to render in place, so it navigates to an in-memory object URL created from the response. The protocol itself is pay per use, so every time you hit an API - you will be charged.
So it can't be used to 'unlock' a paid article forever? You can only read it once, and if you closed the tab, you need to pay again?
We are founding members of the x402 foundation and built the most popular x402 explorer, x402scan [0] Happy to answer any questions! [0] https://www.x402scan.com/
What are 'Featured Services' on this site?
The all time overall stats says volume is ~52m, but the table of featured services adds up to < 11m, with one 'x402 Facilitator - Dexter ' being like 95% of that...
Quite apart from whether the concept can succeed after having failed a number of well-funded and well-publicised times— I open https://shtein.me/api/joke in a normal-enough browser (Firefox Nightly with Enhanced Tracking Protection and uBlock Origin). After loading its 2.3MB response (no useful HTML, just a huge inlined JS blob, and served without transfer compression), it asks me to select a wallet. There are two ch…
>Nothing discernible happens. No errors or network activity in the dev tools.
I guess it expects any 'WEB3' browser extension to be installed. Anything that supports Ethereum should work: Metamask, Enkrypt, Rainbow, …
We are founding members of the x402 foundation and built the most popular x402 explorer, x402scan [0] Happy to answer any questions! [0] https://www.x402scan.com/
What are 'Featured Services' on this site? The all time overall stats says volume is ~52m, but the table of featured services adds up to < 11m, with one 'x402 Facilitator - Dexter ' being like 95% of that...
Featured services is our attempt at a slightly more curated list of services.
Anyone can register services and APIs. Some people treat x402scan like a leaderboard, and they try and game it in all sorts of ways. We try and keep the "featured" list to resources we know are not boosting their numbers. It's a bit of a cat and mouse game though, and is by no means perfect. There will be false negatives/positives.
Quite apart from whether the concept can succeed after having failed a number of well-funded and well-publicised times— I open https://shtein.me/api/joke in a normal-enough browser (Firefox Nightly with Enhanced Tracking Protection and uBlock Origin). After loading its 2.3MB response (no useful HTML, just a huge inlined JS blob, and served without transfer compression), it asks me to select a wallet. There are two ch…
>Nothing discernible happens. No errors or network activity in the dev tools. I guess it expects any 'WEB3' browser extension to be installed. Anything that supports Ethereum should work: Metamask, Enkrypt, Rainbow, …
I don’t know if “Injected” is the name of some service, or a description of what is to happen (in which case it’s lousy wording). Whatever it is, the failure mode is clearly atrocious. I hope that’s avoidable.
I did not get it how it could be used for a _static blog_. >…the paywall fetches the content behind the scenes, and since our response is JSON rather than HTML it has nothing to render in place, so it navigates to an in-memory object URL created from the response. The protocol itself is pay per use, so every time you hit an API - you will be charged. So it can't be used to 'unlock' a paid article forever? You can onl…
There is a description of an access token, so it looks like you'll have some time to access a page. Anyway, this is more for bots. If you want this page so much, just print it to pdf.
So do/can users get a preview of the content before being required to make payment? Or is the idea that users are likely already familiar with the site/content to which they will pay? Sorry I only skimmed the article.
The protocol itself only seems to define only the payment related negotiations. The author is free to implement some sort of preview themselves, though the full content should be on a separate page in order to use the browser's built in x401 client implementation.
Quite apart from whether the concept can succeed after having failed a number of well-funded and well-publicised times— I open https://shtein.me/api/joke in a normal-enough browser (Firefox Nightly with Enhanced Tracking Protection and uBlock Origin). After loading its 2.3MB response (no useful HTML, just a huge inlined JS blob, and served without transfer compression), it asks me to select a wallet. There are two ch…
This is all Firefox's implementation of the client. In the dropdown it shows wallets that it sees as available. I was able to test with coinbase wallet, for you it seems like coimbase alltogether is blocked, yes, but also, for example when I install Metamask extenaion - it becomes available as an option, so you can, in theory use whatever crypto wallet is available in your country. But yeah, as the top comment says - the legality of the whol thing is questinable.
> This literally can change how we use internet making advertisement economy internet runs on obsolete. Hmm, so I will pay to see websites that have ads. This may or may not be fine and solve some other problems (like paywalling AI agents), but lets not be naive. It won't replace ads, in most cases it will just be another stream.
Having options is always a good thing, but trying to make a test payment I myself saw how far away this thing is in terma of encountering a user with a funded wallet on correct network. So I actually agree, it won't replace ads foe a long time if ever.
I did not get it how it could be used for a _static blog_. >…the paywall fetches the content behind the scenes, and since our response is JSON rather than HTML it has nothing to render in place, so it navigates to an in-memory object URL created from the response. The protocol itself is pay per use, so every time you hit an API - you will be charged. So it can't be used to 'unlock' a paid article forever? You can onl…
Yeah, it doesn't unlock content forever, the protocol is made with assumption of payment per use. I haven't tried to present the same payment confirmation twice, but reading about it I assume it will fail. In this PoC the browser's ser opened content in memory as a separate tab, but it is a side effect, bot a feature. So you are right, it's not usable for tracking subscriptions in any way.