Idempotency keys for contract write endpoints#937
Closed
Johnsource-hub wants to merge 8 commits into
Closed
Conversation
|
@Johnsource-hub Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
can you update fork and comit again |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#closes
#842
Description
This PR implements an Idempotency Layer in the backend API to satisfy the critical goal of preventing accidental duplicate on-chain writes (such as duplicate content submissions, voting, or double-minting rewards via Soroban smart contracts) caused by client network retries or page refreshes.
By introducing an Idempotency-Key header verification lifecycle, the API guarantees that a unique business operation is executed exactly once, safely caching and replaying successful responses on subsequent retries, and throwing standard errors during rapid concurrent race conditions.
Implementation Details
Added an IdempotencyKey tracking table to the PostgreSQL schema via Prisma.
Key Strategy: The key serves as a unique primary string index.
Status tracking: Set to STARTED when a transaction begins and updated to COMPLETED upon a successful API outcome.
Storage & Expiry Policy: Records have a strict 24-hour Time-to-Live (TTL) enforced via automated application level cleanup routines and check validations to minimize database bloat while safely covering client retry windows.