Anubis has no single permanent address and no clearnet site. It publishes several onion addresses, all resolving to the same market. Copy a current one from this page, open it in Tor Browser, and verify it against the login.
Yes. Anubis is one of the very few Tor markets that accepts Ethereum, alongside Bitcoin, Litecoin and Monero. Note that Ethereum is not private, so if privacy is the goal use Monero instead.
Monero by default for privacy. Bitcoin, Litecoin or Ethereum when they fit your situation, but only Monero keeps the payment off a public ledger. The deposit address is fresh per order.
Copy the address from this page, then hold it against the login and confirm it matches your bar. Never type a fifty-six character onion from memory. Solve the tile captcha in the visible field only.
No. A genuine login never asks for the recovery phrase. A page that does is a phishing clone. Close the tab and reach the market through a verified address.
Build a fresh Tor circuit and retry, or switch to another address here. There is usually more than one onion live at once, and all resolve to the same market.
Monero if the payment should leave no permanent public record, which covers most reasons for being on a hidden service. Bitcoin, Litecoin and Ethereum all write the amount and both addresses to a ledger anybody can read indefinitely.
It gives you an Ethereum deposit address and watches the chain. That is different from markets that pipe ETH through a conversion bridge, where you pay the spread and the swap itself becomes a record.
Because it uses accounts rather than discrete outputs, so one address carries every transaction it has ever made. Reuse is the default rather than a mistake, which links your activity harder than Bitcoin does despite confirming faster.
The first page of a session builds a path across roughly six relays with no caching anywhere, so tens of seconds is the design rather than a fault. Pages after it ride the same path and land in seconds.
Your path has usable latency and poor capacity, which are different properties. A queue drains with patience, a capacity limit does not, so a fresh circuit is the fix and waiting is not.
Either storage is blocked for that address or you have two of the addresses open together. The browser files each onion separately, so two tabs will overwrite one another.
Both are true. The fee came out of the figure you entered rather than being added to it, so the amount that landed is short by exactly the fee. Raise it with the order reference instead of sending again.
No, and treat it as a rule rather than a case by case call. You have no way to tell an honest cash flow request from a fraudulent one, and the click cannot be undone.
Open the dispute. The release timer runs regardless of whether you are being patient, and opening a case is what stops the clock. Waiting quietly past that point only removes your own leverage.
It moves the knowledge of your Tor use from your network operator to a company holding your billing details. That is a trade rather than an upgrade, and the connection itself is no more private than before.