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 the cryptographic property of being anonymous. (ex: neither stripe, nor the payment recipient know that I am Bob)
With this sort of cryptography based approach, cloudflare could verify my payment token without any cryptocurrency proof-of-work kerfuffle?
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 the cryptographic property of being anonymous. (ex: neither stripe, nor the payment recipient know that I am Bob)
With this sort of cryptography based approach, cloudflare could verify my payment token without any cryptocurrency proof-of-work kerfuffle?