Quote from: shorena on October 15, 2015, 08:55:32 AM

It explains how a TX is created and confirmed, it does not explain how addresses are created.

I see what you meant there made an error, but the info-graphic still is handy.
It took me a while there to get the question misread it your right the private key comes first the bitcoin address comes last not that the bitcoin address is deduced backwards to find the master public key then the private key.

Was thinking of a strange configuration where the master public key reveals a private key through a hash in a deterministic wallet exploit.
https://bitcoinmagazine.com/articles/deterministic-wallets-advantages-flaw-1385450276
https://en.bitcoin.it/wiki/BIP_0032

Posting the proper one:

Quote from: Swordsoffreedom on October 15, 2015, 08:47:12 AM

Op's question was
Can a bitcoin address can be recovered from public key... If not so how is it related to bitcoin address???

The answer is NO
-snip-

Quote from: shorena on October 15, 2015, 08:55:32 AM

Your answer is wrong, same as 90% of others here that have no idea what they are talking about. The address is the hash the of public key. Of course anyone can hash the public key in the correct way and get the address. Thus the address can be "recovered" from the public key.

What you are possibly refering to is the private key. The chain goes one way like this:

private key -> public key -> address

not (!) the other way around

address -\> public key -\> private key

but thats not the question asked by OP.

In that case, I am confused (!) Following the Process it is Private -> Public -> Address
EDIT: Read it as no its the other way around nvm your fine.

How to create Bitcoin Address
https://en.bitcoin.it/wiki/Technical_background_of_version_1_Bitcoin_addresses

0 - Having a private ECDSA key

   18E14A7B6A307F426A94F8114701E7C8E774E7F9A47E2C2035DB29A206321725

1 - Take the corresponding public key generated with it (65 bytes, 1 byte 0x04, 32 bytes corresponding to X coordinate, 32 bytes corresponding to Y coordinate)

   0450863AD64A87AE8A2FE83C1AF1A8403CB53F53E486D8511DAD8A04887E5B23522CD470243453A 299FA9E77237716103ABC11A1DF38855ED6F2EE187E9C582BA6

2 - Perform SHA-256 hashing on the public key

   600FFE422B4E00731A59557A5CCA46CC183944191006324A447BDB2D98D4B408

3 - Perform RIPEMD-160 hashing on the result of SHA-256

   010966776006953D5567439E5E39F86A0D273BEE

4 - Add version byte in front of RIPEMD-160 hash (0x00 for Main Network)

   00010966776006953D5567439E5E39F86A0D273BEE

(note that below steps are the Base58Check encoding, which has multiple library options available implementing it)
5 - Perform SHA-256 hash on the extended RIPEMD-160 result

   445C7A8007A93D8733188288BB320A8FE2DEBD2AE1B47F0F50BC10BAE845C094

6 - Perform SHA-256 hash on the result of the previous SHA-256 hash

   D61967F63C7DD183914A4AE452C9F6AD5D462CE3D277798075B107615C1A8A30

7 - Take the first 4 bytes of the second SHA-256 hash. This is the address checksum

   D61967F6

8 - Add the 4 checksum bytes from stage 7 at the end of extended RIPEMD-160 hash from stage 4. This is the 25-byte binary Bitcoin Address.

   00010966776006953D5567439E5E39F86A0D273BEED61967F6

9 - Convert the result from a byte string into a base58 string using Base58Check encoding. This is the most commonly used Bitcoin Address format

   16UwLL9Risc3QfPqBUvKofHmBQ7wMtjvM

http://security.stackexchange.com/questions/54136/possible-to-derive-private-key-from-public-key-given-enough-computing-power