x

[SwayStar123]

x

[1715095521]

1715095521

[1715095521]

1715095521

[1715095521]

1715095521

[Anycoin Direct Support]

Hello SwayStar123,


We noticed that your number of "Most unique addresses" is a bit off. Those numbers on blockchain.info are the most unique addresses used on one day.
If you look at Bitinfocharts.com at the top 100 of richest bitcoin addresses, you can see that there are at least 20M addresses that have a transaction history and a balance.
This means that we can state that the actual amount of addresses used is actually much greater. Not that this severely impacts the outcome of your calculations, but it is something to keep in mind.


With kind regards,
The Anycoin Direct team

[bitmover]

I was just scrolling through the forums and i saw a comment on how many percent of total bitcoin addresses was used, so i looked for the answer, i couldnt find anything specific so i will find my own answer
https://bitcointalk.org/index.php?topic=4405638.0
Number of possible bitcoin addresses- 1461501637330902918203684832716283019655932542976

Most unique addresses ever used (idk how this fluctuates but thats what i found online) -1,054,711

1,054,711 / 1461501637330902918203684832716283019655932542976= 7.2166255e-43

Which is 0.00000000000000000000000000000000000000000072166255% Of all addresses ever

Funfact there are 10000000000000000000000000000000000000000000000000000 number of atoms in the sun so if you assigned a bitcoin address to every attom in the sun you would get upto 0.001461% of the atoms covered! That might not seem like much but compared to other numbers this number is very big

Total number of possible privatekeys is 2^256 or in base 10 it would be 10^77.

2^256= 115,792,089,237,316,195,423,570,985,008,687,907,853,269,984,665,640,564,039,457,584,007,913,129,639,936
 according to https://www.calculator.net/big-number-calculator.html?cx=2&cy=256&cp=20&co=pow (big number calculator)

[andrew1carlssin]

I was just scrolling through the forums and i saw a comment on how many percent of total bitcoin addresses was used, so i looked for the answer, i couldnt find anything specific so i will find my own answer
https://bitcointalk.org/index.php?topic=4405638.0
Number of possible bitcoin addresses- 1461501637330902918203684832716283019655932542976

Most unique addresses ever used (idk how this fluctuates but thats what i found online) -1,054,711

1,054,711 / 1461501637330902918203684832716283019655932542976= 7.2166255e-43

Which is 0.00000000000000000000000000000000000000000072166255% Of all addresses ever

Funfact there are 10000000000000000000000000000000000000000000000000000 number of atoms in the sun so if you assigned a bitcoin address to every attom in the sun you would get upto 0.001461% of the atoms covered! That might not seem like much but compared to other numbers this number is very big

edit: number of unique addresses are actually around 20million so the total number of possible addresses used it actually  0.000000000000000000000000000000000000000013684555%

Sometimes using a scientific notation makes our life easier ..so just a quick revision

10⁰ equals One;
10¹ equals Ten;
10² equals Hundred;
10³ equals Thousand;
10⁴ equals Ten-thousand;
10⁵ equals Hundred-thousand;
10⁶ equals Million;
10⁷ ...

So we get the idea we are "10⁶" community .. so we can comeback slowly to the avarage joe reality and our bitcoin calc,
(meaning Bitcoin Arithmetic Unit (ALU) and leave the FPU floating-point unit to deal with DPS DIgital Signal Processor ..)
System on a chip

[bitmover]

Im not quite  sure but doesnt every address have only 1 private key?

Yes.

That's the total number of possible addresses
2^256= 115,792,089,237,316,195,423,570,985,008,687,907,853,269,984,665,640,564,039,457,584,007,913,129,639,936

[_oh_no_stop_this_]

You can try to generate lots of addresses and maybe some will have balance on them

[Rath_]

You can try to generate lots of addresses and maybe some will have balance on them

Actually, it's not as easy as you might think. There is a group called LBC which aim so find private keys which correspond to addresses which have some bitcoins on them. As it turns out, it is not really profitable. You would better spend your money on mining either altcoins using GPUs or Bitcoin using ASICs. You can find more information about it in the link above.

[_oh_no_stop_this_]

You can try to generate lots of addresses and maybe some will have balance on them

Actually, it's not as easy as you might think. There is a group called LBC which aim so find private keys which correspond to addresses which have some bitcoins on them. As it turns out, it is not really profitable. You would better spend your money on mining either altcoins using GPUs or Bitcoin using ASICs. You can find more information about it in the link above.

Oh thank you! I used to have their website address but then lost it...
Maybe it can be profitable if someone will make an FPGA design specifically for that purpose... but I am not sure anyways, it would be nice to think of some kind of protection mechanism... it seems to be impossible at the first sight, but maybe keeping funds on thousands of wallets? Could be an interesting idea for institutional investors...

[starmyc]

Most unique addresses ever used (idk how this fluctuates but thats what i found online) -1,054,711

