List of Hosting Providers That Accept Cryptocurrencies or Cash as Payment

General Tor and Anonymity Talk
46

Okay, this will be a very big and impactful post, so we will start with the custom drop-in solution (fully migrated from the maintained list on the Whonix Wiki for April 2026, but not from the beginning of this topic nor the historical archived list):

Relevant repositories:

There are currently four statuses:

  1. Verified, which means I have personally used the service, either before or now
  2. Approved, which means I have personally reviewed the entire website up until the checkout process and generated invoice
  3. Pending, an unreviewed entry, but also includes reviewed broken checkout processes (instead of removing the entry until the next month)
  4. Rejected, failing the Whonix Wiki criteria outright and is deferred any status update until the beginning of next year’s Firefox release

Every Firefox release, any entries with “verified” or “approved” status becomes automatically changed to “pending”, acting as the successor to the monthly Whonix Wiki cadence. This is enforced through a Forgejo Runner job from upstream-sync.yml in the FlawlessFox repository:

      - name: Reset hosting statuses
        if: steps.check.outputs.new_version == 'true'
        run: |
          python3 flawlessfox/scripts/reset-hosting-status.py \
            --repo-url "https://forgejo.franklyflawless.org/FranklyFlawless/Website.git" \
            --branch main \
            --push

That is the high-level summary, so are are my suggestions for you from this point onwards:

  1. Remove the “Anonymous Third-Party Hosting Providers” and “onion Webspace” headers in the respective Whonix Wiki page, including all contents within it
  2. Keep the historic deprecated list and this entire topic available/intact for me to fully and manually recrawl/rescrape every entry after the next Firefox release around May 19th, 2026, along with extracting every good idea to implement into the Hosting Directory on the next round.
  3. Decide a name for your (next) Firefox fork (currently based on Mozilla’s GitHub Firefox repository upstream, not from the Tor Project’s GitLab repository).

The current tenative name is “BaseSecure” (derived from Base Browser, which no longer exists, and Kicksecure), but I have also considered “BrowSEC” and various variations involving these two, from extending “SEC” to “Secure”, to truncating the names themselves (“BaseSEC” → “BaSEC”). Currently, “Secure” in “BaseSecure” is capitalized because Firefox forks historically practice this (LibreWolf, GNU IceCat, etcetera). If you want it super simple, then we reuse “SecBrowser” again (or SecureBrowser, etcetera). Once you have decided, then after letting me know, you will likely want to either create a new topic or add to an existing topic about this Firefox fork on the Kicksecure Forum, depending on your decision.

1 Like