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

[feeleep]

coinmine.pl pool updated

[jackielove4u]

A new major Groestlcoin Core version 2.11.0 is now available for download bringing both new features and bug fixes, so it is recommended to upgrade to it if you are running a full Groestlcoin node or a local Groestlcoin Core wallet.

v2.11.0 is now the official release version of Groestlcoin Core. On top of the new features, this update contains very important security fixes and all users MUST upgrade to this version as soon as possible. Pool operators, P2Pool and solo miners especially, as once BIP 66 is enforced, blockversion 112 (aka 1) and blockversion 2 will be rejected from the network entirely and only blockversion 3 will be accepted.

What's new in version v2.11.0?
This is a major release of Groestlcoin Core, featuring the technical equivalent of Bitcoin v0.11.0 but with Groestlcoin specific patches. On a general level, most of what is new is is hidden where block synchronization and various internals are considerably faster and more efficient, and it has several major privacy improvements.  The most significant changes include:
• Qt dependency changed. Version upgraded to 5.5.
• OpenSSL dependency changed. Version upgraded to 1.0.2a (19 March 2015).
• BerkeleyDB dependency changed. Version for Windows and MAC upgraded to 5.3.21 (11 May 2012).
• Protocolversion changed to 70002
• Blockversion 112 interpreted as version 1. All new blocks will have blockversion 3, but v2.11.0 clients will also accept blockversion 1 (v112) and blockversion 2 blocks until 95% of all blocks will be blockversion 3. After this moment all blockversion 1 and blockversion 2 will be rejected.
• All possible languages added.
• New alert keys added.
• Canonical name for .GroestlCoin in UNIX changed to use all lowercase: .groestlcoin.
• Extra main seeds added.
• New testnet created.
• Comes now with a installer.
• Transaction-URL support of third parties blockexplorers.
• Coin control support.
• Ability to open Groestlcoin URI or payment request.
• Ability to spent unconfirmed coins.
• Ability to see receive and send addresses.
• Groestlcoin-cli. Another change in the v2.11.0 release is moving away from the groestlcoind executable functioning both as a server and as a RPC client. The RPC client functionality (“tell the running groestlcoin daemon to do THIS”) was split into a separate executable, ‘groestlcoin-cli’.
• Transaction malleability-related fixes
• Autotools build system. For v2.11.0 we switched to an autotools-based build system instead of individual makefiles. Using the standard “./autogen.sh; ./configure; make” to build Groestlcoin-Qt and Groestlcoind makes it easier for experienced open source developers to contribute to the project.
• Rebranding to Groestlcoin Core. To reduce confusion between Groestlcoin-the-network and Groestlcoin-the-software we have renamed the reference client to Groestlcoin Core.
• OP_RETURN and data in the block chain support.
• Standard script rules relaxed for P2SH addresses.
• Watch-only wallet support. This allows the wallet to track transactions to and form wallets for which you know the address of but do not have the private key to.
• Memory usage optimization. There have been many changes in this release to reduce the default memory usage of a node.
• Experimental support for big-endian CPU architectures was added in this release.
• Privacy: Stream isolation for Tor. This release adds functionality to create a new circuit for every peer connection, when the software is used with Tor.
• Privacy: Disable wallet transaction broadcast
• Block file pruning for nodes (without wallet). This release supports running a fully validating node without maintaining a copy of the raw block and undo data on disk. Pruning is disabled by default.
• Faster blockchain synchronization due to headers-first synchronization and support for downloading blocks in parallel. Downloading the blockchain is now much quicker and can be completed within a half hour instead of taking hours for some users.
• A REST interface which allows unauthenticated access to public node data when the -rest flag is specified.
• RPC Server “Warm-Up” Mode which starts earlier than previous versions. This helps users or services relying on it know that the server has already started and will be available soon.
• Improved signing security. This is due to using the libsecp256k1 library for signing instead of OpenSSL. libsecp256k1 is a cryptographic library optimized for elliptic curve uses which Groestlcoin relies on and was created by Bitcoin Core developer Pieter Wuille. Featuring better security, via hardening against timing leaks and derandomization, this library is believed to be better tested and more thoroughly reviewed than the implementation in OpenSSL.
• Improved algorithm used for fee estimation. This release automatically estimates how high a transaction fee (or how high a priority) transactions require to be confirmed quickly.
• Consensus library. Starting from v2.11.0, the Groestlcoin Core distribution includes a consensus library. The purpose of this library is to make the verification functionality that is critical to Groestlcoin’s consensus available to other applications, e.g. alternative node implementations.
• New utility applications including groestlcoin-tx for transaction related functionality and groestlcoin-cli for RPC command line functionality as groestlcoind no longer accepts them.
• Strict DER encoding for signatures (BIP 66). This introduces block version 3 and a new consensus rule which prevents non-standard transactions from being included in blocks. This also removes the dependency on OpenSSL’s signature parsing. Eventually, libsecp256k1 will be used for all consensus related tasks, depreciating the need for OpenSSL entirely.
• RPC Access Changes. RPC access now supports binary network addresses. This means that you can specify a single IP address, a CIDR network address or a netmask for accessing the RPC service. Please note, wildcard string matching no longer works and will display an error in the debug.log file when you attempt to use use a wildcard string in the rpcallowip= variable, either as a config setting or launch parameter. Note: IPv6 addresses can also be used.
• Added option -alerts’ to opt out of the network alert system. Please note that disabling network alerts should only be used by power users as this system is used for network emergencies and important security releases. The default behavior is that network alerts are enabled.
• Detect and reject LibreSSL. This prevents a non-approved SSL library being used for compiling Groestlcoin Core, preventing potential consensus compatibility issues.
• Improved getbalance RPC functionality to allow the user to display zero confirmation transactions (this works with watch-only addresses as well).

