Burst.Lexitoshi.Uk - New Pool Development (New Feature Discord Alerts)
-
Update: ive decided to change the way the pool saves data. instead of using json files i'm thinking a sql database might be better suited. as its easier to query doesn't slow down as much when it gets big and you can index it. makes for easy reporting.
im probably going to leave the json file method as an option. maybe add it as a configurable option
ive been working a bit on getting users capacity to show in current round shares and previous round shares.
if anyone has any suggestions of things you would like to see or like to see changed dm me. im always open to new ideas lol.
-
@Lexicon showing users capacity for each of their miners would be huge.
-
@iKnow0 not that hard either it currently shows the capacity in the best deadline and ive managed to save this info in the poolshare.json file. all i need now is to bring it back to something on screen. im thinking of adding a text field where it shows the current difficulty of the network. that shows the total capacity of all miners combined. and maybe another tab that lists the NXT address's name and capacity of each miner.
theirs a slight issue with this though. its only really accurate for anyone using blago's miner. i think jminer doesn't send the info as i have someone on my pool who shows as 0 GB however these will limited to a small percent of the community.
ill be updating my repository today on Git-Hub when i get home. the update will have the issue fixed where uray keeps forking. and also fix's ghost blocks along with the pool balance going negative.
i was going to wait until i got most of the code done for everything before i did this however it should stimulate the community and help the smaller uray pools cope.
its been roughly 2 weeks since this update that should of fixed negative balance and ghost blocks. and so far neither lexitoshi pool or tross pool has had an issue with balance going negative or ghost blocks appearing. and considering tross pool has 250+ miners and mine has roughly 28. it seems highly probable that this issue has gone to
another note. ive also hit a milestone this week. despite having only 28 miners my pool has gotten quite high up the list of burstcoin pools. and was the first time this has happened since the pool began.

-
@Lexicon Excellent work! Stable and reliable pool code is must for Burst going forward.
-
Update,
just released the code that fix's ghost blocks, uray forks and negative balances.
can be found here.
https://forums.burst-team.us/topic/2643/lex-pool-a-rewritten-pool-based-on-uray-source
-
havnt had much time recently but i spent a short amount of it integrating discord into the pool.
so far theirs 2 commands shown below
and also notifications
i did add in some code so it send the entire console to a channel. might be advisable to mute the channel this is posted in to avoid the spam. ive left this out atm

discord link: https://discord.gg/Z2HSNFv
-
@Lexicon That's so cool man... hahahaha
-
its pretty useful the win alerts come through on discord for my phone. its a nice touch.
-
@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






