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

Lexicon

latest changes are in the below screenshot.

added more css for the various different class types. added a new tab section to sow pending payments. along with calculating the humanized version of the deadline to display in the center console.

also working on various commands that can be typed through the local chat. currently only have one command entered which updates the pending payments tab.

logging to file from console is now also in. took me a shortwhile to add this into the various different class files. but it works. increases disk activity though so might not be a good option of you have slow disk's or load balanced vps servers.

also working on my first public release.

Lexicon

made a ton of changes over the past few days. ive now also created 2 different modes for detecting block payments.
the original way of doing this was check balance and payout if the balance reaches above a certain threshold.
the new one works by looking at the block winner for that block, then by finding out if that persons reward recip matches the pool address. if it does it then uses the getBlockInfo API call to find out the reward for that block and distribute that among the shares accordingly and stores them to a pending payment array. the pays out any in pending over the threshold set in the config.

also implemented commands that can be executed by putting a password you set in the config in the username box on the pool and typing the command in the message box.

currently ive written it so it outputs block info into the chat box and also made it so i can simulate a block win by going back to a prior block the pool ran.

Console output

genesis base target = 18325193796
current timestamp 1478722715029
genesis-block blocktime 71000315
genesis-block timestamp 1407722400029
burst pool running on port 8124
websocket running on port 4443
http server running on port 80
new block #293480 BT:1935112 ND:9469.836265807871
Pool Balance = 126.43294219 BURST
total pending payment amount = 64.74000000000001 pool balance = 126.43294219netB
alance = 61.69294219
9037319325910335992 payment amount 17.370000000000005 is below payment threshold
 0
8139841036819454640 payment amount 16.420000000000005 is below payment threshold
 0
12497588908633202484 payment amount 6.99 is below payment threshold 0
14834463895479742872 payment amount 13.409999999999995 is below payment threshol
d 0
3501633088787745304 payment amount 2.48 is below payment threshold 0
7811831612493581007 payment amount 1.42 is below payment threshold 0
10400995181240832668 payment amount -1 is below payment threshold 0
6238401638398757545 payment amount -1 is below payment threshold 0
16650910394466232610 payment amount -0.35 is below payment threshold 0
4161009231636266338 payment amount -1 is below payment threshold 0
storing pending payment 18.370000000000005 for 9037319325910335992
storing pending payment 17.420000000000005 for 8139841036819454640
storing pending payment 7.99 for 12497588908633202484
storing pending payment 14.409999999999995 for 14834463895479742872
storing pending payment 3.48 for 3501633088787745304
storing pending payment 2.42 for 7811831612493581007
storing pending payment 0 for 10400995181240832668
storing pending payment 0 for 6238401638398757545
storing pending payment 0.65 for 16650910394466232610
storing pending payment 0 for 4161009231636266338
new block #293481 BT:1935112 ND:9469.836265807871
Pool Balance = 126.43294219 BURST
total pending payment amount = 64.74000000000001 pool balance = 126.43294219netB
alance = 61.69294219
9037319325910335992 payment amount 17.370000000000005 is below payment threshold
 0
8139841036819454640 payment amount 16.420000000000005 is below payment threshold
 0
12497588908633202484 payment amount 6.99 is below payment threshold 0
14834463895479742872 payment amount 13.409999999999995 is below payment threshol
d 0
3501633088787745304 payment amount 2.48 is below payment threshold 0
7811831612493581007 payment amount 1.42 is below payment threshold 0
10400995181240832668 payment amount -1 is below payment threshold 0
6238401638398757545 payment amount -1 is below payment threshold 0
16650910394466232610 payment amount -0.35 is below payment threshold 0
4161009231636266338 payment amount -1 is below payment threshold 0
storing pending payment 18.370000000000005 for 9037319325910335992
storing pending payment 17.420000000000005 for 8139841036819454640
storing pending payment 7.99 for 12497588908633202484
storing pending payment 14.409999999999995 for 14834463895479742872
storing pending payment 3.48 for 3501633088787745304
storing pending payment 2.42 for 7811831612493581007
storing pending payment 0 for 10400995181240832668
storing pending payment 0 for 6238401638398757545
storing pending payment 0.65 for 16650910394466232610
storing pending payment 0 for 4161009231636266338
new block #293482 BT:1935112 ND:9469.836265807871
Pool Balance = 126.43294219 BURST
total pending payment amount = 64.74000000000001 pool balance = 126.43294219netB
alance = 61.69294219
9037319325910335992 payment amount 17.370000000000005 is below payment threshold
 0
8139841036819454640 payment amount 16.420000000000005 is below payment threshold
 0
12497588908633202484 payment amount 6.99 is below payment threshold 0
14834463895479742872 payment amount 13.409999999999995 is below payment threshol
d 0
3501633088787745304 payment amount 2.48 is below payment threshold 0
7811831612493581007 payment amount 1.42 is below payment threshold 0
10400995181240832668 payment amount -1 is below payment threshold 0
6238401638398757545 payment amount -1 is below payment threshold 0
16650910394466232610 payment amount -0.35 is below payment threshold 0
4161009231636266338 payment amount -1 is below payment threshold 0
storing pending payment 18.370000000000005 for 9037319325910335992
storing pending payment 17.420000000000005 for 8139841036819454640
storing pending payment 7.99 for 12497588908633202484
storing pending payment 14.409999999999995 for 14834463895479742872
storing pending payment 3.48 for 3501633088787745304
storing pending payment 2.42 for 7811831612493581007
storing pending payment 0 for 10400995181240832668
storing pending payment 0 for 6238401638398757545
storing pending payment 0.65 for 16650910394466232610
storing pending payment 0 for 4161009231636266338

