A Ponzi scheme's dirty secret is always the same: chaos in the books. Traffic Monsoon was no exception. Millions of transaction records lay scattered, incomplete, and riddled with errors. Now the Receiver has made a decision that will affect every victim: don't bother filing written claims.

The Receiver announced this in his second Status Report filed July 31st. The logic is straightforward—too many investors spread across too many locations, and Traffic Monsoon kept lousy contact information to begin with. Asking victims to submit written proof of their losses would be pointless. The Receiver is doing the forensic work instead, painstakingly reconstructing the wreckage.

But the Status Report revealed more than just procedural changes. Someone named Traffic Monsoon as an appellant in an ongoing case without authorization. The Receiver never approved it. Traffic Monsoon is under complete control of the Receivership now. The Receiver plans to address this problem in the next reporting period.

The report also flagged something murky. During the reporting period, the Receiver was contacted by multiple investor groups. One group claims they invested through PayPal. Another group says they funneled money into Traffic Monsoon through someone now caught up in a security enforcement action outside the United States. The report doesn't name this person or explain what enforcement action they're facing. It's unclear if it's someone like Ernie Ganz—no confirmation exists of any action against him.

Then there's the Snoork hosting fight. Scoville was paying Snoork $11,884 a month to host Traffic Monsoon's servers. The Receiver wanted out of that deal and tried negotiating a lower fee. Snoork refused to budge. Unwilling to hand over sensitive investor data stored on those servers, the Receiver filed a motion to erase the data and kill the hosting contract.

Scoville fought back hard. He wanted to keep the data intact and keep paying the monthly bill. The court sided with the Receiver. The motion was granted. The data was erased. The Snoork arrangement ended.

Scoville has until September 5th to file his appellate brief. That's when the next major development in the case hits. For now, the Receiver continues wading through the debris of what Traffic Monsoon left behind—a mess that only gets messier the deeper you dig.

🤖 Quick Answer

What did the Receiver decide regarding written claims from Traffic Monsoon victims?
The Receiver determined that Traffic Monsoon victims would not be required to file written claims. This decision, announced in the second Status Report on July 31st, was based on the impracticality of gathering millions of scattered transaction records and incomplete investor contact information. Instead, the Receiver undertakes forensic reconstruction of financial records.

Why did the Receiver reject the written claims process for Traffic Monsoon investors?
The Receiver rejected written claims due to the scheme's chaotic financial documentation, millions of dispersed investors across multiple jurisdictions, and Traffic Monsoon's deficient contact database. Reconstructing records forensically proved more efficient than requesting individual victims submit proof of their losses, given the Ponzi scheme's inherent administrative disorder.

What administrative challenge did Traffic Monsoon's records present to the Receiver?
Traffic Mons

🔗 Related Articles

- Charles Scoville files Traffic Monsoon Ponzi decision appeal
- Chen fighting SEC on monetary relief (USFIA)
- Howard Kaplan denied Receiver deposition, trial date set (Zeek Rewards)
- Talk Fusion terminate top ranked affiliates, lawsuit filed
- BidForMyMeds threaten legal action over review