Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts)

Lexicon

we hit another block about an hour ago whilst i was on the way to work lol.

Lexicon

Update,

going well so far. rewrote the way payments are now done. separated chat and put it into a tab control on the page so now we have local and cross pool chatrooms.

removed a 5 second delay on sending payments. and added the 5 second delay after payments are sent out. this is so the wallet has time to catch up before the next pool round starts as sometimes the command to get balance returns a balance with a few missing transactions that cause the pool to think it has another X amount in it available to send out. thus sending the pool minus.

Lexicon

started work last night on changing the frequency of payouts. i was looking at making it so it sends x amount of payouts split over x amount of rounds configurable by the config.

however today is my birthday and i reckon im gonna spend it getting smashhammeredholed instead XD

tross

@Lexicon Happy Birthday! We can wait till ya get back! Have fun!

Lexicon

made a few more changes today. to send payments. added a line in the config file for Payments per round. so it only sends out x amount of payments per round to reduce spamming the wallet with 50+ transactions in less than a second. and re enabled payouts. sent out 8k burst over 6 rounds. so that works

Lexicon

looking good so far last change i seperated payments and distribution of funds into pending via 2 config settings.

now when a new block comes it checks if the currentfund> pendingpayments. if it is it then checks if currentfund>min payout. if this is true it will distribute the current block amongst the shares. if its false it will start the payment run.

ill work on a process flow when i get time to show this. also within the next few weeks ill be sending 3k to the pool at random intervals as a giveaway. so keep posted for that.

FrilledShark

I have edited the main post as per @Lexicon 's request.

change the thread title to "New Burst Pool In Development pooburst.bounceme.net"

And on the first post change the address from http://burstpool.servebeer.com to http://pooburst.bounceme.net

Lexicon

Thanks @FrilledShark you a legend..

ive made a process flow detailing what changes i've now made. it took about 5 minutes and only really outlines what logic payments now take.

bandarfjb

I don't know why my internet provider block your pool address???

Lexicon

@bandarfjb its probably because its a no-ip address. try using the 176.126.246.124 address or http://burst.lexitoshi.uk/ instead.

ive also just moved my entire pool onto a linux vps so it now has a static ip. and also means when my power goes at home the pool still stays up.

hopefully ill start to see more miners so i can test this code. might also have to add a donation button to help pay for the vps costs. but ill look at that when i can.
i dont mind spending my own dollar for this purpose

FlippyCakes

Pool seems to be frozen for four hours now.

Lexicon

@FlippyCakes thanks for letting me know. i got an error in the wallet whilst i was asleep.

the server is now catching up i had to restore an old copy of the block.db file in the wallet.

^[[A2016-10-22 01:30:09 SEVERE: Error in blockchain download thread
java.lang.RuntimeException: java.sql.SQLException: Login timeout
at nxt.BlockDb.hasBlock(BlockDb.java:43)
at nxt.BlockchainProcessorImpl$4.getCommonMilestoneBlockId(BlockchainProcessorImpl.java:470)
at nxt.BlockchainProcessorImpl$4.run(BlockchainProcessorImpl.java:293)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.sql.SQLException: Login timeout
at org.h2.jdbcx.JdbcConnectionPool.ge

Burstde

@Lexicon Well that chart makes sense now thanks again

Lexicon

@Burstde sometimes its easier to see in pictures than in code how things works. it helps when spotting mistakes. the diagram isn't a full picture but it contains the jists of what was changed.

also after 8 hours of deleteing db files i finally got it back up and running. im wondering if this is related to the dns attack that happened in america over the past few days. im also thinking that could be why tross pool was seeing orphaned blocks

jervis

@Lexicon what's the difference of this pool from a ninja clone pool? Also, you should have someone to look after this on a different timeline to avoid wallets getting stuck. :) I would love to jump in here :)

Lexicon

@jervis this one i'm developing as a customisable updated version of urays pool with more features.
currently the old one isn't as robust. payments go out async and sometimes when it requests the balance from the wallet. it doesn't include some of the payments going out causing the balance to rise. when this happened it shares out the balance which is wrong. and the next block when it gets the correct balance the pool goes negative. if this is left it causes the next winning block to have a lot less to pay the pool.

this was one bug i've found. im also adding in some protection against ghost blocks. and intending to have a request payment feature in the future so users of the pool can save on TX fees.

another planned update is to have a much fairer pay system than using just shares. where instead the block winner gets half of the block then the rest gets divided amongst the pool.

i noticed the ninja pool was quite popular. however i really dislike how it looks. its almost as if someone ate a load of starburst and skittles and vomited pastel colours all over the page.

BenBurst

@lexicon Hi there,
I'm running the modified Uray pool since 18 days, I just see it stucked one time and never see negative balance on it.
Maybe some errors come from the pool settings ? If you are available in the next hours I would like to discuss a bit with you as you are coding some updates /bug corections.

Ben

tross

I think the larger the uray pool the more evident the bugs are. If you try to configure the pool to payout similar to ninja then you will see the bugs. Like nextBlockFundSaving why would that be needed? why give an award for the next block? Set it to 0 and all funds go to current block and all shares. This is where the fun begins! Now you have cumulativeFundReduction a value of 1 will distribute more equally but I think it pays bottom heavy plus block winner reward is very low for small miners and a little better for large. Ok for more realistic rewards then set cumulativeFundReduction to .5 <<< all rewards from block winner to small miners are exceptionable. All works fine then out of the blue you get the pretties minus you laid your eyes on! I think uray pool was designed PPLN to discourage pool hopping. Thats why my conf has problem! Lexicon can give you a better answer!

Lexicon

@BenBurst sure dm me. ive seen both the issue on my pool and tross pool its less frequent on mine but happens a lot more on his due to the amount of miners he has gives it a greater chance on happening

Lexicon

@BenBurst has also seen the minus in his pool. it happened in the past 24 hours.

ive made another change to fix this. what i've done is make it so each block it only sends out less than a value that's now set in the config..

so if the value in the config is 2000 once the payments hit a transaction that pushes it over 2k it will split the last payment removing any extra and saving that for the next round.
this coincides with my prior update where the balance isn't shared out unless the value goes over 2000.

an example of this is if a block's value was 2.5k and i had to miners a and b the payout would look like this if miner a got shared 1k and b got 1.5k

Block1
Pay a 1000
Pay b 1000
Block 2
pay b 500