Lex Pool (A rewritten pool based on uray source)
-
Got everything (hopefully) set up right, got the latest files from @Lexicon, server starts up ok, I can access the webclient page from outside my internal network so the port fowardings are ok...
as soon as I try to connect from my other computer to test the pool, the burst-pool.js crashes out with the following
C:\Users\NiceHash Miner\Desktop\burst-pool-master>node burst-pool.js
genesis base target = 18325193796
current timestamp 1481404217245
genesis-block blocktime 73681817
genesis-block timestamp 1407722400245
burst pool running on port 8124
websocket running on port 4443
http server running on port 80
TypeError: minerReq.query.hasOwnProperty is not a function
at onNonceSubmitReq (C:\Users\NiceHash Miner\Desktop\burst-pool-master\burst
-pool.js:82:24)
at transformRequest (C:\Users\NiceHash Miner\Desktop\burst-pool-master\burst
-pool-protocol.js:80:5)
at Server.<anonymous> (C:\Users\NiceHash Miner\Desktop\burst-pool-master\bur
st-pool-protocol.js:128:9)
at emitTwo (events.js:106:13)
at Server.emit (events.js:191:7)
at HTTPParser.parserOnIncoming [as onIncoming] (_http_server.js:546:12)
at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
cleanAny ideas?
Edit: Quick search found similar issues https://github.com/hapijs/hapi/issues/3280 must be a difference in the node version I am running. I am running node 6.9.2 I Have confirmed that rewirint the code as liste in link does work (didnt redo all code, just enough to test). What node version are you all running?
-
I had the same issue before, when I have used latest node. Installing older version fixed the issue. I am using node 4.6.2
-
@Jumper I didnt update mine either and glad I didnt lol
-
@Jumper Ill play around with node files, see which one is the latest that this supports. and post that so @lexicon can specify it in the instructions
-
https://nodejs.org/download/release/v5.12.0/ this version appears to be the latest that can run the pool with its current coding. Change in the coding as listed above will be needed to run on any newer version of nodejs
-
pool is up at burst.btfg.space
Be grateful if anyone can do some quick mining there and tell me if everything appears to be functioning normally :)
-
Will tested, so would be lovely to test my too.
http://burstcoin-germany.ddns.net/Edit: Works
-
@MrWho No problem, Ill test it out on my other machine for ya :)
-
@MrWho
Attempting to mine at your pool crashes my miner!
-
@MrWho yup, works!-)
my own "egopool" unfortunately does not! my dl confirmations are a few thousand years long!-(
-
@nixxda thanks for testing both, nixxda are you joined over my ip or url? I will look at your pool if you wanna send.
-
@MrWho url. (both me!)
I've shut mine down for today. bin müde!-)
-
<.< I want one of those nice index pages with the local and global chat!!! :P
-
You can bind it with javascript very quickly. :)
-
may be easy but i barely have time to sit down and do the work i need to lol.
Though I would be willing to pay someone to make a nicer front page for me. If anyone is interested, let me know a price
-
I have just discovered that the script will send coin to a hardcoded address.
You should comment out these line, unless you are ok of this action
bust-pool-payment.js
This is how it should look like once you commented out:
-
@Jumper
Thats the code for sending part of the mining fee to the developer (lex) for further development. Its easier to turn it off in your config file (set devfee = false)that being said, thanks for finding where it is hard coded! later I want to be able to change it still give the dev a bit, but less than 1% (as I play to run my pool at less than 1% fee :)
-
@Valareos thanks for pointing that out man. i wish people would take the time to read the post. ive edited the first one now to include this so it wont be missed. its saddened me that someone would openly call out that im a thief. then modify the code that gives me an incentive to continue working on this project. which is currently less than 25 coins per block and getting smaller each month.
the amount of headache not having my release due to ghost blocks and forks would far exceed this cost.
comments like those make me lose motivation for a project i worked on solidly for 3 months till 4 am. whilst juggling a full time job. and just shows how far some people are willing to go. i was deliberately staggering releases to this source just to test the waters. and having the risk of losing my credibility from a mistake and not just that but openly screenshotting and posting it in 2 places on the forums.
i dont know whether to drop this project or continue with it now.
-
Dont lose faith. And to be fair most people dont read past the first post anyway. unless htey looking for a specific fix to a problem.
-
@Lexicon Please continue your work - having pool code options is important.
I've commented a number of times in the other thread.
Two suggestions - document the setting in the readme, and make the donation percentage configurable.
If the pool operators decide to disable the devfee, I'll assist you with development funds.



