Skip to content
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.

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

Per-origin and cross-origin implications on double spend state #104

Closed
chris-wood opened this issue Mar 11, 2022 · 1 comment · Fixed by #130
Closed

Per-origin and cross-origin implications on double spend state #104

chris-wood opened this issue Mar 11, 2022 · 1 comment · Fixed by #130

Comments

@chris-wood
Copy link
Collaborator

Origins currently choose whether their challenges are per-origin or cross-origin. For cross-origin, double-spend prevention is only as good as the coordination between origins and the Issuer. Per-origin allows double-spend prevention to be isolated to a single origin; also prevents the cache of tokens being take up by some other origin.

@chris-wood
Copy link
Collaborator Author

Write this as "any origins that share a redemption context must also share double spend state for that context."

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

Successfully merging a pull request may close this issue.

1 participant