[ANN][GRS] Groestlcoin | 1st to activate Segwit & Taproot

[IMZ]

Lonely Highway Delivery Guy accepts GRS

Just had beer and meat delivered. Paid with 667 GRS. This 'occasional merchant-trader' is assisted by IndiaMikeZulu. LHDG got her first GRS at 750. Sold the lot at 2500. Now has a bid up for 8500 GRS at 1000.

http://imgur.com/a/8BcHZ

[IMZ]

Coming along nicely:

https://www.coinexchange.io/market/GRS/BTC

https://www.coinexchange.io/market/GRS/ETH

Edit: me still plodding along here. Trying to keep a fair buy-sell spread without getting my toes trodden on.

[divinsky]

New GRS Pool
 www.ch-pool.com


ALGORITHM: groestl
STRATUM: stratum+tcp://ch-pool.com
PORT: 7140 (diff: '4') / 7150 (diff: '10') / 7160 (diff: '50')
Username: wallet address
Password: anything

Exemple: stratum+tcp://ch-pool.com:7140 -u YOURWALLETHERE -p x


Live stats
Pool fees: 0.5%
Instant mining payouts


Twitter: www.twitter.com/ch_pools
Forum: https://bitcointalk.org/index.php?topic=1927339.0

[jackielove4u]

New GRS Pool
 www.ch-pool.com


ALGORITHM: groestl
STRATUM: stratum+tcp://ch-pool.com
PORT: 7140 (diff: '4') / 7150 (diff: '10') / 7160 (diff: '50')
Username: wallet address
Password: anything

Exemple: stratum+tcp://ch-pool.com:7140 -u YOURWALLETHERE -p x


Pool fees: 0.5%
Reward time: 10 minutes
Minimum payment: 0.01 GRS


Twitter: www.twitter.com/ch_pools

1) Make sure u have GRS Core 2.13.3 running.
2) Make sure u have patched ur pool to enable segwit transactions: NOMP: https://github.com/zone117x/node-stratum-pool/pull/115 UNOMP: https://github.com/UNOMP/node-merged-pool/pull/4 YIIMP: https://github.com/tpruvot/yiimp/commits/segwit
3) Put a unique coinbase text so we can identify you. Currently it says yiimp?
4) Can you tell us what walletaddress the pool uses so we can tag you on the blockexplorer?
5) Cant we see which blocks your pool mined on your pool site?

[IMZ]

Wrote this 'Report' on crypto adoption:

http://groestlcoin.org/forum/index.php?topic=477.105

Abd something else also came up in the conversation:

remember when hard cap was a major attraction of cryptos? Then smart contracts and some other stuff took the limelight? Well, the concern about world debt, which just refuses to lie down, is going to (ultimately) direct attention back to established hard-capped cryptos.

Niiiice!

[IMZ]

https://www.reddit.com/r/CryptoCurrency/

If anyone has a little spare time, there are many newcomers asking on the threads here about the most basic realities of cryptos. We have the strength of solid crypto and a small and sane community -- it's a real asset!

EDIT: Wow! Cryptos has pulled nearly $US 5,000 Millions in new capital since I got out of bed this morning.

And bought 700 GRS worth of groceries yesterday.

[priestc]

I tried to generate an address with the Groestlcoin paper wallet generator, but the address it gave had a "checksum error". The rivate key also gives me a checksum error too.

Here is the address: Foi3FNkp6f2u1aVyBLpUuQjAtvXvLoQyDz

and the corresponding private key also gives me a checksum error: 5KDcgddMkhPsLFypd1giap5fziz43SazRupaTmLYWvVmcu5YS9g

by any chance did Groestlcoin change the base58 address encoding that bitcoin uses? Why would it give me this error?

Here is the python code I'm using:

>>> from base58 import b58decode_check
>>> b58decode_check("Foi3FNkp6f2u1aVyBLpUuQjAtvXvLoQyDz")
ValueError: Invalid checksum
>>> b58decode_check("5KDcgddMkhPsLFypd1giap5fziz43SazRupaTmLYWvVmcu5YS9g")
ValueError: Invalid checksum


