New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Standardize 402 responses #1

Open

whoabuddy opened this issue May 2, 2024 · 0 comments

Contributor

whoabuddy commented May 2, 2024

With this demo we show that:

if a user paid, they get their content with a 200 response
if a user did not pay, the get a 402 response with info to pay the contract

For that second scenario we should draft a basic standard, maybe even evolve it into a SIP.

Some early thoughts:

if we return contract name + function name + function args, can easily construct a call to the smart contract
Clarity contract source is available on-chain, so easily accessible to compare against
Clarity provides a contract ABI that might be useful (draw similarities to tools like Clarigen)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment