Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts)
-
Ok. busy day. just moved the pool over to the new host. found the redirect feature in the config works perfectly so ill write up some notes to add to the repo. it did take about 30 minutes for the new dns to fully propagate throughout the network.
had a mild hiccup where the pool paid out twice on block

as a preemptive measure as i knew this might happen i sent the pool 4k burst as a safeguard as it were. adding to the 6k left in it for any similar issues. just in case we won 2 blocks in a row.
after talking with IceBurst in an upcoming update ill be adding the android logo next to the best deadlines of users using the Android miner. edit: i have now written this code in and should display like this

this now means i can move the discord bot from my laptop onto my old paid vps. meaning it should have 100% uptime (unless some wierd funky magic happens and something fatel errors. but ill fix these as they arise.)
-
Great news! im working on another potentially huge update today. this update reduces wallet stress by about 90% (a guess based on what ive seen, ill be recording some metrics to get a more accurate number). basically whilst going through looking for what submitNonce returns i found that the pool forwards every single submission sent from every miner to the wallet. regardless on if its the best deadline or worst.
so im writing a quick process that uses the deadline sent from the miner. compares it to the best deadline submitted and if its the best it then forwards it to the wallet. if it isn't. it doesn't submit but calculates shares anyway.
an example of this old method
- Miner 1 share 6 hours - submitted to wallet
- Miner 1 share 5 hours - submitted to wallet
- Miner 2 share 9 hours - submitted to wallet
- Miner 3 share 1 minute - submitted to wallet
- Miner 1 share 3 hours - submitted to wallet
- Miner 2 share 5 hours - submitted to wallet
- Miner 1 share 2 hours - submitted to wallet
- Miner 1 share 1 hours - submitted to wallet
- Miner 2 share 3 hours - submitted to wallet
the new method will look like this
- Miner 1 share 6 hours - submitted to wallet
- Miner 1 share 5 hours - submitted to wallet
- Miner 2 share 9 hours - skipped wallet submit
- Miner 3 share 1 minute - submitted to wallet
- Miner 1 share 3 hours - skipped wallet submit
- Miner 2 share 5 hours - skipped wallet submit
- Miner 1 share 2 hours - skipped wallet submit
- Miner 1 share 1 hours - skipped wallet submit
- Miner 2 share 3 hours - skipped wallet submit
obviously the more miners the worse this gets. as you could imagine 70 miners submitting 10 api calls per miner to a wallet in less than 2 minutes. is pretty intensive to say the least. in comparison the new method should only send about 1-10 api calls total. each round compared to what could be 700 calls
-
@Lexicon imagine my 291miners lol Great job!
-
after talking with IceBurst in an upcoming update ill be adding the android logo next to the best deadlines of users using the Android miner. edit: i have now written this code in and should display like this
Thank you sir. It's collaborative development like this that produces the best end products for the users. Rock on.
-IceBurst
-
@IceBurst it is indeed buddy. thanks for the heads up :)
in regards to the post i put up the other day about an update. the thing i was looking to improve would of gotten much slower (due to the code taking 1000ms compared to the 150ms the wallet takes) so ive put that on the back burner for now and will get back to it when i get chance.
so instead ive worked on forwarding the api call to submit a deadline to multiple pools. instead of just the current.
so each round not only do the best deadlines get submitted to the local wallet instance. but it also goes to the web versions.
-
just had my first wallet fork. 3 blocks. lost roughly 6k of the buffer i had in the pool wallet. quite frustrating..
im going to add some checks in on new block so i can detect a fork if it happens and prevent payout to stop the wallet from bleeding. maybe even make it swap wallets
-
Everyone.
today i updated the code on my server. it fix's some issues where users were submitting nonce's over port 80.
this missed a lot of code out so the recent update disabled the use of this port for most api requests. please use port 8124 instead.
ill be working on updating the source so it accepts this again once ive written a process so it all goes through the same procedures.
-
You Da Maaan! Lex.
Keep at it.
-
Great job Lexicon! I wish everyone could see the magic you created since we started working together. From August -December you spent day and night trying to fix this code and every time it gets better and better! If you are not an asset to this community then I dont know who is!
-
@tross Amen to that :)
-
@tross I agree, though I haven't worked with or had a lot discussions with him, I've noticed he's been actively contributing to the community since he created his account.
-
well after all thats happened ive finally replotted 1tb. and shitloads left to go.
thanks to the members who helped me and @socalguy for those kind words
-
giveaway happening on lex pool due to wallet payments getting deferred and pool downtime
added in some new code to make it easy to excute giveaways or Burst bashs as tross likes to call them.
also upped the payout threshold to 250
-
@Lexicon Are you planning to implement account names on your pool?
-
@Ip85 at some point yes.hopefully when i move it from the current method of saving json file to using mysql.
i would do it now however without storing this info in a table it becomes quite heavy on the wallet.i might have a quicker solution though.
in other news ive just uploaded the new interface for testing
http://burst.lexitoshi.uk/index2.htmlit uses bootstrap and bootstrap tables below is a preview. above is the link to the live demo

-
-
I totally agree with Lexicon! I seen what the logs did to my system. I already got a linux vps so might try to add this all to apache php sql and company but am rusty with those things lol
-
-
@LithStud said in Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts):
@Lexicon you might wat to do
.panel-primary { border-color: #08BA01; overflow: hidden; };)
done. thanks for the bit of css change. i didnt see what scrollbar it removed so guessing it was something you were seeing that i wasnt
because this is in bootstrap it scales perfectly to IOS and andriod devices/
@nixxda the color scheme is using the same css however using datatables and some fancy bootstrap widgets to show everything nicer.
before you say it.. yeah i know current shares isnt in a table yet. kinda added a dirty fix to get that running as it isnt as simple as passing a json to the datatable.
-
@Lexicon Nice and clean, great job






