Pages:
Author

Topic: [ANN][GCH] Galaxy Cash, PoW, PoS, Multialgo, Masternodes, No Premine - page 26. (Read 22720 times)

member
Activity: 195
Merit: 10
Ok.I can solved this ploblem. I delete all node in GalaxyCash.conf except addnode=193.124.0.135  .
But i lost 3000+ gch . Shocked
You can lose coins only in one case, if you delete wallet.dat.
Coins themselves do not disappear from network. This is not a Hogwarts network.
Your wallet address, from which coins were lost?
member
Activity: 195
Merit: 10
We need a stress test of the new version, with big mining powers on all algorithms at same time to make sure that everything is fine.

in my wallet show 12503 block. on web show 12494 block  Huh Huh
You update wallet to 1.1.1.5?
Old version wallets not compatible with 1.1.1.5, difficulty retargeting correction.
full member
Activity: 417
Merit: 105
Nice, the new update has made things a lot more stable for me now.  Hopefully we will continue to see good updates you from dev!  Looking forward to see what your plans for GalaxyCash are.
full member
Activity: 196
Merit: 100
in my wallet show 12503 block. on web show 12494 block  Huh Huh

May be your wallet not connected to network?
full member
Activity: 196
Merit: 100
Low diff - nice to solo mine at X12  Smiley
sr. member
Activity: 479
Merit: 253
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.

You know when you point your miner to a stratum address....what would i put in place of a stratum address if i am trying to solo mine?
full member
Activity: 252
Merit: 100
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.
sr. member
Activity: 479
Merit: 253
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
member
Activity: 195
Merit: 10
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!
member
Activity: 195
Merit: 10
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?
full member
Activity: 266
Merit: 100
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.
newbie
Activity: 56
Merit: 0
dev- building galaxycashd still produces errors, and then when finally built on first launch you get

galaxycashd
Segmentation fault (core dumped)
member
Activity: 160
Merit: 18
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?Huh X11??
I helped the forum here... this kind of problem is not related of algorithm.
https://bitcointalksearch.org/topic/m.25998300
member
Activity: 154
Merit: 10
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.
member
Activity: 160
Merit: 18
It's asic protection  Cheesy, 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
member
Activity: 195
Merit: 10
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  Cheesy, 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?
member
Activity: 160
Merit: 18
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.

member
Activity: 324
Merit: 10
windows solo, use cmd
-server -algo=x12 or change algo what you want
member
Activity: 90
Merit: 10
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.
member
Activity: 160
Merit: 18
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://bitcointalksearch.org/topic/m.25998300

The wallet is still unstable!
Pages:
Jump to: