Reliability & concurrency bugs
“My connection dropped, I hit retry, and now there are two of it.”
A write endpoint advertises an idempotency key and accepts it without error, but never stores or checks it. Clients that retry on timeout — exactly the clients the key exists for — silently duplicate the write.
Idempotency key accepted but ignoredblack beltRetry-safety and exactly-once semantics on write paths
Choose your app
The same mistake, planted in different products. Pick the domain you want to hunt it in.
TapTrust Federal
TapTrust Federal Credit Union · Banking · Online + teller
online.taptrustfederal.test
1 planted defecthunt here →
QualityMart
QualityMart Inc. · Retail · Big-box e-commerce
shop.qualitymart.test
1 planted defecthunt here →
QualityChart
St. Quality Health · Healthcare · EHR
Not seeded here yet — an open seat for a contributor to plant this defect in QualityChart.