Topic: [ANN][GCH] Galaxy Cash, PoW, PoS, Multialgo, Masternodes, No Premine - page 27. (Read 22741 times)
December 10, 2017, 03:02:23 AM
after a day of stable work, another fork (((developer why this happens? it needs to be corrected, so no exchange will support your coin
December 10, 2017, 02:13:27 AM
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.
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
December 10, 2017, 01:52:08 AM
so , any exchanges
December 10, 2017, 01:17:48 AM
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.
To mine X12 with AMD cards on Ubuntu? Can somebody point me in the right direction?
Thanks in advance.
December 09, 2017, 08:04:23 PM
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
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
Quote
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
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:
Quote
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:
Quote
https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Windows.x86.zip
If 64 bits download:
Quote
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
December 09, 2017, 02:34:35 AM
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
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
Quote
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
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:
Quote
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:
Quote
https://github.com/galaxycash/galaxycash/releases/download/1.1.1.4/Windows.x86.zip
If 64 bits download:
Quote
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
December 09, 2017, 01:49:38 AM
Hey dev,
I have been mining this for hours now on X11 with 125 mh/s and I am on the correct block number, but I still haven't find any blocks and the difficulty says always the same number, even though the network hashrate is changing, difficulty stays the same.
Am I doing something wrong here that I am not actually mining correctly or what am I missing? How come i haven't found any blocks?
Thanks
EDIT: was using a miner program not properly coded for mining x11, works now.
I have been mining this for hours now on X11 with 125 mh/s and I am on the correct block number, but I still haven't find any blocks and the difficulty says always the same number, even though the network hashrate is changing, difficulty stays the same.
Am I doing something wrong here that I am not actually mining correctly or what am I missing? How come i haven't found any blocks?
Thanks
EDIT: was using a miner program not properly coded for mining x11, works now.
Damn dude you must be over 50% of the X11 hash. Be sure to check your blockheight a few times a day to ensure you're still synced
December 08, 2017, 09:46:43 PM
Hey dev,
I have been mining this for hours now on X11 with 125 mh/s and I am on the correct block number, but I still haven't find any blocks and the difficulty says always the same number, even though the network hashrate is changing, difficulty stays the same.
Am I doing something wrong here that I am not actually mining correctly or what am I missing? How come i haven't found any blocks?
Thanks
EDIT: was using a miner program not properly coded for mining x11, works now.
I have been mining this for hours now on X11 with 125 mh/s and I am on the correct block number, but I still haven't find any blocks and the difficulty says always the same number, even though the network hashrate is changing, difficulty stays the same.
Am I doing something wrong here that I am not actually mining correctly or what am I missing? How come i haven't found any blocks?
Thanks
EDIT: was using a miner program not properly coded for mining x11, works now.
December 08, 2017, 05:49:42 PM
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
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
Quote
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
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:
Quote
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:
Quote
If 64 bits download:
Quote
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!
December 08, 2017, 04:57:08 PM
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
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
December 08, 2017, 04:48:58 PM
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
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á
December 08, 2017, 04:28:55 PM
now it turned out. it's not normal that the chain itself is rejected ...
December 08, 2017, 04:25:37 PM
what kind of nonsense. chain of blocks shows 100 more than there is 
Can you please clarify the problem you are having? My wallet block height is 9346, the exact same as the block explorer. I know some people are having trouble staying synced, but it looks like lots of people are able to do so if they follow the instructions carefully: https://bitcointalksearch.org/topic/m.25978707
If those instructions are too complicated for you, you may want to look for a different currency with slightly less technical issues. I'm sticking to this one because, while there are some problems with forking, anyone who is careful can stay synced. Also, the dev is very active so I think he will work the problem out in the end.
December 08, 2017, 04:07:32 PM
what kind of nonsense. chain of blocks shows 100 more than there is
Can you please clarify the problem you are having? My wallet block height is 9346, the exact same as the block explorer. I know some people are having trouble staying synced, but it looks like lots of people are able to do so if they follow the instructions carefully: https://bitcointalksearch.org/topic/m.25978707
If those instructions are too complicated for you, you may want to look for a different currency with slightly less technical issues. I'm sticking to this one because, while there are some problems with forking, anyone who is careful can stay synced. Also, the dev is very active so I think he will work the problem out in the end.
December 08, 2017, 04:02:29 PM
what kind of nonsense. chain of blocks shows 100 more than there is
December 08, 2017, 11:59:08 AM
@GalaxyCash,
Could you share with us the roadmap?
By the way if is not completed yet, just for us to know the next steps.
Are you thinking to implement the PoS method (Proof of Stake)?
Could you share with us the roadmap?
By the way if is not completed yet, just for us to know the next steps.
Are you thinking to implement the PoS method (Proof of Stake)?
December 08, 2017, 11:53:40 AM
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:
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
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
December 08, 2017, 10:39:52 AM
I will repeat to help make it clear:
1) MAKE SURE YOUR BLOCK HEIGHT IS THE SAME AS THE EXPLORER IF YOU ARE SOLO MINING
2) USE THE ADDNODES IN THE ANN TO SYNC WALLET
This has worked for me. If you don't do it, you could end up forking from the main chain.
1) MAKE SURE YOUR BLOCK HEIGHT IS THE SAME AS THE EXPLORER IF YOU ARE SOLO MINING
2) USE THE ADDNODES IN THE ANN TO SYNC WALLET
This has worked for me. If you don't do it, you could end up forking from the main chain.
Del all exept wallet and conf from c:\Users\*You*\AppData\Roaming\GalaxyCash\
Dowload blockchain from https://github.com/galaxycash/galaxycash/releases
Add node
addnode 178.46.63.50:1337 add
addnode 124.13.26.207:4603 add
addnode 5.189.152.63:7604 add
addnode 193.124.0.135:7604 add
Check block here https://193.124.0.135/
Follow these instructions if you are solo mining or trading this coin! Make sure you are on the right chain!
Huge potential here, but people need to stop mining on forked chains.
December 08, 2017, 10:00:42 AM
my wallet after some time of normal work goes into the fork. why? give the correct configuration file. Or is that not the case? and the latest version of the wallet is not synchronized beyond the 5000 block
I'm having a similar issue, can't sync beyond Block 5000. Seems like other people have synced though, so I don't know what's wrong.
Del all exept wallet and conf from c:\Users\*You*\AppData\Roaming\GalaxyCash\
Dowload blockchain from https://github.com/galaxycash/galaxycash/releases
Add node
addnode 178.46.63.50:1337 add
addnode 124.13.26.207:4603 add
addnode 5.189.152.63:7604 add
addnode 193.124.0.135:7604 add
Check block here https://193.124.0.135/
Instructions worked for me, thank you. I am able to stay synced for now, though I have a friend who still forks sometimes. How can we solve this problem permanently? Do we need more nodes?
December 08, 2017, 09:32:34 AM
who mining faster,
any pool
any pool
Jump to: