[ANN][GCH] Galaxy Cash, PoW, PoS, Multialgo, Masternodes, No Premine

[saLve88]

now it turned out. it's not normal that the chain itself is rejected ...

saLve88,

I did it today and works fine (I knew the GCH today).
Go in your wallet home and create the file GalaxyCash.conf:

Code:

listen=1
server=1
daemon=1
rpckeepalive=1
addnode=193.124.0.135

Drop the file peers.dat and restart your wallet. Just waiting 5 minutes and voilá

peers.dat appears every time after closing the wallet. and conf.file I have created
While like works. but for how long?!?!?

rpcuser=saLve88
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=4604
port=7604
gen=1
server=1
daemon=1
listen=1
addnode=193.124.0.135
addnode=178.46.63.50:1337
addnode=124.13.26.207:4603
addnode=5.189.152.63:7604
addnode=193.124.0.135:7604

Let's do it step-by-step. I'm supposing you are using Windows.

If you ARE SURE YOUR WALLET IS ZERO regarding the GCH, delete ALL FILES inside the folder.
If you have balance, save the WALLET.DAT in another folder and delete all files.

Windows Folder

C:\Users\YOUR_USER\AppData\Roaming\GalaxyCash

Now, create the file GalaxyCash.conf exactly like that:
PS: note that I'm using the algo X13.

Code:

rpcuser=saLve88
rpcpassword=x
port=17604
rpcport=14064

listen=1
server=1
daemon=1
gen=1
genproclimit=-1
keypool=200
maxconnections=20
rpcconnect=127.0.0.1
rpcallowip=127.0.0.1
rpckeepalive=1
rpcthreads=8

algo=x13

addnode=193.124.0.135
addnode=85.11.137.70:7604

From now, download the bootstrap, unzip it and move all content to your folder:

https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Blockchain.08.12.2017.zip

Check if your Windows is 32bits or 64bits.
Go to Control Panel > All Control Panel Items > System

A new window will be opened. Find the item "System Type" to know your version.
The new wallet version was uploaded yesterday in GitHub

If 32 bits download:

 https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Windows.x86.zip

If 64 bits download:

 https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Windows.x64.zip

Just uncompress the ZIP and open the exec galaxycash-qt.exe
Maybe your Windows will ask if you want to allow the galaxycash-qt.exe to access the Internet: say YES

-----------------------
Open the wallet and wait some minutes. Make sure your antivirus is not blocking the connection for the wallet.
-----------------------
After all steps are done, if you have balance in your OLD WALLET (the backup copied on the beginning of this guide), close your wallet for completed and replace the WALLET.DAT.
-----------------------

Let me know if you are done!

Yes, I did it that way) the night passed successfully without forks. I mine from x12

And yes, thanks for taking the time to explain in detail

[kidshell]

now it turned out. it's not normal that the chain itself is rejected ...

saLve88,

I did it today and works fine (I knew the GCH today).
Go in your wallet home and create the file GalaxyCash.conf:

Code:

listen=1
server=1
daemon=1
rpckeepalive=1
addnode=193.124.0.135

Drop the file peers.dat and restart your wallet. Just waiting 5 minutes and voilá

peers.dat appears every time after closing the wallet. and conf.file I have created
While like works. but for how long?!?!?

rpcuser=saLve88
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=4604
port=7604
gen=1
server=1
daemon=1
listen=1
addnode=193.124.0.135
addnode=178.46.63.50:1337
addnode=124.13.26.207:4603
addnode=5.189.152.63:7604
addnode=193.124.0.135:7604

Let's do it step-by-step. I'm supposing you are using Windows.

If you ARE SURE YOUR WALLET IS ZERO regarding the GCH, delete ALL FILES inside the folder.
If you have balance, save the WALLET.DAT in another folder and delete all files.

Windows Folder

C:\Users\YOUR_USER\AppData\Roaming\GalaxyCash

Now, create the file GalaxyCash.conf exactly like that:
PS: note that I'm using the algo X13.

Code:

rpcuser=saLve88
rpcpassword=x
port=17604
rpcport=14064

listen=1
server=1
daemon=1
gen=1
genproclimit=-1
keypool=200
maxconnections=20
rpcconnect=127.0.0.1
rpcallowip=127.0.0.1
rpckeepalive=1
rpcthreads=8

algo=x13

addnode=193.124.0.135
addnode=85.11.137.70:7604

From now, download the bootstrap, unzip it and move all content to your folder:

https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Blockchain.08.12.2017.zip

Check if your Windows is 32bits or 64bits.
Go to Control Panel > All Control Panel Items > System

A new window will be opened. Find the item "System Type" to know your version.
The new wallet version was uploaded yesterday in GitHub

If 32 bits download:

 https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Windows.x86.zip

If 64 bits download:

 https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Windows.x64.zip

Just uncompress the ZIP and open the exec galaxycash-qt.exe
Maybe your Windows will ask if you want to allow the galaxycash-qt.exe to access the Internet: say YES

-----------------------
Open the wallet and wait some minutes. Make sure your antivirus is not blocking the connection for the wallet.
-----------------------
After all steps are done, if you have balance in your OLD WALLET (the backup copied on the beginning of this guide), close your wallet for completed and replace the WALLET.DAT.
-----------------------

Let me know if you are done!

Yes, I did it that way) the night passed successfully without forks. I mine from x12

And yes, thanks for taking the time to explain in detail

Niiiiice

[ArcticParadise]

Maybe it's too late and I'm drawing a blank but...

To mine X12 with AMD cards on Ubuntu? Can somebody point me in the right direction?

Thanks in advance.

[bad name]

so , any exchanges

[saLve88]

Maybe it's too late and I'm drawing a blank but...

To mine X12 with AMD cards on Ubuntu? Can somebody point me in the right direction?

Thanks in advance.

my amd does not work on x 12 HW HW HW

[saLve88]