It is appreciated if feedback of the following is provided:
1. Can you receive coins? (small amounts to avoid losing them)
2. Can you send coins?
3. Can you view your transaction on a third party blockexplorer (restart the client after entering the url of the blockexplorer) ?
4. Can you use the wallet with TOR?
5. Are you able to backup your wallet (wallet.dat) file?
6. Are you able to encrypt your wallet (wallet.dat) file?
7. Are you able to use watch-only function?
8. How long does it take to fully synchronize?
9. Are you able to sign/verify messages?
10. Are you able to see you send/receive addresses?
11. Are you able to use the wallet in your local language?

The application may have unfound bugs and problems. Please report using the issue tracker at github:
https://github.com/groestlcoin/groestlcoin/issues

Important:
• There is no warranty and no party shall be made liable to you for damages. If you lose coins due to this app, no compensation will be given. Use this app solely at your own risk.
• Encrypt your wallet. This can be done by clicking the settings menu from inside the wallet. Make sure your password is secure and do not forget it.
• Make a copy your wallet.dat file as a backup and move it to a secure location:
Location Windows: Navigate to C:\Users\Username\AppData\Roaming\groestlCoin\wallet.dat (or open windows explorer and enter %appdata%\Groestlcoin\wallet.dat)
Location Mac: Finder -> Go {Hold Option] -> Library -> groestlcoin -> wallet.dat (~/Library/Application Support/groestlcoin/wallet.dat)

WARNING:
While this branch has been extensively tested to be compatible with the existing Groestlcoin v2.1.0.6 network there is the possibility that we missed something. BACKUP YOUR GROESTLCOIN DATA DIRECTORY and wallet.dat because after you run v2.11.0 the old v2.1.0.6 version is no longer compatible with your on-disk data. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised v2.11.0 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. Because release v2.11.0 makes use of headers-first synchronization and parallel block download, the block files and databases are not backwards-compatible with older versions of Groestlcoin Core or other software:
• Blocks will be stored on disk out of order (in the order they are received), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this.
• The block index database will now hold headers for which no block is stored on disk, which earlier versions won’t support.

