Undetectable VPN for ordinary users and experts. VpnHood is a solution to bypass Advanced Firewalls and circumvent deep packet inspection. VpnHood has been created entirely from scratch in C#.
Get VpnHood!
It is available for Windows and Android. The iOS client still needs to be ready!
Hot Restart (User sessions' will not close on restart)
Built-In User Management
Built-in NAT with zero configuration
NetScan Protector
Windows (x64) 10, 11, or Windows Server
Linux
Developer Features
Open source (LGPL License)
Completely in .NET
Highly Customizable
Easily Embed into your .NET app
Extendable User Management via REST API
Component-based via Nuget packages
Open the solution with Visual Studio and build
IPv6 Support
VpnHood supports IPv6, but in Windows, you need to be already on the IPv6 network, so all your network traffic will be tunneled through VpnHood. In Windows, you will not have access to IPv6 sites if your network is not already configured to use IPv6. In Android, however, you will get an IPV6 address and access to all IPv6 sites regardless of your network configuration.
FAQ & Documents
Please check our Wiki to see the VpnHood documents.
Daemons intended for public use can be set up to require payment
in the form of hashes in exchange for RPC service. This enables
public daemons to receive payment for their work over a large
number of calls. This system behaves similarly to a pool, so
payment takes the form of valid blocks every so often, yielding
a large one off payment, rather than constant micropayments.
This system can also be used by third parties as a "paywall"
layer, where users of a service can pay for use by mining Monero
to the service provider's address. An example of this for web
site access is Primo, a Monero mining based website "paywall":
https://github.com/selene-kovri/primo
This has some advantages:
- incentive to run a node providing RPC services, thereby promoting the availability of third party nodes for those who can't run their own
- incentive to run your own node instead of using a third party's, thereby promoting decentralization
- decentralized: payment is done between a client and server, with no third party needed
- private: since the system is "pay as you go", you don't need to identify yourself to claim a long lived balance
- no payment occurs on the blockchain, so there is no extra transactional load
- one may mine with a beefy server, and use those credits from a phone, by reusing the client ID (at the cost of some privacy)
- no barrier to entry: anyone may run a RPC node, and your expected revenue depends on how much work you do
- Sybil resistant: if you run 1000 idle RPC nodes, you don't magically get more revenue
- no large credit balance maintained on servers, so they have no incentive to exit scam
- you can use any/many node(s), since there's little cost in switching servers
- market based prices: competition between servers to lower costs
- incentive for a distributed third party node system: if some public nodes are overused/slow, traffic can move to others
- increases network security
- helps counteract mining pools' share of the network hash rate
- zero incentive for a payer to "double spend" since a reorg does not give any money back to the miner
And some disadvantages:
- low power clients will have difficulty mining (but one can optionally mine in advance and/or with a faster machine)
- payment is "random", so a server might go a long time without a block before getting one
- a public node's overall expected payment may be small
Public nodes are expected to compete to find a suitable level for
cost of service.
The daemon can be set up this way to require payment for RPC services:
monerod --rpc-payment-address 4xxxxxx \
--rpc-payment-credits 250 --rpc-payment-difficulty 1000
These values are an example only.
The --rpc-payment-difficulty switch selects how hard each "share" should
be, similar to a mining pool. The higher the difficulty, the fewer
shares a client will find.
The --rpc-payment-credits switch selects how many credits are awarded
for each share a client finds.
Considering both options, clients will be awarded credits/difficulty
credits for every hash they calculate. For example, in the command line
above, 0.25 credits per hash. A client mining at 100 H/s will therefore
get an average of 25 credits per second.
For reference, in the current implementation, a credit is enough to
sync 20 blocks, so a 100 H/s client that's just starting to use Monero
and uses this daemon will be able to sync 500 blocks per second.
The wallet can be set to automatically mine if connected to a daemon
which requires payment for RPC usage. It will try to keep a balance
of 50000 credits, stopping mining when it's at this level, and starting
again as credits are spent. With the example above, a new client will
mine this much credits in about half an hour, and this target is enough
to sync 500000 blocks (currently about a third of the monero blockchain).
There are three new settings in the wallet:
- credits-target: this is the amount of credits a wallet will try to
reach before stopping mining. The default of 0 means 50000 credits.
- auto-mine-for-rpc-payment-threshold: this controls the minimum
credit rate which the wallet considers worth mining for. If the
daemon credits less than this ratio, the wallet will consider mining
to be not worth it. In the example above, the rate is 0.25
- persistent-rpc-client-id: if set, this allows the wallet to reuse
a client id across runs. This means a public node can tell a wallet
that's connecting is the same as one that connected previously, but
allows a wallet to keep their credit balance from one run to the
other. Since the wallet only mines to keep a small credit balance,
this is not normally worth doing. However, someone may want to mine
on a fast server, and use that credit balance on a low power device
such as a phone. If left unset, a new client ID is generated at
each wallet start, for privacy reasons.
To mine and use a credit balance on two different devices, you can
use the --rpc-client-secret-key switch. A wallet's client secret key
can be found using the new rpc_payments command in the wallet.
Note: anyone knowing your RPC client secret key is able to use your
credit balance.
The wallet has a few new commands too:
- start_mining_for_rpc: start mining to acquire more credits,
regardless of the auto mining settings
- stop_mining_for_rpc: stop mining to acquire more credits
- rpc_payments: display information about current credits with
the currently selected daemon
The node has an extra command:
- rpc_payments: display information about clients and their
balances
The node will forget about any balance for clients which have
been inactive for 6 months. Balances carry over on node restart.
It is becoming more known: adding more torrent trackers increase your torrent download speed. This is why, every year, I publish a fresh new list of open and free torrent trackers that you can use in your favourite torrent program. In broad terms, by adding more torrent trackers, your torrent downloads will connect to a wider network of seeds and peers – ultimately this will increase the downloading speeds of your torrents.
In this blogpost, I will share the torrent trackers list 2022 as well as a short tutorial on how to add the trackers into the torrent downloading program of your choice.
Reminder: What is a torrent tracker?
First, let’s see what Wikipedia has to say about what is a BitTorrent tracker:
A BitTorrent tracker is a special type of server that assists in the communication between peers using the BitTorrent protocol.
In peer-to-peer file sharing, a software client on an end-user PC requests a file, and portions of the requested file residing on peer machines are sent to the client, and then reassembled into a full copy of the requested file. The “tracker” server keeps track of where file copies reside on peer machines, which ones are available at time of the client request, and helps coordinate efficient transmission and reassembly of the copied file. Clients that have already begun downloading a file communicate with the tracker periodically to negotiate faster file transfer with new peers, and provide network performance statistics; however, after the initial peer-to-peer file download is started, peer-to-peer communication can continue without the connection to a tracker.
So basically when you add a torrent tracker URL to your torrent program, it will instruct your torrent program to connect to that BitTorrent tracker server. This tracker is basically the ‘referee’ and knows the rule of the torrent-game: it will keep an eye on the full downloading scene that is happening surrounding the concerned torrent.
In this blogpost I will only list open, public and free torrent trackers. This means that you don’t need to pay, register or connect to a specific network in order to make use of the tracker services. You simply import the list and the new seeds and peers should start to connect automatically.
The main advantages of trackers
First of all: a torrent tracker is not something optional in the BitTorrent world. Without trackers, you would not be able to start your downloads. It means that your torrent will be stuck at 0% because it cannot find any seeds or peers. If you add a torrent to your torrent program by downloading a .torrent file or clicking a magnet link, it will already contain a reference to 1 or a small list of trackers.
So by adding (more) trackers, your downloads will not get stuck at zero percent (or somewhere in the middle). Secondly, your overall downloads speed will increase, so that in the end your downloads will finish quickly.
As a third advantage I want to add that more seeds and peers will be added which are close to you geographically. If you live in Germany, the torrent trackers will likely also inform your torrent program there are other seeds and peers closely – in the same country or nearby. Your download program can perform a quick check on the latency of each seed/peer and prefer faster seeds and peers. Example: if you download an internal torrent file (such as Ubuntu Desktop), you will likely be connected to other users all over the world. Yet, your torrent program may prefer to download from other users in Germany or Europa rather than far away from you.
How to add a torrent tracker in my torrent program?
Adding new trackers (coming from the torrent tracker list below) to your torrent program is relatively easy. But, it depends on your preferred program how it works exactly. The principle of adding trackers is the same for all programs though, so if you follow below steps, you should be able to replicate these steps for your program.
The below procedure should work for the following popular BitTorrent programs:
uTorrent
qBittorrent
Vuze
Transmission
BitTorrent
Deluge
Tixati
BitComet
Web-based torrent
Here are the steps you should follow:
First, copy the below list of trackers to your clipboard. Note that the empty new lines are required and should remain.
Open your torrent program and select the ‘trackers’ option
Click on ‘add trackers’ (or similar option)
Paste the list of trackers and confirm by clicking ‘Ok’
Select the ‘Add a new tracker…’ in the ‘Trackers’ screen.
If you followed these simple steps, you should have succesfully added the trackers for your torrent. You should note that these steps should be repeated for every torrent file you are downloading. Now the torrent download should start to add more seeds and peers, this is because the new trackers will keep track of more connected users who are also downloading and uploading the concerned torrent file.
Torrent tracker list 2022
Use the torrent tracker list below: copy this and paste it into your downloading program.
:extract_focal()/https%3A%2F%2Fgithub.com%2Fvpnhood%2FVpnHood%2Fwiki%2Fimages%2Flogo-vpnhood.png)
:extract_focal()/https%3A%2F%2Fgithub.com%2Fvpnhood%2FVpnHood%2Fwiki%2Fimages%2Fdownload-google-play.png)
:extract_focal()/https%3A%2F%2Fgithub.com%2Fvpnhood%2FVpnHood%2Fwiki%2Fimages%2Fdownload-win.png)
:extract_focal()/https%3A%2F%2Fgithub.com%2Fvpnhood%2FVpnHood%2Fwiki%2Fimages%2Flogo-win.png)
:extract_focal()/https%3A%2F%2Fgithub.com%2Fvpnhood%2FVpnHood%2Fwiki%2Fimages%2Flogo-linux.png)
:extract_focal()/https%3A%2F%2Fthomas.vanhoutte.be%2Fminiblog%2Fwp-content%2Fuploads%2Fimage-21-1024x447.png)
