[ANN][POW][SOLACE] Solacecoin - Your humane Cryptonote coin

[AverageCitizen]

Hello!
I was attempting to create a new Solace coin pool cloned from Github (https://github.com/LPHuynh/cryptonote-solacecoin-pool) but keep running into an error and hoped someone with more knowledge could assist me.
Scenario: The pool is running, rpc wallet running, pool wallet open in background refresh. Miner connects and hashes, pool accepts shares. So it seems everything is working ok on the backend. Now, on the front end, when a miner connects, miner worker stats show and update, everything looks good. However, under the space where address lookup is, in red it blinks CONNECTION ERROR every few seconds. Nothing seems to be broken but I'm not a pool expert.
Could someone tell me how to fix the blasted red blinky connection error please?

Thanks and keep hashing!

AverageCitizen

I updated my github with a quick fix just now

Thank you Leafy, that did the trick.

[Schmeckles23]

First donation has been given out! http://charity.solace-coin.com/first-donation/

[algodude]

First donation has been given out! http://charity.solace-coin.com/first-donation/

Yay, for the kids 

[kabarbogor]

all pool down 

[AverageCitizen]

Hello!
I was attempting to create a new Solace coin pool cloned from Github (https://github.com/LPHuynh/cryptonote-solacecoin-pool) but keep running into an error and hoped someone with more knowledge could assist me.
Scenario: The pool is running, rpc wallet running, pool wallet open in background refresh. Miner connects and hashes, pool accepts shares. So it seems everything is working ok on the backend. Now, on the front end, when a miner connects, miner worker stats show and update, everything looks good. However, under the space where address lookup is, in red it blinks CONNECTION ERROR every few seconds. Nothing seems to be broken but I'm not a pool expert.
Could someone tell me how to fix the blasted red blinky connection error please?

Thanks and keep hashing!

AverageCitizen

I updated my github with a quick fix just now

Thank you Leafy, that did the trick.

Congratulations on the coin's first donation!!!!!!

Now, back to the blasted pool lol.  Apparently, I'm doing something wrong.
Scenario:

Pool hashing, everything showing ok on pool (front and back end). Miner connected for 36hrs @ 1.6 to 2 kh with no blocks found.
Daemon and wallet running on specified ports from solacecoin.json, RPC wallet synced on same port as stated in .json. Like I said, everything shows good grrrrr except no blocks found and the effort has been anywhere from 300% to 1256%. What might I have missed in configuring the pool?

Thanks for the assistance

[Schmeckles23]

Hello!
I was attempting to create a new Solace coin pool cloned from Github (https://github.com/LPHuynh/cryptonote-solacecoin-pool) but keep running into an error and hoped someone with more knowledge could assist me.
Scenario: The pool is running, rpc wallet running, pool wallet open in background refresh. Miner connects and hashes, pool accepts shares. So it seems everything is working ok on the backend. Now, on the front end, when a miner connects, miner worker stats show and update, everything looks good. However, under the space where address lookup is, in red it blinks CONNECTION ERROR every few seconds. Nothing seems to be broken but I'm not a pool expert.
Could someone tell me how to fix the blasted red blinky connection error please?

Thanks and keep hashing!

AverageCitizen

I updated my github with a quick fix just now

Thank you Leafy, that did the trick.

Congratulations on the coin's first donation!!!!!!

Now, back to the blasted pool lol.  Apparently, I'm doing something wrong.
Scenario:

Pool hashing, everything showing ok on pool (front and back end). Miner connected for 36hrs @ 1.6 to 2 kh with no blocks found.
Daemon and wallet running on specified ports from solacecoin.json, RPC wallet synced on same port as stated in .json. Like I said, everything shows good grrrrr except no blocks found and the effort has been anywhere from 300% to 1256%. What might I have missed in configuring the pool?

Thanks for the assistance

Has the blockchain fully synced?

[AverageCitizen]

Hello!
I was attempting to create a new Solace coin pool cloned from Github (https://github.com/LPHuynh/cryptonote-solacecoin-pool) but keep running into an error and hoped someone with more knowledge could assist me.
Scenario: The pool is running, rpc wallet running, pool wallet open in background refresh. Miner connects and hashes, pool accepts shares. So it seems everything is working ok on the backend. Now, on the front end, when a miner connects, miner worker stats show and update, everything looks good. However, under the space where address lookup is, in red it blinks CONNECTION ERROR every few seconds. Nothing seems to be broken but I'm not a pool expert.
Could someone tell me how to fix the blasted red blinky connection error please?

Thanks and keep hashing!

AverageCitizen

I updated my github with a quick fix just now

Thank you Leafy, that did the trick.

Congratulations on the coin's first donation!!!!!!

Now, back to the blasted pool lol.  Apparently, I'm doing something wrong.
Scenario:

Pool hashing, everything showing ok on pool (front and back end). Miner connected for 36hrs @ 1.6 to 2 kh with no blocks found.
Daemon and wallet running on specified ports from solacecoin.json, RPC wallet synced on same port as stated in .json. Like I said, everything shows good grrrrr except no blocks found and the effort has been anywhere from 300% to 1256%. What might I have missed in configuring the pool?

Thanks for the assistance

Has the blockchain fully synced?

Yes, the blockchain has been sync'd 100 percent on mainnet. Just to be sure of anything I deleted the DB and resync'd with the same problem results. RPC says [RPC0]Expected 1 tx, got 0

Update:
I noticed the daemon reported
2018-May-02 00:35:32.067870 [P2P2][118.69.72.95:53838 INC]Sync data returned a new top block candidate: 32936 -> 16232 [Your node is 16704 blocks (11 days) ahead]
SYNCHRONIZATION started
2018-May-02 00:37:30.395813 [P2P0][118.69.72.95:53931 INC]Sync data returned a new top block candidate: 32939 -> 16232 [Your node is 16707 blocks (11 days) ahead]
SYNCHRONIZATION started

HUH?! this must be above my paygrade.

[Schmeckles23]

Hello!
I was attempting to create a new Solace coin pool cloned from Github (https://github.com/LPHuynh/cryptonote-solacecoin-pool) but keep running into an error and hoped someone with more knowledge could assist me.
Scenario: The pool is running, rpc wallet running, pool wallet open in background refresh. Miner connects and hashes, pool accepts shares. So it seems everything is working ok on the backend. Now, on the front end, when a miner connects, miner worker stats show and update, everything looks good. However, under the space where address lookup is, in red it blinks CONNECTION ERROR every few seconds. Nothing seems to be broken but I'm not a pool expert.
Could someone tell me how to fix the blasted red blinky connection error please?

Thanks and keep hashing!

AverageCitizen

I updated my github with a quick fix just now

Thank you Leafy, that did the trick.

Congratulations on the coin's first donation!!!!!!

Now, back to the blasted pool lol.  Apparently, I'm doing something wrong.
Scenario:

Pool hashing, everything showing ok on pool (front and back end). Miner connected for 36hrs @ 1.6 to 2 kh with no blocks found.
Daemon and wallet running on specified ports from solacecoin.json, RPC wallet synced on same port as stated in .json. Like I said, everything shows good grrrrr except no blocks found and the effort has been anywhere from 300% to 1256%. What might I have missed in configuring the pool?

Thanks for the assistance

Has the blockchain fully synced?

Yes, the blockchain has been sync'd 100 percent on mainnet. Just to be sure of anything I deleted the DB and resync'd with the same problem results. RPC says [RPC0]Expected 1 tx, got 0

Update:
I noticed the daemon reported
2018-May-02 00:35:32.067870 [P2P2][118.69.72.95:53838 INC]Sync data returned a new top block candidate: 32936 -> 16232 [Your node is 16704 blocks (11 days) ahead]
SYNCHRONIZATION started
2018-May-02 00:37:30.395813 [P2P0][118.69.72.95:53931 INC]Sync data returned a new top block candidate: 32939 -> 16232 [Your node is 16707 blocks (11 days) ahead]
SYNCHRONIZATION started

HUH?! this must be above my paygrade.

Is there any chance you can come to Discord and we will help you?

[Schmeckles23]

Remote Wallet has been released!
https://github.com/schmeckles22/SolaceGUI-LITE/releases

[algodude]

Remote Wallet has been released!
https://github.com/schmeckles22/SolaceGUI-LITE/releases

this will make live so more easy

[jojogt]

Remote Wallet has been released!
https://github.com/schmeckles22/SolaceGUI-LITE/releases

What's the different with my GUI-Wallet Dev?

I can't figure it out, maybe someone can explain it here... thanks

[StandardPro]

Remote Wallet has been released!
https://github.com/schmeckles22/SolaceGUI-LITE/releases

What's the different with my GUI-Wallet Dev?

I can't figure it out, maybe someone can explain it here... thanks

Hello,

This wallet will sync with a remote node fixing long wait for the blockchain to sync.

[algodude]

Remote Wallet has been released!
https://github.com/schmeckles22/SolaceGUI-LITE/releases

What's the different with my GUI-Wallet Dev?

I can't figure it out, maybe someone can explain it here... thanks

the waller does not download the hole blockchain on you pc
when you open it, its ready for use. no need to wait for sync to finsh

[ethomaz]

I newbie question.

Are there a Linux GUI wallet?

Edit - I guess there is no binaries... I need to compile it

Edit 2 - Seems like no GUI to Linux at all

Edit 3 - Finally worked to mining with XMR-Stak on Linux... C2D E8600 running at 20H/s is normal?

[ethomaz]

Good morning.

How can I decrease the number of "Low difficulty share" on mining? I'm using XMR-Stak with a C2D E8600.

[algodude]

I newbie question.

Are there a Linux GUI wallet?

Edit - I guess there is no binaries... I need to compile it

Edit 2 - Seems like no GUI to Linux at all

Edit 3 - Finally worked to mining with XMR-Stak on Linux... C2D E8600 running at 20H/s is normal?

yea, the coin algo is Crytonight Heavy. calculations are harder

Good morning.

How can I decrease the number of "Low difficulty share" on mining? I'm using XMR-Stak with a C2D E8600.

to add fix difficulty add .diffnumber behind you wallet adrees in the miner confi file

So i would be :  pool.solace-coin.com:4500 -u walletadress.600 -p
(30x20=600)

[ethomaz]

to add fix difficulty add .diffnumber behind you wallet adrees in the miner confi file

So i would be :  pool.solace-coin.com:4500 -u walletadress.600 -p
(30x20=600)

Thank you... that option give me a lot of room to tests but 600 is losing a lot of work (only 30% accepted).

I'm from Brasil... maybe the transmission takes too much to be sent? I will try others difficult options lower and higher (now testing 1000) to see if I can reach at least 90% non-rejected... I will try others pools too.

[STAT303954]

Good morning.

How can I decrease the number of "Low difficulty share" on mining? I'm using XMR-Stak with a C2D E8600.

make sure your mining cryptonight heavy algorithm

[ethomaz]

Yeap I'm minning cryptonight heavy... that is why only 20 H/s... the others give over 40 H/s.

Weird enough I could find any fixed difficult to give me more than 20% acceptable share with XMR-Stak... so I changed the program... I'm using now XMRig and 99% of my shares are being acceptable with 600 fixed difficult (I did not tried other).

Seems like this XMR-Stak was causing the issue... XMRig 2.6 Beta (to support the algo) is working pretty well all day long.

Here my stats:

Pending Balance: 77.1172294 SOLACE
Total Paid: 0.0000000 SOLACE
Next payment: 1.507373408
Last Share Submitted: less than a minute ago
Hash Rate: 22.00 H/sec
Total Hashes Submitted: 546717

Even the pool site (where the hashrate only counts the accepted shares) is giving me ~20 H/s.

[CR78]

Remote Wallet has been released!
https://github.com/schmeckles22/SolaceGUI-LITE/releases

That makes much more easy. Thx.