Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts)
-
@Lexicon Yes it is... and it can show in the future a lot of info in the future like blocks info, reward info detailed and a lot of new features so it is indeed pretty cool ?! The potencial of it is huge imo?!
-
so yeah a recent addition was showing the block reward and tx fee on the discord chat for this pool. discord.io/burst
haven't had much time to do many more updates. super busy at work and its the holiday season. along with helping almost every person setting up a new pool.
the pool has finally sustained more than 64 users i think the record of 70 was hit either this week or last. keep up the goo work guys.
its really helpful to have you all mining on the pool as it allows me to debug problems with the source i've written faster. users have noticed my modifications improving performance over time. showing less non confirmed deadlines etc. and the feedback is great.
-
just made a miner change to the pool. i set the minimum payout to 100 burst. this way 5% of payments for smaller miners aint lost as tx fees
-
Quick thank you to the member of my pool who wrote an article on burst.
marketing is always something burst needs so getting publicity like this is great news espeacially for burst.
not to mention that he added a link to my pool in the article ;)
i cannot thank you enough.. i was hoping that by today i would have the pool moved over to a new server that has an 800MB/s down and 250 MB/s up speed however this has been delayed for one reason or another.
the next thing ill be doing ideally is replacing the method of storing data in json files. and instead storing this in a SQL database. as file databases can get slower the bigger the files get. the 100 burst payout threshold has been doing well. and miners have been seeing the benefit. im still thinking of raising this though or at least making it so users can set it themselves. ill probably task this for when the SQL database is implemented. as storing so many accounts and payout thresholds could get quite large in a json file database.
when thats implemented im also going to add a few more columns to store some user statistics etc. like how much burst the pool has sent the user in total along with TB Size and other nice things.
-
-
@gpedro cookies are being sent as we speak
-
@nameless @gpedro thanks for the cookie guys wasnt expecting that :D i should probably upgrade the wallet on my laptop to 1.7.1 as the asset transfer frose my wallet pmsl
-
@Lexicon I think you mean 1.2.7 but you're welcome for the cookie bro ;P
-
@gpedro yeah well rather 0.3.7.1 just woke up after a long day lol should probably wait a few minutes before trying to internet XD
-
@Lexicon WOW you woke up later hahahaha Holidays right? Enjoy bro... ;D
-
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 :)



