Lex Pool (A rewritten pool based on uray source)
-
@iKnow0 From the time I got my host up, and these forums started I've said the same thing - If ANYONE has a Burst related project, I'll host a VM for them for free. Offer still stands.
-
@Lexicon
Do you have the code needed to allow my pool to pay 50% to block finder, with rest distributed as normal? I know it was talked about further up in the thread
-
@haitch said in Lex Pool (A rewritten pool based on uray source):
@iKnow0 From the time I got my host up, and these forums started I've said the same thing - If ANYONE has a Burst related project, I'll host a VM for them for free. Offer still stands.
That's so noble from you, your're doing a lot to this community and wish its pays you back
@Lexicon PLEASE do better documentation to avoid such little incidents .. your work is highly appreciated
-
Hi, lex. I know a little javascript, but I'm in no way am Einstein. Can you tell me simply how you got the miners capacity? I would like to display it in the panel. And what is the Pending Payments on your pool? Is that estimated payments? Thanks!! :-)
-
@Tate-A pending payments show the payments that haven't hit the min payout. as soon as these guys reach over 20 burst it releases it as a payout.
as for showing capacity. its pretty hard to do. as it involves storing the info in one of the json files. and if you already have data in them you would need to delete them before doing any changes. as if they have 1 thing out of place the entire pool refuses to run
-
@Lexicon Have you considered raising the payout threshold? Those that earn their Burst slowly and just creep over the threshold are effectively paying 5% of their earning for transaction fees. That's why the 300 Burst/24 Hours idea was implemented on the Ninja pools - it makes the impact of the fee much lower.
-
@haitch its something ive considered. i was going to raise it either when i replaced the file database with a sql based one instead. as ive found when a block is won it has to read x amount of lines from a file and the bigger this file grew the longer it took. or when i coded in some form of auto release if the miner hasn't been on the pool for greater than 24 hours as when people pool hop it doesn't release the funds and i found the file to grow quite large after a few weeks/months.
-
When runnning the pool I have the problem, that it confirms much too high deadlines to my miner... So the miner send a deadline of about 1 day and the pool confirms 1000 years.....
Any idea what could be the problem?
-
@schnebi i aint sure what that could be. make sure your poolPublicRS and poolPublic are set correctly and you passphase for the pool wallet is correct. that happens to me when these are set incorrect
-
edited original thread. includes some useful documentation for when users need to swap vps hosts. or upgrade to a new host.
unfortunately when doing this myself my pools paid out twice however that was caused due to an oversight which i explain how to easily avoid
-
just commited an update so burst-pool.js had a simple getDateTime Function and a simple change to show miner type
Details
-
getDateTime added so users can add times to console output. added a
simple example with best deadline. -
added icon display for various miner types. so users with blago who
get a best deadline get shown with blago's icon. same with andriod. and
jminer. unknown ones will come up with a ? icon
-
-
-
The Tools you have written for Burst @lexicon are awesome!
-
@adsactly thanks buddy and many more to come :)
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!





