Bitcoin Forum
April 24, 2024, 12:10:55 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: wrong Network Hash Rate: for monero  (Read 645 times)
bapparabi (OP)
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000


View Profile
February 11, 2017, 03:55:09 PM
 #1

hi we use node-cryptonote-pool  for monero pool but our site show double Network  the actual hash rate .. do any one know what is the actual iisue and how to solve it

your valuable info will help us ..
1713960655
Hero Member
*
Offline Offline

Posts: 1713960655

View Profile Personal Message (Offline)

Ignore
1713960655
Reply with quote  #2

1713960655
Report to moderator
1713960655
Hero Member
*
Offline Offline

Posts: 1713960655

View Profile Personal Message (Offline)

Ignore
1713960655
Reply with quote  #2

1713960655
Report to moderator
1713960655
Hero Member
*
Offline Offline

Posts: 1713960655

View Profile Personal Message (Offline)

Ignore
1713960655
Reply with quote  #2

1713960655
Report to moderator
According to NIST and ECRYPT II, the cryptographic algorithms used in Bitcoin are expected to be strong until at least 2030. (After that, it will not be too difficult to transition to different algorithms.)
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1713960655
Hero Member
*
Offline Offline

Posts: 1713960655

View Profile Personal Message (Offline)

Ignore
1713960655
Reply with quote  #2

1713960655
Report to moderator
1713960655
Hero Member
*
Offline Offline

Posts: 1713960655

View Profile Personal Message (Offline)

Ignore
1713960655
Reply with quote  #2

1713960655
Report to moderator
1713960655
Hero Member
*
Offline Offline

Posts: 1713960655

View Profile Personal Message (Offline)

Ignore
1713960655
Reply with quote  #2

1713960655
Report to moderator
nshyamkrishna
Member
**
Offline Offline

Activity: 72
Merit: 11


View Profile
February 11, 2017, 05:35:24 PM
 #2

hi we use node-cryptonote-pool  for monero pool but our site show double Network  the actual hash rate .. do any one know what is the actual iisue and how to solve it

your valuable info will help us ..

Try adding these lines to config.json file

  "coinUnits": 100000000,
  "coinDifficultyTarget": 120,

add these two lines after 3rd line ("symbol": "XMR",) in config.json

I guess it should work. pls check and let me know.
bapparabi (OP)
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000


View Profile
February 11, 2017, 05:48:18 PM
 #3

hi we use node-cryptonote-pool  for monero pool but our site show double Network  the actual hash rate .. do any one know what is the actual iisue and how to solve it

your valuable info will help us ..

Try adding these lines to config.json file

  "coinUnits": 100000000,
  "coinDifficultyTarget": 120,

add these two lines after 3rd line ("symbol": "XMR",) in config.json

I guess it should work. pls check and let me know.

no its not working

Code:
2017-02-11 20:44:00 [master] Pool fork 1 died, spawning replacement worker...

Error: bind EADDRINUSE
    at errnoException (net.js:901:11)
    at net.js:1081:30
    at Object.12:1 (cluster.js:592:5)
    at handleResponse (cluster.js:171:41)
    at respond (cluster.js:192:5)
    at handleMessage (cluster.js:202:5)
    at process.EventEmitter.emit (events.js:117:20)
    at handleMessage (child_process.js:318:10)
    at child_process.js:392:7
    at process.handleConversion.net.Native.got (child_process.js:91:7)


this error i get
nshyamkrishna
Member
**
Offline Offline

Activity: 72
Merit: 11


View Profile
February 11, 2017, 06:03:43 PM
 #4

hi we use node-cryptonote-pool  for monero pool but our site show double Network  the actual hash rate .. do any one know what is the actual iisue and how to solve it

your valuable info will help us ..

Try adding these lines to config.json file

  "coinUnits": 100000000,
  "coinDifficultyTarget": 120,

add these two lines after 3rd line ("symbol": "XMR",) in config.json

I guess it should work. pls check and let me know.

no its not working

Code:
2017-02-11 20:44:00 [master] Pool fork 1 died, spawning replacement worker...

Error: bind EADDRINUSE
    at errnoException (net.js:901:11)
    at net.js:1081:30
    at Object.12:1 (cluster.js:592:5)
    at handleResponse (cluster.js:171:41)
    at respond (cluster.js:192:5)
    at handleMessage (cluster.js:202:5)
    at process.EventEmitter.emit (events.js:117:20)
    at handleMessage (child_process.js:318:10)
    at child_process.js:392:7
    at process.handleConversion.net.Native.got (child_process.js:91:7)


this error i get

Try this frok.. https://github.com/clintar/cryptonote-xmr-pool

its updated..
bapparabi (OP)
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1000


View Profile
February 11, 2017, 06:51:28 PM
 #5

hi we use node-cryptonote-pool  for monero pool but our site show double Network  the actual hash rate .. do any one know what is the actual iisue and how to solve it

your valuable info will help us ..

Try adding these lines to config.json file

  "coinUnits": 100000000,
  "coinDifficultyTarget": 120,

add these two lines after 3rd line ("symbol": "XMR",) in config.json

I guess it should work. pls check and let me know.

no its not working

Code:
2017-02-11 20:44:00 [master] Pool fork 1 died, spawning replacement worker...

Error: bind EADDRINUSE
    at errnoException (net.js:901:11)
    at net.js:1081:30
    at Object.12:1 (cluster.js:592:5)
    at handleResponse (cluster.js:171:41)
    at respond (cluster.js:192:5)
    at handleMessage (cluster.js:202:5)
    at process.EventEmitter.emit (events.js:117:20)
    at handleMessage (child_process.js:318:10)
    at child_process.js:392:7
    at process.handleConversion.net.Native.got (child_process.js:91:7)


this error i get

Try this frok.. https://github.com/clintar/cryptonote-xmr-pool

its updated..

great this work like charm ..all working fine now
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!