Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts)
-
going to rewrite the payments.js today. laptop retstarted itself last night so the pool went offline for a significant amount of time lol. set up a discord as well https://discord.gg/Z2HSNFv
-
new codes written and in testing. removed the code that kept the poolfee in the balance of the pools wallet and instead wrote in some code that sent the fee out as a transaction instead. this should remove the negative pool issue as a wallet can never have less than a 0 balance.
-
@Lexicon nice work guys
-
had a small issue where the wallet got stuck. when i loaded it in safe mode it said block not accepted. had to delete the entire burst folder and replace it with an earlier backup. ive made a few more changes due to a few bugs. and now added somethings so you can chat

-
should be handing over my code to @tross later. all i need is to hit another few blocks to be shown its stable and nothing goes wrong. like people getting pending payments for a negative value. the pool going negative.or it crashing due to a typo in some code. doesnt help that i was up till half 3 am lol. probably why i have eyestrain today.
-
@Lexicon Your doing a great job! Maybe we get lucky today!
-
we hit another block about an hour ago whilst i was on the way to work lol.
-
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.
-
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
-
@Lexicon Happy Birthday! We can wait till ya get back! Have fun!
-
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
-
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.
-
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
-
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 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
-
Pool seems to be frozen for four hours now.
-
@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
-
@Lexicon Well that chart makes sense now thanks again
-
@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



