Use other cryptographic hash to create bitcoin address

[Sanglotslongs]

Hello,

I'm studying this graph "how to generate a bitcoin address" :

https://royalforkblog.github.io/2014/08/11/graphical-address-generator/

But if SHA256 and RIPE160 give us only bytecode that is X bits long and the orignal secret to all of this is a random 256 bits number.

Can I create bitcoin address with another cryptographic hash like BLAKE2 ?

[1714631814]

1714631814

[1714631814]

1714631814

[1714631814]

1714631814

[1714631814]

1714631814

[1714631814]

1714631814

[nc50lc]

Possible but you won't be able to spend from it.
Eg.: P2PKH's locking script contains OP_HASH160 which specifically uses SHA256 and RIPEMD-160.
Clients wont be able to verify a "Public Key Hash" generated from other cryptographic hash functions.

This is worth the read: https://learnmeabitcoin.com/technical/p2pkh | https://en.bitcoin.it/wiki/Script#Crypto

[pooya87]

Clients wont be able to verify a "Public Key Hash" generated from other cryptographic hash functions.

To be clear: There is no OP code for OP_BLAKE2 in bitcoin scripts so you can't even create it for clients to want to verify.
There are only 3 hash algorithms available as OP codes: SHA1, SHA256, and RIPEMD160. (there are also 2 "combination" OP codes OP_HASH160 and OP_HASH256 which use the same hash algorithms).

Adding a new hash algorithm to OP codes requires a soft fork.

[NotATether]

There are only 3 hash algorithms available as OP codes: SHA1, SHA256, and RIPEMD160.

Also there's no way to encode  a sha1 or sha256 message as a base58 address (thus send it to someone to pay you at), because all of the currently defined formats expect ripemd160 hash as input.

[pooya87]

Also there's no way to encode  a sha1 or sha256 message as a base58 address (thus send it to someone to pay you at), because all of the currently defined formats expect ripemd160 hash as input.

True but addresses are more like agreements rather than consensus rules, so technically two parties can come up with an agreement that a certain encoded strings represent certain script types. It's just that we agree that a base58 string that is [0x00 + 20 bytes] represents a P2PKH script, we can simply extend this agreement (whether globally or between two parties) that a base58 string that is [0x01 + 20 bytes] P2PKH with the hash replaced by SHA1.

P.S. SHA1 is not safe to use by the way.