Author

Topic: bitcoin version 1, addresses space 2^160 (Read 227 times)

legendary
Activity: 3122
Merit: 2178
Playgram - The Telegram Casino
September 24, 2019, 08:42:42 AM
#9
chose any public address with an output spent (must have at least one output transaction ) i will easy extract the public key  Grin

i learned this few hours ago Tongue

Yes, that's because outgoing transactions from P2PKH addresses need to publish the public key as well, otherwise no one could verify that the transaction is valid. That's not "extracting the public key" that's merely parsing public information.


jr. member
Activity: 56
Merit: 3
September 24, 2019, 07:33:20 AM
#8
can we go address > public key ?
Whether the public key can be derived from a P2PKH address? No.

an address is the hash of the public key where as those outputs
can we go address > public key ?
no we can not go from address to public key

chose any public address with an output spent (must have at least one output transaction ) i will easy extract the public key  Grin

i learned this few hours ago Tongue
legendary
Activity: 3472
Merit: 10611
September 24, 2019, 04:20:54 AM
#7
an address is the hash of the public key where as those outputs
i feel almost every words of you has some hidden meaning 

can we go address > public key ?

what i meant was to point out that there is a difference between addresses and scripts. address is the human readable encoding of some of the most popular scripts, in other words we have more scripts than addresses. example is the P2PK scripts that were mentioned, another would be those with OP_CSV or other OP codes in them.

as for second part, no we can not go from address to public key since hash algorithms used in bitcoin are one way functions.
legendary
Activity: 3122
Merit: 2178
Playgram - The Telegram Casino
September 24, 2019, 03:06:32 AM
#6
can we go address > public key ?

What do you mean? Whether the public key can be derived from a P2PKH address? No. The public key is cryptographically hashed, which means it's been put through a cryptographically secure one-way function that does not allow for an easy reversal of the process.
jr. member
Activity: 56
Merit: 3
September 24, 2019, 12:09:05 AM
#5
an address is the hash of the public key where as those outputs

i feel almost every words of you has some hidden meaning 

can we go address > public key ?

Code:
base58check({version byte}RIPEMD160(SHA256(pubkey)))


http://gobittest.appspot.com/Address

legendary
Activity: 3472
Merit: 10611
September 23, 2019, 11:01:43 PM
#4
i have this question when exactly the year and month we start using 2^256?

the year that we succeed at optimizing the algorithm for nested hash function {RIPEMD160(SHA256)} and find a collision. nobody can predict when that can happen, estimating it would be at least another 50 years.

~
am i understand you correctly!
all bitcoin addresses use 2^160 160bits and the only exception 2009 and 2010 that use 2^256 Embarrassed
an address is the hash of the public key where as those outputs from first year(s) were the public key itself.

There's no change of "bitcoin version 1", assuming you're talking about Bitcoin address which have prefix 1.

Bech32 address format have more character count, but according to https://bitcoin.stackexchange.com/a/69554 it also uses RIPEMD-160 which means current address space is still 2^160, but only with different format/encoding. CMIIW.
P2WPKH scripts are using the same RIPEMD160(SHA256(pubkey)) digests so they are the same 20 bytes (160 bits). P2WSH scripts use SHA256(script) digest so they are 32 bytes (256 bits) and both of them use Bech32 encoding to represent the corresponding "address".
jr. member
Activity: 56
Merit: 3
September 23, 2019, 03:01:32 PM
#3
Bitcoin has almost always used address space of 2^160, and is still using it.

The only exception are those addresses that were created in 2009 (and 2010) --snip--
am i understand you correctly!
all bitcoin addresses use 2^160 160bits and the only exception 2009 and 2010 that use 2^256 Embarrassed


There's no change of "bitcoin version 1", assuming you're talking about Bitcoin address which have prefix 1.

Bech32 address format have more character count, but according to https://bitcoin.stackexchange.com/a/69554 it also uses RIPEMD-160 which means current address space is still 2^160, but only with different format/encoding. CMIIW.
not the prefix i meant the the address space ()
this line is clear something to me: There are exactly 2^160 possible addresses as long as we keep using RIPE-MD160.

old topic https://bitcointalksearch.org/topic/how-many-possibly-bitcoin-addresses-are-there-exactly-and-how-long-does-it-24268
full member
Activity: 378
Merit: 197
September 23, 2019, 01:54:33 PM
#2
Bitcoin has almost always used address space of 2^160, and is still using it.

The only exception are those addresses that were created in 2009 (and 2010), that did have and still have an address space of  2^256.
Those addresses are the P2PK addresses. (P2PK= "pay to public key")

P2PK addresses have address space of 2^256, because there is only one public key that corresponds to one private key.
jr. member
Activity: 56
Merit: 3
September 23, 2019, 12:58:41 PM
#1
i have this question when exactly the year and month we start using 2^256?
...
all addresses before 2013 use 2^160
all addresses before 2014 use 2^160

2015  addresses use ?
2016  addresses use ?
2017  addresses use ?

2019  addresses use 2^256


Jump to: