Lex Pool (A rewritten pool based on uray source)
-
@Burstde that error message usually means you dont have npm installed. or have another versoin that is missing the moment modules. try reinstalling npm and node 4.4
-
This post is deleted!
-
@Burstde it runs on node.js mate. you would need npm either way. theres no possible way you would of had the original pool running otherwise.
in your old pool folder. move node_modules into the new pool or copy it. then try.
NPM stands for Node Package Manager.
-
@Lexicon said in Lex Pool (A rewritten pool based on uray source):
move node_modules
Your right, that's funny carried that folder around for awhile not knowing why.
-
@Burstde said in Lex Pool (A rewritten pool based on uray source):
@Lexicon said in Lex Pool (A rewritten pool based on uray source):
move node_modules
Your right, that's funny carried that folder around for awhile not knowing why.
you can delete that folder and do a
npm installto pull the modules defined in the "package.json"
-
@Lexicon
Funny thing just happened in your pool! Which makes me question the "payout scheme" a bit!
I'm not questioning fairness because it could happen to everyone and it just is!-)So here whats happened: We won 3 Blocks in a row depleting all the "history shares". Which led to an huge payment for the last block winner.
Third block win in a row
payments
it looks like "GAJL-...." squeezed in with a few Minutes deadline between the winner and my one hour dl (M2Y3-....)!
So he got a little for his current shares. Nevertheless I'm happy for them!-)
But I'm starting to think this is suboptimal! Because it somewhat defies the "pool thought". And you could probably win the whole block reward with an fast enough dl.edit: I put this here because it seems to be "uray mannerism" which cant be unset in the config. right?
Btw. are the payments setup now to pay 50% to the winner no matter what dl he has? Saw you talking about it but I'm unsure.
-
@nixxda cheers buddy. it is on the list of things left to do and i did post it in my original thread in the pool announcements a few weeks ago. i have a local copy of the live pool that i use for testing to prevent pool downtime. i'm getting somewhere with these changes.
is there any chance you can test the payout methods for me. ill let you know when ive uploaded the changes to payouts. it currently goes still goes off the standard uray payout code
i thought of a minor issue with keeping the historic shares and keep paying out on them was if someone were to leave the pool and the pool hit 2-3 blocks in a row the round after he left. the user would be getting paid for being at another pool. however im thinking this issue might not crop up often and when it does the effects could be negligible
i've got 3 types of payouts in mind
-
Reserve half of the block reward for the winner upon working out share payments ignore the block winners shares and payout the remaining burst and dont delete prior shares.
-
Reserve half of the block reward for the winner upon working out share payments ignore the block winners shares and payout the remaining burst and delete prior shares
-
Payout to each rounds shares but dont delete share history
if theirs any others you can think of and also if there is one you would like me to do first let me know. ill make this somewhat of a priority when im between tasks
-
-
hej @Lexicon
I had to think about your Ideas for a while!-)
So basicly we have got this two suboptimal cases where one is keeping the historic shares and continue to payout even when somebody left. And the other is resetting historic shares which leads to the problem I described above.
If I had to weighing them against each other I'd say that the first one probably happens more often but less Coins would be involved!?
Or is it exactly the same since one would always lose on historic shares?? I'm unsure...
Goal would be to make it the least "painful" for all the miners actually mining there!Personally I liked the Idea of paying out 50% to the block winner. Because he's the winner no matter what deadline he had!-)
And it enshures that you dont get under 1000 for winning (for the time being!)But my numbers dont ad up! I might still not have understood the uray payout fully. More thinking.......
as for testing, sure fire away! If you've got some dev pool running at an other port tell me! But I've only got one miner. Maybe I'll get my ACD account back next week then I've got two.
-
@nixxda it is to be honest quite hard to get right as that difference could of been tx fees. yesterday my pool hit a block with a 4000+ tx fee which would of sqewed any results. ill be interested to see the data this was based off if possible. https://cdn.discordapp.com/attachments/234305723285110786/255789393971773440/unknown.png
-
@Lexicon Block data you mean?!
http://pools.cryptodex.io/home seams to have issued 4 assets and payed 1000 Burst each. 1 2 3 4 !-)
-
Hello! New Burstminer looked everything over and am quite impressed.
I do want to set up my own pool, and given this is really the only up to date pool program I can find, I want to use this.
But im running into trouble. First, the files I get dont have the batch file for setting everything up.
I have ran npm install, but running node burst-pool throws errors (have to get them from the system itself,Ill post them later)
Any steps with your new files that I may be missing?
Also, in the Pool Fee, the percentages is listed such as 0.00015
Why is that? intuitively 1.5% would be .015 ...
THanks for the assist
-
@Valareos Are you running a wallet? The conf.js is the setup file and yes .00015 s a typo lol try .015 instead.
-
@tross I am running a wallet (downloading blockchain now), ive set up the burst-pool-config file (though Ill go and change the percentages now LOL)
Ill log onto the server here now and post the error im recieving
-
commas are a bane of my existance. was missing one, all works now it looks like
-
Repo has just been updated to use blockmature in config to set delay on blockwinner check by x amount of blocks.
-
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
