Quote from: priestc on May 26, 2017, 08:54:37 AM

Quote from: jackielove4u on May 25, 2017, 02:09:40 PM

So yes, base58 address encoding uses double groestl512 instead of double sha256.

I see. If there a reason for this? I can understand why you'd change the POW, but why change the address hash? There doesn't seem to be any benefit to doing that, other than to make it harder for people like me to implement wallets. I now have to fork every base58 library to replace sha256 with groestl512, which I've done here: https://github.com/priestc/Groestlbase58, except i can't find a good Groestl implementation in python, so Groestlcoin will unfortunately remain unimplemented in my project Sad

Yes we have our reason for this which i already tried explaining before:
You cant send accidentally grs to another coin and vice versa. No more mistakes (like sending ltc to a btc multisig) because we changed base58. A grs address (public/priv/segwit/multisig) ONLY works on grs blockchain. This is to protect our users sending coins to another coin address.

What kind of wallet are you trying to implement? If its interesting enough, we can do all the hard work for you.

Not sure if u had a look at our github with over 100 repositories. Anyway we use this groestl implementation in python for electrum and bip32utils: https://github.com/Groestlcoin/groestlcoin-hash-python
Example: https://github.com/Groestlcoin/bip32utils