Lex Pool (A rewritten pool based on uray source)
-
@rds try replacing socket.io.js with https://cdnjs.cloudflare.com/ajax/libs/socket.io/2.0.1/socket.io.js
-
@Lexicon , So I would copy all the script off the web link you posted, edit socket.io in the client folder, replace the script in there with the web script and save the file with the same name (socket.io) ?
-
Worked like a charm. Thanks I now see an active, animated webpage. 1 miner, haha.
As a point of interest, why did this solve the problem? Was it specific to my situation or should this file be the standard for the pool software?
-
@Lexicon ,
Is the pool fee BURST account supposed to show up as a miner? I only have one miner, but the screen shows 2 miners and one if the FEE account??
-
@rds ja it shows the fee accountant as a miner . Something I seen earlier cumulativeFundReduction : 0.5,
Thats going to pay 50 / 50 .
-
@tross said in Lex Pool (A rewritten pool based on uray source):
@rds ja it shows the fee accountant as a miner . Something I seen earlier cumulativeFundReduction : 0.5,
Thats going to pay 50 / 50 .
Not sure I understand the payout structure can you explain it in ninja terms?
I know for ninja, if you hit a block you get your current share and your historic share I believe it's 60% for the current 40% for the historic. Is that how it is for this pool except it's 50/50?
-
@rds that setting pay 50% current shares and 50% All Shares (historical shares) change it to .40 then its 60/40
-
@tross said in Lex Pool (A rewritten pool based on uray source):
@rds that setting pay 50% current shares and 50% All Shares (historical shares) change it to .40 then its 60/40
OK, that is simple enough, thanks.
What do the numbers in the brackets mean next to the miners in the "all round shares" box mean?
-
-
new commit.
this fixs a bug where if you set block mature to more that 1 and win 2 blocks in a row reward wouldn't calculate correctly.
