Sourcery exit & escrow recovery instructions

https://www.reddit.com/r/SourceryMarket/comments/7colvs/thats_a_wrap_cut_print_cry_to_sleep/

That's too bad. I felt comfortable using sourcery w/ their multisig enforcement after tr. Thanks for your work /u/Merlin_Sourcery.


Comments


[3 Points] None:

Big Predictable if true


[2 Points] MandyThatGirl:

Chinese Hackers.


[1 Points] None:

A damn shame really.


[1 Points] TheLastCig:

The main post was edited / removed, what did /u/merlin_sourcery say?


[1 Points] DNM_FuckFace:

Read the announcement on Sourcery


[1 Points] StuxianNightmare:

In one of the posts above Merlin mentioned hosting running out soon

Ddos’ing if I understand it correctly not only affects the (in this case) .onion in question, but it will also affect the other services being hosted in the warehouse/business/server racks/etc

if Sourcery is/was being hosted through third party .onion hosting services, and Sourcery is getting ddos’d, that should take up network resources for other services hosted in the same server racks etc

The service provider would be understandably upset: their other clients might cancel service because of slow or nonexistent responses to their services due to the ddos. Thus even though Sourcery wants to continue, they might have no choice, nowhere to host. And given that the ddosing does not seem like it will stop, what business would want to keep one problematic client at the expense of others?

Also if the service is being hosted on a personal network such as at a home, would an ISP be able to see irregular amounts of Tor traffic going to a specific IP? The ISP would also have a reason to investigate why, the ddos would chew up bandwidth for nearby customers

If im wrong correct me im geniunely curious