after a day of stable work, another fork (((developer why this happens? it needs to be corrected, so no exchange will support your coin

[kidshell]

I can't open wallet. It show "Microsoft  Visual C++ Runtime  liberry
Runtime error!
This application has requested the runtime to terminate it in  an unusual way.
Please contact the application's support team for more information."

Hi Sonosuka,

Try do what I wrote here:
   https://bitcointalk.org/index.php?topic=2424587.msg25998300#msg25998300

The wallet is still unstable!

[bloodxia]

maybe has some bug.
I use asic miner,x13 algo.
>95% has error,reject.
I don't know why.
Maybe I put daemon to server and put a pool can solve the problem.

[bad name]

windows solo, use cmd
-server -algo=x12 or change algo what you want

[kidshell]

maybe has some bug.
I use asic miner,x13 algo.
>95% has error,reject.
I don't know why.
Maybe I put daemon to server and put a pool can solve the problem.

It's happening with me too.
I don't know why! I need to close, create a new wallet.dat and everything backs to work again.
After 45 mining with ASIC, the wallet stop to sync again.

[GalaxyCash]

maybe has some bug.
I use asic miner,x13 algo.
>95% has error,reject.
I don't know why.
Maybe I put daemon to server and put a pool can solve the problem.

It's asic protection  , sorry for joke, comming big update, must solve all problems associated with mining. I working on rewrite checkpoint system for hardness sync.
What version of client are you using?

[kidshell]

It's asic protection  , sorry for joke, comming big update, must solve all problems associated with mining. I working on rewrite checkpoint system for hardness sync.
What version of client are you using?

I'm using 1.1.1.4
Is there any new wallet updated?

I sent you a PM for these days ago... feel free to call me

Jaime

[johntwo]

Those of you with rejected shares: make sure you are setting the right algo in the .conf file.  The client will not automatically switch algorithms, it has to be looking for the right algorithm.  This alone may not solve the problem if there are other issues I am unaware of, but you should at least have the algo right.  An X11 miner should only be mining if algo=x11 is set in the .conf file.

[kidshell]

Those of you with rejected shares: make sure you are setting the right algo in the .conf file.  The client will not automatically switch algorithms, it has to be looking for the right algorithm.  This alone may not solve the problem if there are other issues I am unaware of, but you should at least have the algo right.  An X11 miner should only be mining if algo=x11 is set in the .conf file.

ahnnn? X11??
I helped the forum here... this kind of problem is not related of algorithm.
https://bitcointalk.org/index.php?topic=2424587.msg25998300#msg25998300

[The SHAman]

dev- building galaxycashd still produces errors, and then when finally built on first launch you get

galaxycashd
Segmentation fault (core dumped)

[redsun17]

dev- building galaxycashd still produces errors, and then when finally built on first launch you get

galaxycashd
Segmentation fault (core dumped)

Is this preventing you from launching a pool for the coin?  To be honest, it might be best to hold off on a pool until the stability improves and forking stops.  Until then, solo mining is probably the best strategy.

[GalaxyCash]

Comining update 1.1.1.5, stop mining.

dev- building galaxycashd still produces errors, and then when finally built on first launch you get

galaxycashd
Segmentation fault (core dumped)

on what system you compile daemon? linux? windows?

[GalaxyCash]

Version 1.1.1.5 released

- Hard checkpoint system for mining.
- Problem with synchronize without bootstrap from scratch - resolved (before
 synchronization stoping after 5042 block - first multialgo block).
- In value "difficulty" of getinfo rpc command result, stores summary difficulty of all algorithms.
- Minor changes

For update not need remove data from old client.
Wallets on github: https://github.com/galaxycash/galaxycash/releases/latest
This update required!

[xxkaiwaxx]

Dev, how can I mine solo using the algo X13?
I have an ASIC and I would love to trust in your project mining start now...
I tried algo=x13 and didn't work

I created a conf - GalaxyCash.conf - as:

Code:

listen=1
server=1
daemon=1
gen=1
rpcuser=xxxxxx
rpcpassword=yyyyy
port=17604
rpcport=14064
rpckeepalive=1
rpcthreads=8
addnode=193.124.0.135

algo=x13

algo=x13 works fine for me.  What problem are you having?  Rejected blocks?

I don't know! I have created the conf before to open the wallet.
For now, I just closed the wallet and restart again and worked fine!
Reject means the wallet is not syncing, that was not my case.

Tks

Is this what to put into conf file....to solo mine with asic? I never solo mined before...but i want to try ^^" (x13 on baikal mini)

Or , a x13 pool would be nice

[TheKryptonian]

Dev, how can I mine solo using the algo X13?
I have an ASIC and I would love to trust in your project mining start now...
I tried algo=x13 and didn't work

I created a conf - GalaxyCash.conf - as:

Code:

listen=1
server=1
daemon=1
gen=1
rpcuser=xxxxxx
rpcpassword=yyyyy
port=17604
rpcport=14064
rpckeepalive=1
rpcthreads=8
addnode=193.124.0.135

algo=x13

algo=x13 works fine for me.  What problem are you having?  Rejected blocks?

I don't know! I have created the conf before to open the wallet.
For now, I just closed the wallet and restart again and worked fine!
Reject means the wallet is not syncing, that was not my case.

Tks

Is this what to put into conf file....to solo mine with asic? I never solo mined before...but i want to try ^^" (x13 on baikal mini)

Or , a x13 pool would be nice

You need to also specify "rpcallowip=127.0.0.1" (127.0.0.1 is the "local" address of any machine, it means you're allowing the local computer to mine on a client connected to the same computer.  If the miner is on a different computer and/or has a different IP address, you need to allow that ip address).

But yes, we could use some pools once this coin is confirmed stable.  My initial impression is that this is the most stable build so far, but I'm still testing it to make sure I don't fork when solo mining.

EDIT: Still haven't forked yet, under conditions where I usually forked before 1.1.1.5.  This is a very good sign, though it's still early and more people need to confirm.