Agreed - I'd like to think both this, and the Lavabit being coerced to hand over private SSL keys news elsewhere today - indicates that TOR and SSL are still "as secure as needed" against even targeted FBI attacks.

Unfortunately that all now needs to be viewed with the suspicion of "parallel reconstruction" - I'm somewhat less convinced that if the NSA targeted someone specific that SSL and TOR would resist their efforts (and that for something like Silk Road, that the NSA wouldn't happily break and read everything DPR did over his SSL secured TOR connections, and "share" just the right tidbits with the FBI for them to go and create a plausible explanation involving google searches and old forum posts).

Welcome to the post Snowden era - where we know that our governments not only don't have our best interests in mind, but have sophisticated programs in place to lie to us about how they arrive at the evidence they present (in those annoying occasions where they have to use courts who aren't just rubber-stamping everything they're told too).

(Edit: on reflection, it's kinda sad that this might well have been good detective work by diligent, talented, and persistent FBI investigators doing exactly what he taxpayer employs them to do - but that effort is now permanently under the dark cloud of suspicion of unconstitutional dragnet surveillance and morally corrupt processes like "parallel reconstruction".)

The question is - what was the service provided by Silk Road at the end of the day, and what can be decentralized?

The trust and review system, the search engine and the communication platform can all run independently and don't need to happen on the same platform.

The web interface can be provided by an open-source turn-key package, so the next DPRs only need to figure out the hosting.

The escrow system was probably the most critical service that SR provided. Unfortunately that seems to require a centralized model.