Someone really doesn't want us up : Dread | Torhoo darknet markets

We are receiving a DDOS attack which will cause site slowdown and introduction point instability. I'm rolling out new fronts as the load grows and hopefully in the coming hours we will get more stable. If you are a premium user in the https://torhoo.cc/go.php?u=TDJRdmJHOTFibWRs# I will be posting a few temporary URL you can visit dread with at full speed and backup front urls in the case the asshole is also a premium member.

I've refunded the promoted post for the next couple days and will be crediting ads with extra time because of this downtime. Gives me a great opportunity to tweak endgame further. I'll update this post as things change. The i2p address is also getting attacked but that will be much easier (and way faster) to reach as more new and improved endgame fronts are rolled out with i2p support out of the box.

Edit: There is a lot of introduction point rotation. If you get to a page where it's timed out or there is no introduction points please grab a new identity to get the updated descriptors. If you use whonix this can be also done by reloading tor while keeping the cookies on the workstation browser.

i2p is up and stable.

Money was burnt. But anything to fuck the DDOSERs mom. We don't give a single fuck what it takes. Dread stays up.

Edit (14th): More adjustments and cost savings!

We could have been just straight up and stable but watching money burn in the front of my eyes hurt too much. So I focused today on optimizing the circuit handshakes process (side stepping the single thread pool and spreading the requests over multiple independent tor process with basically the same memory state to prevent the SINGLE thread pool from blocking everything [TorProject why is there only... one... single... fucking... thread... pool for all this onion handshake shit? Modern cpus have cores for days. DAYS! fuck your cpuworker.c library. Spaghettied all over the place. GIVE ME TRUE THREADING. EAT THE COMPUTE. Just because people can container this shit to sidestep your asshole design doesn't mean this is okay. OKAY?])

Tor values have been tweaked. I did a solid for the Tor network too by statistically spreading the load over basically all the guards. Otherwise there would have been a lot more guard nodes dying all over the place. POW is coming and this attack will be just a bad time in the past. But right now we be optimizing.

Edit (16th): The Tor network is starting to have ripple effects:

https://metrics.torproject.org/torperf.html?start=2022-09-12&end=2022-09-16&server=public&filesize=1mb

While generally this won't result in failures of the circuits at this point. The extra circuit building load has shown to be extremely taxing on the network hurting the overall throughput. There is good news though. After a lot of testing I have a onionbalancing design which should be effective at equally spreading introduction the load over many fronts. With the limits of introduction points on a single V3 descriptor being 20 it's not enough to get uptime. Pushing distinct descriptors on the network is the only way to get these servers up under an attack like this. The current design of distinct descriptors leave a lot wanting because the load isn't as equally spread out as it needs to be. Specifically to introduction points that are controlled by me so no foolishness can happen (and descriptor rejections can be minimized/eliminated as much as possible). After I'm done with it there will be effectively minimal descriptor rotation even under excessive load.

This will be my crown achievement. Protocol layer flaw avoidance by overtaking the entire onion introduction process.

Edit (18th): Get fucked DDOSER. My middle finger is directed at you, while my dick is directed inside your mother.

It just got 10X times harder to take down an existing connection to Dread. You will probably still get timeout issues (more so now) accessing Dread but grab a new identity and you will hopefully get to the captcha. It will still be slower than I would like soon enough I'll tweak this introduction process around the ring we will be basically impossible to take down (unless the Tor network goes down). At least that is the hope.

I would also like to give a big shout out to the amount of support we have got during this downtime. People hate us going down as much as we hate it happening. Makes it all worth it when we get it all done. We will be working multiple days to stabilize this process to keep uptime high and improve reach-ability.

It's interesting to see the change on the Tor network when the attack on Dread started: https://torhoo.cc/go.php?u=YUhSMGNITTZMeTl0WlhSeWFXTnpMblJ2Y25CeWIycGxZM1F1YjNKbkwzUnZjbkJsY21ZdFptRnBiSFZ5WlhNdWFIUnRiRDl6ZEdGeWREMHlNREl5TFRBNUxUQXhKbUZ0Y0R0bGJtUTlNakF5TWkwd09TMHhPQT09# (metrics lag behind about two days). It won't get much better until the attack stops or POW happens. We need about 800 more GUARD nodes on the Tor network so if just a portion of the people in the community can just open up one guard node we will have more than plenty. You can see instructions to do so ⚠️here⚠️. Make sure not to open up too many guard nodes at the same time with the same IP subnet or host (they will be flagged as bad nodes and won't be added!). If you want Dread online that is the single best thing you can do for us. These circuit failures are fucking up so much in the background.

It's a battle and the Tor network is the limit.

Edit (23rd): Okay we are stable. DDOSER's mom has been really satisfied. The site will still be slow at this times but I have been adjusting things to improve performance over the past couple days. Nobody ideally shouldn't be kicked off of any connection anymore (assuming you have a stable internet connection/your guard nodes don't get fucked). Recon is back up now too.

Edit (26th): Onionbalance's edits put too much load on the Tor processes it was running on and crashed the entire layer. Fixed it up and the main onion should be back online. That's a fuck up on my end.