1,054,711 / 1461501637330902918203684832716283019655932542976= 7.2166255e-43

FYI the number of all addresses ever used at least once on the bitcoin blockchain is more that 400M (The exact number I computed for all blk files from 0 to 1,275 is 401,407,598 - This number is getting bigger at each new block).

[_oh_no_stop_this_]

Most unique addresses ever used (idk how this fluctuates but thats what i found online) -1,054,711

1,054,711 / 1461501637330902918203684832716283019655932542976= 7.2166255e-43

FYI the number of all addresses ever used at least once on the bitcoin blockchain is more that 400M (The exact number I computed for all blk files from 0 to 1,275 is 401,407,598 - This number is getting bigger at each new block).

Did you compute this for yourself just once, or you have an API so others may get updated statistics?

[starmyc]

Most unique addresses ever used (idk how this fluctuates but thats what i found online) -1,054,711

1,054,711 / 1461501637330902918203684832716283019655932542976= 7.2166255e-43

FYI the number of all addresses ever used at least once on the bitcoin blockchain is more that 400M (The exact number I computed for all blk files from 0 to 1,275 is 401,407,598 - This number is getting bigger at each new block).

Did you compute this for yourself just once, or you have an API so others may get updated statistics?

Did it myself for a friend with my own block parser, with a set of shell scripts.

[_oh_no_stop_this_]

Most unique addresses ever used (idk how this fluctuates but thats what i found online) -1,054,711

1,054,711 / 1461501637330902918203684832716283019655932542976= 7.2166255e-43

FYI the number of all addresses ever used at least once on the bitcoin blockchain is more that 400M (The exact number I computed for all blk files from 0 to 1,275 is 401,407,598 - This number is getting bigger at each new block).

Did you compute this for yourself just once, or you have an API so others may get updated statistics?

Did it myself for a friend with my own block parser, with a set of shell scripts.

Okay, that is an interesting statistical data that I haven't read about before. Maybe it could be useful for something... maybe when you generate another wallet you can check against that list to make sure it's unique..

[LUKEEEEE]

Number of possible addresses is 2^160. Number of public keys is 2^256.

Cca 2^96 public keys can share same address but cannot steal from each other. So effectively there are "2^256" addresses.
How is that possible? Simple, address is hashed public key.

[bob123]

Total number of possible privatekeys is 2^256 or in base 10 it would be 10^77.

Im not quite  sure but doesnt every address have only 1 private key?

The number of possible private keys is indeed 2^256 (A private key is a 256 bit random number).
But there are 2^160 addresses possible (An address is the RIPEMD-160 hash of a SHA256 hash of the public key -> 160 bit long).

There are 2^96 private keys which match one address ON AVERAGE. This is simply due to the fact that the input dictionary (256 bit) is bigger than the output dictionary (160 bit).

Note that this does NOT impose any security risks.

[_oh_no_stop_this_]

Total number of possible privatekeys is 2^256 or in base 10 it would be 10^77.

Im not quite  sure but doesnt every address have only 1 private key?

The number of possible private keys is indeed 2^256 (A private key is a 256 bit random number).
But there are 2^160 addresses possible (An address is the RIPEMD-160 hash of a SHA256 hash of the public key -> 160 bit long).

There are 2^96 private keys which match one address ON AVERAGE. This is simply due to the fact that the input dictionary (256 bit) is bigger than the output dictionary (160 bit).

Note that this does NOT impose any security risks.

So let's say I have 1 wallet with 2 private keys pointing to it. If someone sends me a coin to this wallet, then any of my private keys can spend it!?

[TryNinja]

So let's say I have 1 wallet with 2 private keys pointing to it. If someone sends me a coin to this wallet, then any of my private keys can spend it!?

No. But since your wallet consists of both private keys, the software will know (and use) which private key can spend the coins.

If you receive the coins in the address A and export the Address B private key, you won't be able to spend the coins. You will need the private key A.

[bob123]

The number of possible private keys is indeed 2^256 (A private key is a 256 bit random number).
But there are 2^160 addresses possible (An address is the RIPEMD-160 hash of a SHA256 hash of the public key -> 160 bit long).

There are 2^96 private keys which match one address ON AVERAGE. This is simply due to the fact that the input dictionary (256 bit) is bigger than the output dictionary (160 bit).

Note that this does NOT impose any security risks.

So let's say I have 1 wallet with 2 private keys pointing to it. If someone sends me a coin to this wallet, then any of my private keys can spend it!?

No. A 'wallet' is simply a piece of software which handles private-/public- keypairs.


When creating an 'address' your doing it this way:

1. Create random number (private key)
2. Calculate public key out of private key
3. Hash the public key with RIPEMD-160(SHA256(public_key)) = Address