This base58 library works fine for other BTC forked coins like LTC, PPC, Doge, etc...

[jackielove4u]

I tried to generate an address with the Groestlcoin paper wallet generator, but the address it gave had a "checksum error". The rivate key also gives me a checksum error too.

Here is the address: Foi3FNkp6f2u1aVyBLpUuQjAtvXvLoQyDz

and the corresponding private key also gives me a checksum error: 5KDcgddMkhPsLFypd1giap5fziz43SazRupaTmLYWvVmcu5YS9g

by any chance did Groestlcoin change the base58 address encoding that bitcoin uses? Why would it give me this error?

Here is the python code I'm using:

>>> from base58 import b58decode_check
>>> b58decode_check("Foi3FNkp6f2u1aVyBLpUuQjAtvXvLoQyDz")
ValueError: Invalid checksum
>>> b58decode_check("5KDcgddMkhPsLFypd1giap5fziz43SazRupaTmLYWvVmcu5YS9g")
ValueError: Invalid checksum


This base58 library works fine for other BTC forked coins like LTC, PPC, Doge, etc...

Chris,

Did you create the Groestlcoin paperwallet generator online or offline (http://groestlcoin.org/forum/index.php?topic=314.0)?

Groestlcoin is not a normal Bitcoin fork, we groestlized all hashes (not only pow). So yes, base58 address encoding uses double groestl512 instead of double sha256. Our privkey starts with a "5" and multisig/segwit addresses starts with a "3" like bitcoin. But the beauty of it is: You cant send accidentally grs to btc address 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.

I c you are a python guy so have a look at this commit and you will understand: https://github.com/Groestlcoin/electrumx-grs/commit/b7345bf871f3c9c19674e8b1ec51d644053895cc

I verified your generated public and priv key and they are valid! Dont use it anymore tho since you shared the priv key with us.

[divinsky]

New GRS Pool
 www.ch-pool.com


ALGORITHM: groestl
STRATUM: stratum+tcp://ch-pool.com
PORT: 7140 (diff: '4') / 7150 (diff: '10') / 7160 (diff: '50')
Username: wallet address
Password: anything

Exemple: stratum+tcp://ch-pool.com:7140 -u YOURWALLETHERE -p x


Pool fees: 0.5%
Reward time: 10 minutes
Minimum payment: 0.01 GRS


Twitter: www.twitter.com/ch_pools

1) Make sure u have GRS Core 2.13.3 running.
2) Make sure u have patched ur pool to enable segwit transactions: NOMP: https://github.com/zone117x/node-stratum-pool/pull/115 UNOMP: https://github.com/UNOMP/node-merged-pool/pull/4 YIIMP: https://github.com/tpruvot/yiimp/commits/segwit
3) Put a unique coinbase text so we can identify you. Currently it says yiimp?
4) Can you tell us what walletaddress the pool uses so we can tag you on the blockexplorer?
5) Cant we see which blocks your pool mined on your pool site?

1) We have the latest wallet. ['version': 2130300]

2) The pool is on UNOMP and is SW ready
 
3) Don't know how to do this
 
4) FXud4Lurb8XzGvTAN9EdcDJGMkJuAcRA7k
 
5) You can’t see that yet, everything is ready and we are waiting for miners.

[jwinterm]

Any updates from the guy who wanted million GRS bounty to work on stuff?

[IMZ]

Any updates from the guy who wanted million GRS bounty to work on stuff?

I don't think so, jwin.

[And tee hee -- I see you over on Reddit!]

[jwinterm]

Any updates from the guy who wanted million GRS bounty to work on stuff?

I don't think so, jwin.

[And tee hee -- I see you over on Reddit!]

That's a shame, and yea, I pretty much live on reddit, so not too hard to spot me there probably.

How much longer is website giveaway signups going on? Another week?

[IMZ]

' . . the 'bridge' between us and the outside has grown from an Adventure-Movie rope-and-plank structure to at least a bitumen country highway . . . '

http://groestlcoin.org/forum/index.php?topic=477.msg1785#msg1785

[jackielove4u]

Any updates from the guy who wanted million GRS bounty to work on stuff?