the new mode looks like this compared

Local Console is also a lot shorter. doesnt check whether it can payout every round reducing needless function calls

genesis base target = 18325193796
current timestamp 1478721410690
genesis-block blocktime 70999011
genesis-block timestamp 1407722399690
burst pool running on port 8124
websocket running on port 4443
http server running on port 80
new block #293473 BT:1815825 ND:10091.93826277312
new block #293474 BT:1802125 ND:10168.658553651938
new block #293475 BT:1787044 ND:10254.472635256883
Pool Balance = 3135.02294216 BURST
total pending payment amount = -297437.38 pool balance = 3135.02294216netBalance
 = 300572.40294216
storing pending fee payment data for 17572168194578653714 Ammount: 71.51
storing pending payment data for 17572168194578653714 Ammount: 1344.00
storing pending fee payment data for 17572168194578653714 Ammount: 35.76
storing pending payment data for 17572168194578653714 Ammount: 672.00
storing pending fee payment data for 17572168194578653714 Ammount: 17.88
storing pending payment data for 17572168194578653714 Ammount: 336.00
9037319325910335992 payment amount 17.370000000000005 is below payment threshold

8139841036819454640 payment amount 16.420000000000005 is below payment threshold

12497588908633202484 payment amount 6.99 is below payment threshold
14834463895479742872 payment amount 13.409999999999995 is below payment threshol
d
3501633088787745304 payment amount 2.48 is below payment threshold
7811831612493581007 payment amount 1.42 is below payment threshold
10400995181240832668 payment amount -1 is below payment threshold
6238401638398757545 payment amount -1 is below payment threshold
16650910394466232610 payment amount -300004.65 is below payment threshold
4161009231636266338 payment amount -1 is below payment threshold
submitted transaction request, miner payment for  17572168194578653714 amount =
5003.36
17572168194578653714 payment amount 5003.3600000000015 is paid
storing pending payment 18.370000000000005 for 9037319325910335992
storing pending payment 17.420000000000005 for 8139841036819454640
storing pending payment 7.99 for 12497588908633202484
storing pending payment 14.409999999999995 for 14834463895479742872
storing pending payment 3.48 for 3501633088787745304
storing pending payment 2.42 for 7811831612493581007
storing pending payment 0 for 10400995181240832668
storing pending payment 0 for 6238401638398757545
storing pending payment -300003.65 for 16650910394466232610
storing pending payment 0 for 4161009231636266338

Lexicon

applied the code to the live server yesterday. everything went smoothly. updated tross's last night he ran into a few issues due to his own customization's i helped him get things back on track and things have been running smoothly for him since.

also before i started work on this project @tross told me his cpu temperatures were at about 70 degrees and after this last update he noticed its gone down to the 50's. and runs so much smoother. in the next release im adding a block delay option in the config that can be changed but not saved via a command send through the local chat section of the pool so you dont have to restart the pool in order to change this variable..

thinking of additional commands would be useful so im open to suggestions. the current list of commands ive implemented are

config-mode - Toggles between getbalance payout mode and the new blockreward based one that improves performance.
getblock #height - dumps a json screen of the block allocationed with the height variable #height.
getpending - refreshes the pending payments tab
updateonnewblock #height - a command i implemented to test out the new payout method.

Lexicon

made a few more changes. replaced the numerical account id in best deadlines with the account id instead.

also added additional info on the reward the block generates

along with that I've also added in some code to record block winners for each block that passes.
it stores it in a csv file located http://burst.lexitoshi.uk/blockWinner.csv

I've also figured out where i can get the size of the miners. so that will be included in a future update

new login button. another future update is so people can register by the following steps

sending the pool a message with what password they want to set.
then check for the message by issuing a command through the local chat that contains the transaction-id of the message.

this should be a good authentication method if implemented correctly

Lexicon

Latest update to the pool includes;

better integration with google analytics events so it accurately shows session time,
outgoing payment info in the console now shows the burst id instead of the numerical version.
also added the miners total capacity for the share they submitted. if they submit from 2 miners with the same mining address it will show the capacity of the miner that submitted it. .

Future Idea

once implemented the login system display to the user all the nonce's they have submitted for that round. and what the deadlines were. should provide some additional information to the user.
optional alerts users can configure once logged in
* E-Mail - Alerts
1. on miner capacity changes shows users when a drive has been disconnected or stopped working.
2. on block win - emailing them info on what reward they have received.

Lexicon

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.

iKnow0

@Lexicon showing users capacity for each of their miners would be huge.

Lexicon

@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.

iKnow0

@Lexicon Excellent work! Stable and reliable pool code is must for Burst going forward.

Lexicon

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

Lexicon

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

gpedro

@Lexicon That's so cool man... hahahaha

Lexicon

its pretty useful the win alerts come through on discord for my phone. its a nice touch.

gpedro

@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?!

Lexicon

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.

Lexicon

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

Lexicon

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 ;)

http://www.dailysquib.co.uk/business/21520-want-to-get-into-cryptocurrency-burstcoin-is-the-way-forward.html

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

@Lexicon
@nameless give this man a pack of cookies in my behalf haahahaha

nameless

@gpedro cookies are being sent as we speak

Lexicon

@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