How to Upgrade?
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Groestlcoin-Qt (on Mac).
Linux users: Canonical name for .GroestlCoin in Linux is changed to use all lowercase: .groestlcoin. Please make a link as a solution: ln .GroestlCoin .groestlcoin and rename the GroestlCoin.conf to groestlcoin.conf.  And copy over groestlcoind/Groestlcoin-qt.

Download the Windows Wallet (64 bit) here: https://github.com/GroestlCoin/groestlcoin/releases/download/v2.11.0/groestlcoin_x64.msi
Download the Windows Wallet (32 bit) here: https://github.com/GroestlCoin/groestlcoin/releases/download/v2.11.0/groestlcoin_x86.msi
Download the MAC Wallet here: https://github.com/GroestlCoin/groestlcoin/releases/download/v2.11.0/Groestlcoin-Qt.dmg

Source code:
https://github.com/Groestlcoin/groestlcoin
Build instructions for Linux can be found here: https://github.com/GroestlCoin/groestlcoin/blob/master/doc/build-unix.md
Build instructions for OSX can be found here: https://github.com/GroestlCoin/groestlcoin/blob/master/doc/build-osx.md
Build instructions for Windows can be found here: https://github.com/GroestlCoin/groestlcoin/blob/master/doc/build-windows.md

1. Yes
2. Yes
3. Yes
4. Didn't test
5. Yes
6. Yes
7. Yes
8. 30 min
9. Yes
10. Yes
11. Yes

[themikeymen001]

Great one click paper wallet upload is coming soon. Stay tuned devs are really working hard on it.

[LTEX]

Since your algo is great with GPU's, are there any Dutch members here interested in some XFX 7950 3Gb Double cards? I have about 30 lying around doing nothing atm...

[jwinterm]

Any special trick to getting solo mining working with new release v2.11.0? I can't even get it working on local host computer using sgminer 5.1.1 released on 9 March or an older version of sph-sgminer 4.1. I just get this message:

Code:

[20:43:11] Pool 0 slow/down or URL or credentials invalid

But I'm pretty sure it was working before I updated client. Is there a special switch in sgminer for newer clients? Need a newer sgminer?

When I use debug mode on old sph-sgminer I get this output (debug mode on new sgminer causes it to immediately crash):

Code:

[20:46:07] Pushing sem post to thread 1
[20:46:07] Probing for an alive pool
[20:46:07] Testing Pool 0
[20:46:07] Probing for GBT support
[20:46:07] No GBT coinbase + append support found, using getwork protocol
[20:46:07] HTTP request failed: The requested URL returned error: 404 Not Found
[20:46:07] Succeeded delayed connect
[20:46:07] Socket closed waiting in recv_line
[20:46:07] Closing socket for stratum Pool 0
[20:46:07] Failed to parse a \n terminated string in recv_line
[20:46:07] Initiating stratum failed on Pool 0
[20:46:07] Suspending stratum on Pool 0
[20:46:07] Closing socket for stratum Pool 0
[20:46:07] FAILED to retrieve work from Pool 0
[20:46:07] Pool 0 slow/down or URL or credentials invalid
[20:46:07] Waiting on sem in miner thread
[20:46:07] Popping work from get queue to get work
[20:46:17] Waiting for work to be available from pools.

Also, I changed GroestlCoin.conf to groestlcoin.conf, even though I'm not sure that really matters on windows.

Also, also, I'm able to make an rpc call to 127.0.0.1:1441 successfully using curl, so the wallet conf seems setup correctly...

[themikeymen001]

DMD is doing really bad. Wow

[jackielove4u]

The getwork protocol has been removed from Groestlcoin core since it was a inefficient way to mine (due to the speed of FPGA devices).
The old protocol in Groestlcoind or -QT was limited to about 5GH before running into bottlenecks. Groestlcoind could not serve work fast enough for the FPGA's.