Now, theoretically there are 2^96 different private keys which do all 'create' the same address (on average).
This means that it is theoretically(!) possible to create two different private keys, which do refer to the same address. (Practically this won't happen, ever.)

Note that addresses do NOT exist on a technical level. They are just an abstractions for us humans making it easier to read.


Coins can not be send 'to a wallet'. The UTXO's are being assigned to public keys. And you will be able to spend these UTXO's using the corresponding private key.

[_oh_no_stop_this_]

The number of possible private keys is indeed 2^256 (A private key is a 256 bit random number).
But there are 2^160 addresses possible (An address is the RIPEMD-160 hash of a SHA256 hash of the public key -> 160 bit long).

There are 2^96 private keys which match one address ON AVERAGE. This is simply due to the fact that the input dictionary (256 bit) is bigger than the output dictionary (160 bit).

Note that this does NOT impose any security risks.

So let's say I have 1 wallet with 2 private keys pointing to it. If someone sends me a coin to this wallet, then any of my private keys can spend it!?

No. A 'wallet' is simply a piece of software which handles private-/public- keypairs.


When creating an 'address' your doing it this way:

1. Create random number (private key)
2. Calculate public key out of private key
3. Hash the public key with RIPEMD-160(SHA256(public_key)) = Address

Now, theoretically there are 2^96 different private keys which do all 'create' the same address (on average).
This means that it is theoretically(!) possible to create two different private keys, which do refer to the same address. (Practically this won't happen, ever.)

Note that addresses do NOT exist on a technical level. They are just an abstractions for us humans making it easier to read.


Coins can not be send 'to a wallet'. The UTXO's are being assigned to public keys. And you will be able to spend these UTXO's using the corresponding private key.

Thanks for explanation, I was referring "wallet" to the hashed public key, sorry for confusion.
So just to make it clear:
1. I send bitcoin to your hashed public key
2. It is being assigned to your real public key
3. When you send it you sign transaction with your private key

How does it go from [1] to [2] ? Since you only reveal your public key only when you sign transactions.
And you don't sign anything when you receive coins; therefore, leaving public key secret.
Are you sure coins are assigned to the real public key, not to the hashed public key?

[bob123]

So just to make it clear:
1. I send bitcoin to your hashed public key
2. It is being assigned to your real public key
3. When you send it you sign transaction with your private key

How does it go from [1] to [2] ? Since you only reveal your public key only when you sign transactions.

In the first step you are creating new UTXO's. For someone to use this UTXO, he has to meet conditions inside the script of the UTXO.
If i then want to create a new transaction with this UTXO, i have to supply a corresponding screept that meets these condition (e.g. scriptSig). This requires to reveal the public key and using the private key to sign.

And you don't sign anything when you receive coins; therefore, leaving public key secret.

Yes, thats correct.

Are you sure coins are assigned to the real public key, not to the hashed public key?

Coins arent really assigned. They exist as unspent transaction outputs (UTXO).
To claim the ownership and combining their value into new UTXO(s), you have to prove ownership.

Pay to public key hash (P2PKH) does require to create a script: OP_DUP OP_HASH160 <pubKeyHash> OP_EQUALVERIFY OP_CHECKSIG.
To spend these coins you have to provide the public key and a matching signature.

A P2SH UTXO does include the hash of the spending condition (instead of the condition itself).
To spend these coins you are providing the redeem script itself, which is then being checked and evaluated against the redeem script hash during a transaction.

[_oh_no_stop_this_]

So just to make it clear:
1. I send bitcoin to your hashed public key
2. It is being assigned to your real public key
3. When you send it you sign transaction with your private key

How does it go from [1] to [2] ? Since you only reveal your public key only when you sign transactions.

In the first step you are creating new UTXO's. For someone to use this UTXO, he has to meet conditions inside the script of the UTXO.
If i then want to create a new transaction with this UTXO, i have to supply a corresponding screept that meets these condition (e.g. scriptSig). This requires to reveal the public key and using the private key to sign.

And you don't sign anything when you receive coins; therefore, leaving public key secret.

Yes, thats correct.

Are you sure coins are assigned to the real public key, not to the hashed public key?

Coins arent really assigned. They exist as unspent transaction outputs (UTXO).
To claim the ownership and combining their value into new UTXO(s), you have to prove ownership.

Pay to public key hash (P2PKH) does require to create a script: OP_DUP OP_HASH160 <pubKeyHash> OP_EQUALVERIFY OP_CHECKSIG.
To spend these coins you have to provide the public key and a matching signature.

A P2SH UTXO does include the hash of the spending condition (instead of the condition itself).
To spend these coins you are providing the redeem script itself, which is then being checked and evaluated against the redeem script hash during a transaction.

I suspect you are a programmer

So to make it clear for me:
2 different private keys may have the ability (although the possibility that happens is extremely low) to prove ownership of coins assigned to the single "wallet" (e.g. hashed public key)?