This kinda seems like a fantastic way to implement micro payments. The site owner sets up a attestor that knows they’ve paid.
I hate Wei in general, but it really could open up control over bots and paid access.
replies(2):
I hate Wei in general, but it really could open up control over bots and paid access.
That’s kinda tricky to do well. Traffic for monitoring, you can do with a jwt, but like, enabling chunked transfer in python request lib is a problem you discover. An array of attestors could guarantee feature sets.
There's nothing about payments that requires testing client properties though. What you want is the ability to test if there's a corresponding payment, that has nothing really to do with the client's device. It just seems like irrelevant information, what are these "desired properties"?
You want a corresponding token with the request that matches a payment. And WEI seems like a strictly inferior way to get that instead of just... asking a payment provider for the token. What does my hardware/OS/browser have to do with a payment token?