In order to solo mine with the new core:
1. You need an updated sgminer with support for an address parameter, so it can mine through getblocktemplate (GBT).  Cgminer 4.2.0 has already support for adress parameter. The updated sgminer can be released soon (depends on how many people really want to solo mine).
2. Another way that would work is that you need a stratum proxy (such as https://github.com/slush0/stratum-mining-proxy or similar) to convert the getwork to stratum.
3. You could also download a stratum server (such as https://github.com/slush0/stratum or similar) and have that talk to your groestlcoind and then have sgminer talk to that.

It does not matter if you change GroestlCoin.conf to groestlcoin.conf because it is the same on Windows (it only matters for Linux).

Any special trick to getting solo mining working with new release v2.11.0? I can't even get it working on local host computer using sgminer 5.1.1 released on 9 March or an older version of sph-sgminer 4.1. I just get this message:

Code:

[20:43:11] Pool 0 slow/down or URL or credentials invalid

But I'm pretty sure it was working before I updated client. Is there a special switch in sgminer for newer clients? Need a newer sgminer?

When I use debug mode on old sph-sgminer I get this output (debug mode on new sgminer causes it to immediately crash):

Code:

[20:46:07] Pushing sem post to thread 1
[20:46:07] Probing for an alive pool
[20:46:07] Testing Pool 0
[20:46:07] Probing for GBT support
[20:46:07] No GBT coinbase + append support found, using getwork protocol
[20:46:07] HTTP request failed: The requested URL returned error: 404 Not Found
[20:46:07] Succeeded delayed connect
[20:46:07] Socket closed waiting in recv_line
[20:46:07] Closing socket for stratum Pool 0
[20:46:07] Failed to parse a \n terminated string in recv_line
[20:46:07] Initiating stratum failed on Pool 0
[20:46:07] Suspending stratum on Pool 0
[20:46:07] Closing socket for stratum Pool 0
[20:46:07] FAILED to retrieve work from Pool 0
[20:46:07] Pool 0 slow/down or URL or credentials invalid
[20:46:07] Waiting on sem in miner thread
[20:46:07] Popping work from get queue to get work
[20:46:17] Waiting for work to be available from pools.

Also, I changed GroestlCoin.conf to groestlcoin.conf, even though I'm not sure that really matters on windows.

Also, also, I'm able to make an rpc call to 127.0.0.1:1441 successfully using curl, so the wallet conf seems setup correctly...

[themikeymen001]

The getwork protocol has been removed from Groestlcoin core since it was a inefficient way to mine (due to the speed of FPGA devices).
The old protocol in Groestlcoind or -QT was limited to about 5GH before running into bottlenecks. Groestlcoind could not serve work fast enough for the FPGA's.

In order to solo mine with the new core:
1. You need an updated sgminer with support for an address parameter, so it can mine through getblocktemplate (GBT).  Cgminer 4.2.0 has already support for adress parameter. The updated sgminer can be released soon (depends on how many people really want to solo mine).
2. Another way that would work is that you need a stratum proxy (such as https://github.com/slush0/stratum-mining-proxy or similar) to convert the getwork to stratum.
3. You could also download a stratum server (such as https://github.com/slush0/stratum or similar) and have that talk to your groestlcoind and then have sgminer talk to that.

It does not matter if you change GroestlCoin.conf to groestlcoin.conf because it is the same on Windows (it only matters for Linux).

Any special trick to getting solo mining working with new release v2.11.0? I can't even get it working on local host computer using sgminer 5.1.1 released on 9 March or an older version of sph-sgminer 4.1. I just get this message:

Code:

[20:43:11] Pool 0 slow/down or URL or credentials invalid

But I'm pretty sure it was working before I updated client. Is there a special switch in sgminer for newer clients? Need a newer sgminer?

When I use debug mode on old sph-sgminer I get this output (debug mode on new sgminer causes it to immediately crash):

Code:

[20:46:07] Pushing sem post to thread 1
[20:46:07] Probing for an alive pool
[20:46:07] Testing Pool 0
[20:46:07] Probing for GBT support
[20:46:07] No GBT coinbase + append support found, using getwork protocol
[20:46:07] HTTP request failed: The requested URL returned error: 404 Not Found
[20:46:07] Succeeded delayed connect
[20:46:07] Socket closed waiting in recv_line
[20:46:07] Closing socket for stratum Pool 0
[20:46:07] Failed to parse a \n terminated string in recv_line
[20:46:07] Initiating stratum failed on Pool 0
[20:46:07] Suspending stratum on Pool 0
[20:46:07] Closing socket for stratum Pool 0
[20:46:07] FAILED to retrieve work from Pool 0
[20:46:07] Pool 0 slow/down or URL or credentials invalid
[20:46:07] Waiting on sem in miner thread
[20:46:07] Popping work from get queue to get work
[20:46:17] Waiting for work to be available from pools.

Also, I changed GroestlCoin.conf to groestlcoin.conf, even though I'm not sure that really matters on windows.

Also, also, I'm able to make an rpc call to 127.0.0.1:1441 successfully using curl, so the wallet conf seems setup correctly...

Exactly what he said.

[jwinterm]

The getwork protocol has been removed from Groestlcoin core since it was a inefficient way to mine (due to the speed of FPGA devices).
The old protocol in Groestlcoind or -QT was limited to about 5GH before running into bottlenecks. Groestlcoind could not serve work fast enough for the FPGA's.

...

Maybe you guys should change the tag line to "The New Home of the FPGA Miners"

Why is network hashrate so low if there are superfast FPGAs mining? I mean, I can get like 10-20% of the network with a few video cards...

[themikeymen001]

big markets for GRS

Poker--> Extremily high volume, game with by far most revenue and money transferring in the world billion dollar business
Football--) (soccer betting) trillion dollar business
games--> paying games, and in-game payments with grs. A billion dollar business
credit/lending--> Don't even know how many zeros to write. Insane big market.

[btccashacc]

Im waiting GRC under 2000sat again
any chance price will be down again ?
im waiting cheap price and never get it

[themikeymen001]

wait for the new releases, GRS is going easy above 2.000 easy peazy. I personally think around 5000 satoshi is realistic if it all goes as it should.

[jackielove4u]

Maybe you guys should change the tag line to "The New Home of the FPGA Miners"

Why is network hashrate so low if there are superfast FPGAs mining? I mean, I can get like 10-20% of the network with a few video cards...

Its a myth that any PoW coin are FPGA/ASIC resistant. In fact for 99% PoW coins there are already working FPGA implementations. We are still the new home of GPU miners, the FPGA farmers only mine GRS when we ask them to do so.

Simple, because dumpers stopped dumping GRS. The FPGA farmers are a necessary evil to protect the GRS price. Everytime we see miners who dump high ammount of GRS, we ask the FPGA farmers to help us a hand (and bumping the network hashrate to 1 GH/s) so the dumpers don't get many coins to dump. The FPGA farmers won't dump any GRS because they believe in our development as i keep them updated often on what is coming. GRS is one of the few coins being hodled by FPGA farmers, most of the altcoins are being dumped by them (and thus decreasing the price of that altcoin).

[themikeymen001]

Future looking great. Can't wait for new updates and releases...

[jwinterm]

Its a myth that any PoW coin are FPGA/ASIC resistant. In fact for 99% PoW coins there are already working FPGA implementations.

...

I'd disagree in that some PoW algos are certainly more FPGA resistant than others. For instance, the cryptonight algo used by monero and others uses a 2 MB scratch pad and AES encryption. Afaik these values and ciphers were chosen because modern cpus have a 2 MB cache and a built-in ASIC for doing AES; this is why cryptonight is one of the only algos where cpus are remotely competitive with gpus in terms of hash/watt. I don't think there's any FPGA out there that's going to compete with an newish i7 or 750ti in terms of hash/watt, but I could be wrong.

As far as 99% of PoW already having working FPGA implementations, I guess this is probably true since probably 99% (or at least 90%?) of coins are sha or scrypt based.

[jwinterm]

Its a myth that any PoW coin are FPGA/ASIC resistant. In fact for 99% PoW coins there are already working FPGA implementations.

...

I'd disagree in that some PoW algos are certainly more FPGA resistant than others. For instance, the cryptonight algo used by monero and others uses a 2 MB scratch pad and AES encryption. Afaik these values and ciphers were chosen because modern cpus have a 2 MB cache and a built-in ASIC for doing AES; this is why cryptonight is one of the only algos where cpus are remotely competitive with gpus in terms of hash/watt. I don't think there's any FPGA out there that's going to compete with an newish i7 or 750ti in terms of hash/watt, but I could be wrong.

As far as 99% of PoW already having working FPGA implementations, I guess this is probably true since probably 99% (or at least 90%?) of coins are sha or scrypt based.

Most coins aren't SHA or scrypt based, and FPGA would KILL an i7/750Ti on hash/watt on CryptoNight - just not in hash/$.

I think if you include all "dead" coins, then most would be sha or scrypt, or if you define most by marketcap, then btc+ltc+doge dwarfs market cap of all other PoW coins combined (90+%), even with ethereum release.

What do you mean not in hash/$? Only really expensive FPGA would be able to mine effectively?

[themikeymen001]

Its a myth that any PoW coin are FPGA/ASIC resistant. In fact for 99% PoW coins there are already working FPGA implementations.

...

I'd disagree in that some PoW algos are certainly more FPGA resistant than others. For instance, the cryptonight algo used by monero and others uses a 2 MB scratch pad and AES encryption. Afaik these values and ciphers were chosen because modern cpus have a 2 MB cache and a built-in ASIC for doing AES; this is why cryptonight is one of the only algos where cpus are remotely competitive with gpus in terms of hash/watt. I don't think there's any FPGA out there that's going to compete with an newish i7 or 750ti in terms of hash/watt, but I could be wrong.

As far as 99% of PoW already having working FPGA implementations, I guess this is probably true since probably 99% (or at least 90%?) of coins are sha or scrypt based.

Most coins aren't SHA or scrypt based, and FPGA would KILL an i7/750Ti on hash/watt on CryptoNight - just not in hash/$.

I think if you include all "dead" coins, then most would be sha or scrypt, or if you define most by marketcap, then btc+ltc+doge dwarfs market cap of all other PoW coins combined (90+%), even with ethereum release.

What do you mean not in hash/$? Only really expensive FPGA would be able to mine effectively?

Likely. With a massive one, I could fit the scratchpad in flip-flops, perhaps. Suddenly, memory access is REALLY fucking fast. But it'd be many thousands of USD for one - not worth it at all.

For now not but for later; yes.

[themikeymen001]

To summarize the latest feedback:

1 Technically speaking one of the best coins and devs in the world

2 Logo and name don't work

advice: Change name and logo asap. Think more about what people really want...


What do you think...?

[themikeymen001]

some easy to pronounce new names:

Smash (Coin)     Coincoin   smoothcoin  timecoin   Napoleoncoin zoef(coin) platocoin     vincicoin    steamcoin    cocoin       cococoin
Bam    (coin)     dingcoin    nanocoin     speedcoin Darwincoin    gocoin      mozartcoin  ploughcoin pressurecoin crusecoin  ocoin
fewcoin fiewcoin slickcoin lissomecoin daltoncoin deltacoin

(names below are based on most beautiful words in English language)

lithe
Comely
conflate
demure
dulcet
elision
elixir
felicity
lilt
offing
seraglio

http://www.alphadictionary.com/articles/100_most_beautiful_words.html

http://blog.topplaza.com/2011/05/117-most-beautiful-words-in-the-english-language/

[themikeymen001]

elixir

Miraculous, magical, and maybe a little mysterious, an elixir is a sweet substance or solution that cures the problem at hand.

This one is absolutely my favorite:) also in every list of beautiful words...

with a strong (red) logo we are ready for a brand new start.