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

[GalaxyCash]

Hi guys!
I installed a pool for a coin GCH, started the blake2s algorithm, try to connect for 30-60 minutes, whether there will be a payout, or I'm sitting alone ... like there are no errors, but Earnings is empty. I do not understand yet what's the matter.
Write impressions
http://212.47.227.141

Help me please...
In /var/stratum/stratum.log:

Code:

22:42:53: ERROR GalaxyCash Block decode failed
22:43:08: ERROR GalaxyCash Block decode failed
22:43:13: ERROR GalaxyCash Block decode failed
22:43:18: ERROR GalaxyCash Block decode failed
22:43:24: ERROR GalaxyCash Block decode failed
22:43:35: ERROR GalaxyCash Block decode failed
22:43:56: ERROR GalaxyCash Block decode failed
22:43:59: ERROR GalaxyCash Block decode failed

/var/stratum/reject.log:

Code:

2018-03-01 22:43:35: REJECTED GCH block 48625
2018-03-01 22:43:56: REJECTED GCH block 48625
2018-03-01 22:43:59: REJECTED GCH block 48625
2018-03-01 22:44:23: REJECTED GCH block 48626
2018-03-01 22:44:29: REJECTED GCH block 48626

/var/stratum/client.log:

Code:

bad mining address
unable to find the wallet for coinid 1486..

/home/useer/.galaxycash/debug.log:

Code:

ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
connect() to 193.124.0.135:7604 failed after select(): No route to host
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Misbehaving: 74.103.154.124:7604 (0 -> 1)
ProcessMessage(dseep, 116 bytes) FAILED
connect() to 45.117.82.106:7604 failed after select(): Connection refused
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep

You set algorithm in config? If you pool for Blake2s you need set blake2s algo in config - algo=blake2s

[Porter980]

Hi guys!
I installed a pool for a coin GCH, started the blake2s algorithm, try to connect for 30-60 minutes, whether there will be a payout, or I'm sitting alone ... like there are no errors, but Earnings is empty. I do not understand yet what's the matter.
Write impressions
http://212.47.227.141

Help me please...
In /var/stratum/stratum.log:

Code:

22:42:53: ERROR GalaxyCash Block decode failed
22:43:08: ERROR GalaxyCash Block decode failed
22:43:13: ERROR GalaxyCash Block decode failed
22:43:18: ERROR GalaxyCash Block decode failed
22:43:24: ERROR GalaxyCash Block decode failed
22:43:35: ERROR GalaxyCash Block decode failed
22:43:56: ERROR GalaxyCash Block decode failed
22:43:59: ERROR GalaxyCash Block decode failed

/var/stratum/reject.log:

Code:

2018-03-01 22:43:35: REJECTED GCH block 48625
2018-03-01 22:43:56: REJECTED GCH block 48625
2018-03-01 22:43:59: REJECTED GCH block 48625
2018-03-01 22:44:23: REJECTED GCH block 48626
2018-03-01 22:44:29: REJECTED GCH block 48626

/var/stratum/client.log:

Code:

bad mining address
unable to find the wallet for coinid 1486..

/home/useer/.galaxycash/debug.log:

Code:

ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
connect() to 193.124.0.135:7604 failed after select(): No route to host
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Misbehaving: 74.103.154.124:7604 (0 -> 1)
ProcessMessage(dseep, 116 bytes) FAILED
connect() to 45.117.82.106:7604 failed after select(): Connection refused
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlockHeader() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep

You set algorithm in config? If you pool for Blake2s you need set blake2s algo in config - algo=blake2s

That's exactly because I thought that somewhere you need to correctly register)))
But not correctly in the config wrote.
I wrote the algorithm = blake2c, but it was necessary algo .....)))
I checked getminingalgo, issues "x12" and looked where ...

1. Now there is nothing in the log /var/stratum/reject.log
2. /var/stratum/config/blake2s.log:

Code:

22:53:40: ERROR: rpc_do_call: 127.0.0.1:14860 500
22:53:40: ERROR GalaxyCash Block decode failed
22:53:40: *** REJECTED :( GalaxyCash block 48629 4 txs
22:53:45: GCH 48629 - diff 10.280692939 job 19 to 1/1/1 clients, hash 7952.122/$
2018-03-02 00:03:46 [198.13.34.110] , blake2s, bad json
00:03:46: N��Nversion
2018-03-02 01:35:17 [198.13.34.110] , blake2s, bad json
01:35:17: N��Nversion
2018-03-02 02:19:29 [198.13.34.110] , blake2s, bad json
02:19:29: N��Nversion
04:39:26: disconnecting from coind GCH

At this point, I registered in the config "algo=blake2s" and restarted the daemon

Code:

04:40:51: connecting to coind GCH
04:41:15: submit 109.187.0.97 (uid 1) 483, e3010000, 5a98aba4, 0b47a96c, 12.000
04:41:22: submit 109.187.0.97 (uid 1) 483, d3030000, 5a98aba4, 0a932d2b, 17.000
04:41:26: submit 109.187.0.97 (uid 1) 483, a1040000, 5a98aba4, 06452ff4, 5.000/
04:41:26: submit 109.187.0.97 (uid 1) 483, 7a040000, 5a98aba4, 08049b77, 397.00
04:41:29: submit 109.187.0.97 (uid 1) 483, 3c050000, 5a98aba4, 05bbe7be, 19.000
.
.
.
06:28:16: GCH 48849 - diff 17375.182089601 job 269 to 1/1/1 clients, hash 5789.437/1243763.981 in 0.4 ms
06:29:18: GCH 48849 - diff 17375.182089601 job 26a to 1/1/1 clients, hash 4536.672/1243763.981 in 0.1 ms
06:30:00: GCH 48849 - diff 17375.182089601 job 26b to 1/1/1 clients, hash 2903.470/1243763.981 in 0.1 ms
06:30:21: GCH 48849 - diff 17375.182089601 job 26c to 1/1/1 clients, hash 4069.976/1243763.981 in 0.2 ms
06:30:42: GCH 48849 - diff 17375.182089601 job 26d to 1/1/1 clients, hash 4129.581/1243763.981 in 0.2 ms
06:31:05: submit 109.187.0.97 (uid 1) 621, 90050000, 5a98c55e, 057827d3, 801.000/26.000
06:31:45: GCH 48849 - diff 17375.182089601 job 26e to 1/1/1 clients, hash 3686.825/1243763.981 in 0.5 ms
06:32:49: GCH 48849 - diff 17375.182089601 job 26f to 1/1/1 clients, hash 2446.759/1243763.981 in 0.3 ms
06:32:49: GCH 48850 - diff 17375.182089601 job 270 to 1/1/1 clients, hash 3538.759/1243763.981 in 0.0 ms
06:33:03: submit 109.187.0.97 (uid 1) 624, 3c030000, 5a98c5de, 01a2492e, 558.000/26.000
2018-03-02 06:51:04 [94.249.167.246] , blake2s, bad json - [b]here I disconnected[/b]

getinfo:

Code:

{
    "version": 2000003,
    "protocolversion": 90915,
    "walletversion": 60000,
    "balance": 0.11,
    "newmint": 0,
    "stake": 0,
    "blocks": 48869,
    "timeoffset": -3,
    "moneysupply": 2886550,
    "connections": 18,
    "proxy": "",
    [b]"ip": "0.0.0.0",[/b] - this is normal?
    "algorithm": "blake2s",
    "difficulty": {
        "proof-of-work": 16702.64627303,
        "proof-of-stake": 504365055,
        "proof-of-work-x12": 6.73270299,
        "proof-of-work-x13": 1716.65878997,
        "proof-of-work-x11": 15265.98525617,
        "proof-of-work-sha256d": 1892163.9617401,
        "proof-of-work-blake2s": 16702.64627303
    },
    "testnet": false,
    "keypoololdest": "2018-03-01 05:56:00 +0000",
    "keypoolsize": 101,
    "paytxfee": 1.0e-6,
    "mininput": 0,
    "errors": ""
}

/home/useer/.galaxycash/debug.log:

Code:

Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Misbehaving: 68.235.38.177:7604 (0 -> 1)
ProcessMessage(dseep, 116 bytes) FAILED
Prcessing command dseep
Misbehaving: 68.235.38.177:7604 (1 -> 2)
ProcessMessage(dseep, 116 bytes) FAILED
Misbehaving: 68.235.38.177:7604 (2 -> 3)
ProcessMessage(dseep, 116 bytes) FAILED
Misbehaving: 68.235.38.177:7604 (3 -> 4)
ProcessMessage(dseep, 116 bytes) FAILED
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
keypool reserve 7
keypool return 7
PoW Masternode payment to GS6YmcpPAmkvYsjz87QtYHjCSYiESvtqNJ
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
Prcessing command dseep
connect() to 193.124.0.135:7604 failed after select(): No route to host
Prcessing command dseep
connect() to 45.117.82.106:7604 failed after select(): Connection refused

But 2 hours "Last 50 earnings:" - empty
Documentation is not enough ... or I'm not looking there?
Where to look next?

[GalaxyCash]

You need set in yiimp coin config "RPC Type" as POS

[GalaxyCash]

Vote for protocol change on https://galaxycash.info, one vote everyday.
This will help to improve the current state of coin, prices for MN not final and will be discussed after vote.
New protocol will be launched after 100K block.
Results of voting will be take after week.

[jbmustaq]

Vote for protocol change on https://galaxycash.info, one vote everyday.
This will help to improve the current state of coin, prices for MN not final and will be discussed after vote.
New protocol will be launched after 100K block.
Results of voting will be take after week.

What will happen to the existing MN's also Is it possible if you can get the coin listed in graviex.net. It's free and does not need a listing fee. I could have done it but they require a direct contact with Dev for coin to be listed.

[GalaxyCash]

Vote for protocol change on https://galaxycash.info, one vote everyday.
This will help to improve the current state of coin, prices for MN not final and will be discussed after vote.
New protocol will be launched after 100K block.
Results of voting will be take after week.

What will happen to the existing MN's also Is it possible if you can get the coin listed in graviex.net. It's free and does not need a listing fee. I could have done it but they require a direct contact with Dev for coin to be listed.

No response from graviex.net

[Porter980]

Pool For Algoritm Blake2s GCH algorithm:
http://minerpool.online

Code:

Stratum: stratum+tcp://minerpool.online:5766
User: Your GalaxyCash Address
Password: c=GCH

Example:
stratum+tcp://minerpool.online:5766 -u YourGalaxyCashAddress -p c=GCH
For Claymore Dual:
-dpool stratum+tcp://minerpool.online:5766 -dwal YourGalaxyCashAddress -dpsw c=GCH -allpools 1

Payout every hour - Low fee

[GalaxyCash]

Vote for masternode price https://galaxycash.info, result today 11:30pm (UTC +03:00, MSK)
After voting release 2.1.0.0 Titan and creating new ANN thread for clearence.

[GalaxyCash]

Update released on github https://github.com/galaxycash/galaxycash/releases/latest

New protocol:

Type: PoW/PoS Hybrid with Masternodes
Ticker: GCH
Algorithm: X12, X11, X13, Sha256d, Blake2s
Difficulty retarget: Every block
Block time: 10 Minutes
PoW Block reward: 10 GCH (Halving every 210000 blocks)
PoS First Block: 100000
PoS Block reward: 10% per year
Masternode Price: 5000 GCH
Masternode PoW Reward: 17.5%, 65% superblock
Masternode PoS Reward: 12.5%, 50% superblock
Max supply: 30000000
Transaction Fee: 0.00000100, after 1st may 0.00500000
Coinbase maturity: 11 blocks
Minimum confirmations(PoW): 12 blocks
Minimum POS Age: 6 Hours
Maximum POS Age: No Max

New ANN Thread for clearence: https://bitcointalk.org/index.php?topic=3066064.new#new

[tientien1]

Our team will design an API call to a online database service provider and put the information of the IMEI collection as well as the tracking of it on blockchain.

[davidjoshua]

Since providing the IMEI numbers would mean that the supplier is likely to have the goods with them. The IMEI numbers can also be used to ensure that the goods are not stolen goods. As such, putting such critical information on blockchain would certainly help to stop scams as well as improving trading experience.

[andiagung]

You are the one to be blamed for having bought your phone in some weird store. Did you find out with the use of what equipment it was refurbished? Did you ask where the staff of that place buys parts from?

[fadlyzuld]

Galaxy eSolutions emphasizes lower costs through controls at every stage of the refurbishment process. They own a refurbishment factory, and they process all retail transactions themselves. This means they control the price and quality. Not only that, but Galaxy eSolutions guarantees the best price/quality matrix.

[cinming1]

Our team will design an API call to a online database service provider and put the information of the IMEI collection as well as the tracking of it on blockchain.

Are u sure u on the right thread?

[kevinantonio]

Can anyone find out what the bounty is now not charged ?for the second week there are no charges

[zayzik]

Can anyone find out what the bounty is now not charged ?for the second week there are no charges

My understanding is that the spreadsheet is not updated weekly, which may cause confusion.
However, this is not the best place for bounty information. The BitcoinTalk thread speaks directly to the bounty manager.

[tientien4]

We outsource our bounty management campaign and do not discuss bounty program here. We only discuss about the project and ico here. Please kindly refer to the following thread for bounty discussion: https://bitcointalk.org/index.php?topic=2852878.820

[hassanchahrour]

It was on my field(where I write) and I thought it was a new feature of the chat. So I tried. Do you know more about those spams ? I don't want to be boring, so tell me if there's somewhere where I can have some answers about this problem

[andiagung]

Are you interested in promoting your ICO? Are you looking for more investors? Do you want to make more sales? I have a unique method of promoting your ICO to get the attention of investors to your ICO thereby leading to more sales. If you’re interested and would like to take advantage of this, kindly send me a PM.

[kevinantonio]

From the beginning up to date, we are here supporting to the project we tend to believe, not just in its potential but its real life application which everyone will be beneficiary. #GES #ICO