Topic: GoldCoin™ (GLC) Thread - The Gold Standard of Digital Currency [OFFICIAL THREAD] - page 7. (Read 310068 times)

Whats happed with GLD.(gold coin). No such activity from Dev. Wallet broken on cryptopia, from long long time. Cryptopia says, no response from gld dev regarding wallet, to investigate and to rectify, thus bring the cryptopia gld wallet in right mode. Are gld dev loosing interest in his own coin?
waiting for reply....it will be helpfull to all gld  coin community.

windows 7/64bit, amd quad core
i reboot every evening after i get home from work, when i have time on the weekend i'll give 0.14.4 another attempt.

i doubt reboots will solve it however, since the older code works fine.

Can you please provide your machine type, operating system details, etc. In the meantime, you might also try rebooting your machine.

0.14.4 fails on startup with a dialog box saying "unable to start http server" or something similar.

2018-10-20 01:00:40 Goldcoin version v0.14.4.0-8eb798e
2018-10-20 01:00:40 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-10-20 01:00:41 GUI: libpng warning: iCCP: known incorrect sRGB profile
2018-10-20 01:00:41 Validating signatures for all blocks.
2018-10-20 01:00:41 GUI: "registerShutdownBlockReason: Successfully registered: GoldCoin Core didn't yet exit safely..."
2018-10-20 01:00:41 Default data directory C:\Users\ken\AppData\Roaming\GoldCoin (GLD)
2018-10-20 01:00:41 Using data directory C:\Users\ken\AppData\Roaming\GoldCoin_GLD_
2018-10-20 01:00:41 Using config file C:\Users\ken\AppData\Roaming\GoldCoin_GLD_\goldcoin.conf
2018-10-20 01:00:41 Using at most 15 automatic connections (2048 file descriptors available)
2018-10-20 01:00:41 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2018-10-20 01:00:41 Using 4 threads for script verification
2018-10-20 01:00:41 scheduler thread start
2018-10-20 01:00:43 libevent: getaddrinfo: no address associated with nodename
2018-10-20 01:00:43 Binding RPC on address :: port 8122 failed.
2018-10-20 01:00:43 Binding RPC on address 0.0.0.0 port 8122 failed.
2018-10-20 01:00:43 Unable to bind any endpoint for RPC server
2018-10-20 01:00:52 scheduler thread interrupt
2018-10-20 01:00:52 Shutdown: In progress...
2018-10-20 01:00:52 Shutdown: done
2018-10-20 01:02:12 

reverting back to 0.14.3 works fine.

2018-10-20 01:04:29 Goldcoin version v0.14.3.0-7a76ae6
2018-10-20 01:04:29 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-10-20 01:04:29 GUI: libpng warning: iCCP: known incorrect sRGB profile
2018-10-20 01:04:29 Validating signatures for all blocks.
2018-10-20 01:04:29 GUI: "registerShutdownBlockReason: Successfully registered: GoldCoin Core didn't yet exit safely..."
2018-10-20 01:04:29 Default data directory C:\Users\ken\AppData\Roaming\GoldCoin (GLD)
2018-10-20 01:04:29 Using data directory C:\Users\ken\AppData\Roaming\GoldCoin_GLD_
2018-10-20 01:04:29 Using config file C:\Users\ken\AppData\Roaming\GoldCoin_GLD_\goldcoin.conf
2018-10-20 01:04:29 Using at most 15 automatic connections (2048 file descriptors available)
2018-10-20 01:04:29 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2018-10-20 01:04:29 Using 4 threads for script verification
2018-10-20 01:04:29 scheduler thread start
2018-10-20 01:04:32 libevent: getaddrinfo: no address associated with nodename
2018-10-20 01:04:32 Binding RPC on address :: port 8122 failed.
2018-10-20 01:04:32 HTTP: creating work queue of depth 16
2018-10-20 01:04:32 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2018-10-20 01:04:32 HTTP: starting 4 worker threads
2018-10-20 01:04:32 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-10-20 01:04:32 Using wallet wallet.dat
2018-10-20 01:04:32 init message: Verifying wallet...
2018-10-20 01:04:32 CDBEnv::Open: LogDir=C:\Users\ken\AppData\Roaming\GoldCoin_GLD_\database ErrorFile=C:\Users\ken\AppData\Roaming\GoldCoin_GLD_\db.log
2018-10-20 01:04:32 Bound to [::]:8121
2018-10-20 01:04:32 Bound to 0.0.0.0:8121
2018-10-20 01:04:32 Cache configuration:
2018-10-20 01:04:32 * Using 2.0MiB for block index database
2018-10-20 01:04:32 * Using 8.0MiB for chain state database
2018-10-20 01:04:32 * Using 440.0MiB for in-memory UTXO set (plus up to 4.8MiB of unused mempool space)
2018-10-20 01:04:32 init message: Loading block index...

Goldcoin p2pool nodes:

For USA - http://p2p-spb.xyz:8124/static/        -  Chicago

For EU - http://p2p-spb.xyz:8124/static/
          - http://p2p-south.xyz:8124/static/

Goldcoin Core v0.14.4 has been released which includes a very important security fix for a DoS vulnerability!

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).

Download links: https://www.goldcoin.org/downloads.html

All users are advised to upgrade as soon as possible. Submit any issues you encounter here and one of the Goldcoin developers will assist you.

This project is very much in the interest of people because it can be said to be trusted in terms of seeing it and the price of a coin is very expensive so it is very profitable.

Our orphans are from the difficulty going down.  This is normal orphan spike for GoldCoin due to the GoldenRiver and 51% defense systems.

Why are there so many orphans suddenly ? What is happening ?

https://chainz.cryptoid.info/gld/orphans.dws

Hi Guys,

First of all Microguy, Akuma and the team, I do apologize for voicing so much of my anger. I was on the brink of losing a lot of money since I have it all invested in GLD.

Thank you for the update, but are we very certain this works? Lets get all kinks out ASAP. So we do not see another fork down the road. For this to be a mainstream currency, it needs to be at a point where we are not forking this all the time. Looking at the latest update, I am still seeing a butt load of orphans, both in the pools, and in solo mining. I have around 4mhs on this right now, and I see the debug log queing blocks for the appropriate timestamp even though I got blocks found.

Any ideas?

Certainly my hope is also the same as yours,
and I really hope that in the remaining time Goldcoin can increase

I think Goldcoin back stable with price $0.03. I hope he will skyrocket as at mid year and survives on high prices, it would be very nice, but over all is pretty good.

The Goldcoin wallet has been returned to service at Bittrex.

The Goldcoin developers are about to turn on check pointing. If you have not upgraded, you must do so immediately.

If you know anyone that hasn't upgraded, you should reach out to them and warn them to upgrade.

I have revised the URL per your request. Thank you for updating today.

I upgraded daemon on my p2pool nodes to v0.14.3:
http://crypto.mine.nu:8124
http://siberia.mine.nu:8124

Please change on OP URL "P2Pool (14.3)" from http://msk.p2pool.site:8124/static/ to http://p2pool.top/scanner/gld/

http://p2pool.top/scanner/gld/ - is the p2pool node scanner. Therefore, there is no need to specify each node individually

The OP of this thread has just been updated with the latest list of pools including which ones have upgraded.

The current release with ACPD is 0.14.3

what is the valid release ?

14.x  ?

Yesterday, The Goldcoin Team released a mandatory update for the Goldcoin Client.

Unfortunately, we have been unable to reach Hash-to-Coins and they have not updated their wallet as requested. Do not mine GLD on this pool. If you mine this pool, you risk wasting your hashpower since their chain might become forked from the network.

We recommend that you switch immediately to: https://gld.thecoin.pw/

Once Hash-to-Coins has updated their wallet it will be safe to return. But until then, anyone mining GLD on this pool is subject to losing all their Goldcoins.