Jumping in with some statistical perspective on sample size and testing frequency. With 47 tests over ~18 months, we've established a baseline failure rate of ~19%. But this is biased — people are more likely to test a product they're already suspicious about. The true failure rate for randomly selected products is probably lower, maybe 10-15%. How often should we test? For high-volume vendors: every 2-3 months or whenever a batch number changes. This catches: - Manufacturing drift (gradual quality decline) - Supplier changes (different API source) - Intentional reformulation For low-volume or new vendors: immediately, before anyone commits to multiple purchases. Statistical power: With ~20 tests per year (our realistic budget), we can maintain coverage of 5-6 active vendors with testing every 3-4 months. That covers the most popular sources and leaves room for a few wildcard tests. Budget math at $25/person/round, 4 rounds/year: - 20 contributors × $25 × 4 rounds = $2,000/year - Basic testing: $2,000 ÷ $250/test = 8 tests/year - With dual-lab: $2,000 ÷ $500/test = 4 tests/year - Realistic mix: 6 basic + 1 dual-lab = $2,000 That's 7 tests per year. Enough to cover the top 4-5 vendors with annual retesting plus 2-3 new vendor evaluations. Tight but workable.

I support this initiative but want to raise an ethical consideration: what's our obligation if testing reveals a dangerous product? Scenario: we test a vendor's product and find it contaminated with endotoxins above safe levels. Do we: A) Post the results on the forum only? B) Notify the vendor and give them a chance to respond? C) Report to the FDA's MedWatch system? D) All of the above? I'd argue (D). Forum posting protects our community, but FDA reporting protects everyone. The MedWatch system accepts reports from consumers, and contaminated injectable products are exactly the kind of thing they need to know about. Also — if a product fails identity testing (wrong compound), that's potentially criminal fraud and should be reported to the FDA's Office of Criminal Investigations. I'm not being dramatic — injecting an unknown substance because it was mislabeled is a serious safety issue. Can we build a reporting protocol into the initiative? When results are negative, we have a responsibility that goes beyond forum posts.

Emma raises an important point. Here's my proposed reporting protocol: If a product PASSES all specifications: - Results posted on forum - Vendor added/maintained on verified directory - No further action needed If a product fails purity or content (but identity confirmed): - Results posted on forum with clear warning - Vendor notified via email with COA attached — given 14 days to respond - If vendor disputes results, we offer to fund a retest at a different lab - Vendor status changed to "quality concern" on directory - No regulatory report (quality issues in non-FDA-regulated products are a grey area) If a product fails identity (wrong compound) or sterility: - Results posted on forum with URGENT warning - Vendor immediately removed from all directories - FDA MedWatch report filed (I'll handle this) - If the vendor is a licensed pharmacy, report to their state board of pharmacy - All purchasers from recent batches notified directly if possible If endotoxin levels are above safe thresholds: - Same as identity failure — this is a patient safety emergency - Immediate public warning + regulatory reporting I think this graduated response is appropriate. Minor quality issues get transparency and vendor engagement. Safety issues get the full response including regulatory reporting. Alright — let's finalize the first round. Based on votes so far, Round 1 will test ResearchChem Outlet (new batch) and PeptideSciencesRx. DM me to contribute. Target kickoff: first week of April.

Count me in for $25. This initiative is exactly what separates CompoundTalk from the random Telegram groups and Reddit threads where it's all anecdotes and no data. One suggestion for the long game: can we build a public database of all community-funded test results? Something searchable by vendor, batch number, and date? Even a simple spreadsheet would be useful, but a proper database with charts showing purity trends over time would be incredible. Imagine being able to pull up a vendor's page and see: 8 independent tests over 2 years, average purity 97.8%, all identity confirmations passed, no sterility failures. That's real, actionable data that helps everyone make informed decisions. Looking forward to Round 1. Let's do this.