I don't think so, jwin.

[And tee hee -- I see you over on Reddit!]

That's a shame

How much longer is website giveaway signups going on? Another week?

I have asked tenletters to post an update for you (I speak him often on Telegram).

Giveaway signups will be going on till 22 June.

[priestc]

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

[jackielove4u]

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

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

[priestc]

You cant send accidentally grs to another coin and vice versa. No more mistakes

That what the version byte is for. The first letter of the address is what keeps you from sending currency to the wrong type of address. All changing the base58 does is make it more error prone. If I had not happened to stumble upon the fact that GRS uses a different hash algorithm for addresses, I may have implemented GRS to some application using sha256, which would have resulted in me and anyone using that app to lose money by sending to an invalid address. Is very unusual for an altcoin to change the address hash, in fact GRS is the first I've come upon.

I see the bip32utils project you have forked already includes a base58 implementation using groestl. Could you put it up on pypi so I can add it to my project? My project is called moneywagon, it's a cryptocurrency platform for building wallets and exchanges and stuff like that on top of. Also, it seems you also removed sha256 from the transaction serialization code too? If so then another forked python library with groetsl support is needed to make transactions, so the groestl-hash function needs to be added to pypi too.

Also I noticed there is a groestl fork of bitpay insight on the groestlcoin github. Is there a pubic instance of this running?

[jackielove4u]

That what the version byte is for. The first letter of the address is what keeps you from sending currency to the wrong type of address.

Thats not correct. You could still send accidentally GRS to Fuelcoin, Fluttercoin, Fujicoin and all other coins that start with a leading F symbol.
With changing the version byte you can still send currency to the wrong type of address. We need to protect the crypto users.

All changing the base58 does is make it more error prone. If I had not happened to stumble upon the fact that GRS uses a different hash algorithm for addresses, I may have implemented GRS to some application using sha256, which would have resulted in me and anyone using that app to lose money by sending to an invalid address.

Not if you build the checksum validator in all wallets like we have. If you would have tried to send GRS to that address then any of our wallets would say: invalid address. Thus the transaction would never been happend.

Is very unusual for an altcoin to change the address hash, in fact GRS is the first I've come upon.

I know right? Spread the word. We are unique.

I see the bip32utils project you have forked already includes a base58 implementation using groestl. Could you put it up on pypi so I can add it to my project? My project is called moneywagon, it's a cryptocurrency platform for building wallets and exchanges and stuff like that on top of. Also, it seems you also removed sha256 from the transaction serialization code too? If so then another forked python library with groetsl support is needed to make transactions, so the groestl-hash function needs to be added to pypi too.

Interesting project. This might be usefull info for you: http://groestlcoin.org/forum/index.php?topic=343.0
Transaction serialization uses single sha256 (instead of double sha256). A summary what hashes we changed can be found here:
http://groestlcoin.org/forum/index.php?topic=344.0

Also I noticed there is a groestl fork of bitpay insight on the groestlcoin github. Is there a pubic instance of this running?

PM me for info

[IMZ]

Memo from the Night Shift:

Wheee!

Japan and Korea (and India) are the ‘Asian trading-zone’ – which includes Western Australia.

We’re avidly following events here: KRW volume; Korean banks shut for the weekend; are military tensions on the peninsula really driving adoption to some degree?

[IMZ]

Well, 'pullback in price' sure isn't keeping me awake at night.

Check this list*: http://www.marketoracle.co.uk/UserInfo-Jeff_Berwick.html

Note that there's hardly any Bitcoin stuff until mid-2016, but now it's coming thick and fast.

Meanwhile: http://www.zerohedge.com/news/2017-05-28/who-accepts-bitcoins-payment-list-companies-stores-shops  Note that, as the article comes from 99Bitcoins.com, it's information directly from Planet Krypto.

And three years ago today, some guy opined: ' . . . altcoins . . . are the future . . . ' Oh wait! It's me!

http://www.marketoracle.co.uk/Article45811.html


*Let there be no mistake, guys: half the authors who write for M.O. are half mad; but -- like Zero Hedge -- they point you in the right direction.