The method of calculating a Bitcoin P2PKH deal with in base56check encoding format is as follows:
- get a public key from the non-public key
- hash the general public key with the SHA256 hash operate
- hash the end result from the 2nd step with the RIPEMD160 hash operate
- prepend 0x00 to the end result from the earlier step
- calculate checksum of the end result from the 4th step as sha256(sha256(end result))
- take the primary 4 bytes from the obtained end result and append it to the content material from the step 4
- encode it with base58
So, following these steps, the outcomes are as follows:
- 03486669962008e0713660b6d69117a65fcecd221d06c1e5077b4d9cd477c0cf98
- af1a74e378749900ab079315e518dfd27196193ca139f1e8a037e5851f8a5ecb
- cfcc2ce2d8fc82b2b0837b6c1775d5edcffc107f
- 00cfcc2ce2d8fc82b2b0837b6c1775d5edcffc107f
- 79ccb53d787d2c54087ca095504d92ee2ad2bc93a0986ef9d19a017ef8232cdd
- 00cfcc2ce2d8fc82b2b0837b6c1775d5edcffc107f79ccb53d
- 1KwjU4UknzbXh1rnP1jAKz9wwjcuYwe9AC
Trying on the video you offered, operation RIPEMD(SHA256(<pubkey>)) does not give an accurate end result to him, nevertheless it finally ends up getting a great deal with. Very unusual certainly. I see that within the feedback of the video there are additionally individuals who had the identical drawback.
So, the conclusion is that you’re not doing something fallacious. One thing is fallacious (or extra appropriately say unusual) within the video I’d say.