The internet in itself is decentralized. The backbone of the internet is not located in one country, but multiple countries. And pulling the plug on the internet a) doesn't work and b) would be absolutely catastrophic to other stuff that the governments do care about. The internet cannot be shutdown, and with anonymizers like Tor, censorship and blocking can be easily circumvented.

Furthermore, we can also develop a bitcoin network through radio and not rely on current internet infrastructure. Instead we could create a global peer-to-peer radio network solely for bitcoin. There are people who are trying to create such a network

According to this, the odds of you being struck by lightning in the U.S. each year is

If the entire Bitcoin network devoted all of its hashing power to guessing your private key (assuming 1 million trillion checks per second), then the odds each year of someone generating your private key are

In other words, you are 32872500000000000000 times more likely to be struck by lighting.

Even if someone were able to generate 2¹⁰⁹ addresses per year, you are still about 2 billion times more likely to be struck by lightning in a year.

The cost of doing anything to minimize your risk (including even discussing it) is greater than the risk of doing nothing.

You can google "running a full node" for instructions.

You can google "limit bandwidth of bitcoin core" to learn how to limit the bandwidth.

I was looking at this today, and I have a question.  Instead of limiting the bandwidth what happens if I just use the -maxconnections switch?  Wouldn't that limit the number of connections to my full node and as a side effect reduce the bandwidth used?  Installing yet another program to limit the bandwidth seems a bit of a pain - but that is the way to do it on Windows according to the articles I read.

I notice about 20 GB per day outgoing when I run my full node "out of the box".

That is the probability of the same address being generated by two different wallets, assuming that all generated addresses are all used. It is not the same as simply generating an address that is currently in use.

The maximum theoretical probability can be computed. Suppose bitcoins are maximally distributed such that each address holding bitcoins contains only 1 satoshi. There would be 2.1 quadrillion addresses in use (or about 2⁵¹).

The maximum odds of a collision occurring while distributing the 2.1 quadrillion satoshis is approximately (2⁵¹)² / (2 * 2¹⁶⁰), or


That is an incredibly small number.

Once the satoshis are distributed, the odds of generating a single address that is already in use is 2⁵¹ / 2¹⁶⁰, or

These are the highest possible odds of a collision.

Suppose you are trying to steal satoshis by brute force and you hope to crack one address per year. What kind of hash rate do you need? Well, you need to check 2¹⁰⁹ private keys per year (31556926 seconds), or

Note that 2.1x10²⁵ is about 24 million times the total Bitcoin hash rate (though the two rates are not directly comparable)

Just to be picky: "...about .05 BTC daily" would be more accurate.

kali linux ?
google it

What do you exactly mean by collision?
I mean is there an point out of building adresses without connected to the network? i think no..

The probability of a collision is found by a standard formula: p = 1 - k! / N^k-1(N-k)!, where k is the number of hashes generated (100x10¹⁰x10³) and N is the number of possible hashes (2¹⁶⁰).

This is a difficult number to calculate, but there is a good approximation: p = 1 - e^-k(k-1)/2N

But even that value is difficult to compute because of the precision needed. Here is another approximation p = k²/2N.

So the answer is that the probability of at least one collision is approximately 7x10^-19 or 0.00000000000000007%