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



  • @BenBurst sure dm me. ive seen both the issue on my pool and tross pool its less frequent on mine but happens a lot more on his due to the amount of miners he has gives it a greater chance on happening



  • @BenBurst has also seen the minus in his pool. it happened in the past 24 hours.

    ive made another change to fix this. what i've done is make it so each block it only sends out less than a value that's now set in the config..

    so if the value in the config is 2000 once the payments hit a transaction that pushes it over 2k it will split the last payment removing any extra and saving that for the next round.
    this coincides with my prior update where the balance isn't shared out unless the value goes over 2000.

    an example of this is if a block's value was 2.5k and i had to miners a and b the payout would look like this if miner a got shared 1k and b got 1.5k

    Block1
    Pay a 1000
    Pay b 1000
    Block 2
    pay b 500
    


  • @jervis @Lexicon As an owner of a pool
    Ninja Code is just a web design over exist uray code. All I have to do is change my css and index file to theirs and 90 percent of it will work. My pool has 4 different web looks and while the pools is running I can switch to them without any problems except the miners wonder which pool are they mining on.

    I am all for a more revised and truer pool code from us as the user who can make a statement against the Ninja type codes pools who I'm guessing have to workout a deal to get the code.

    The people of uray code are free from this and will rise up against the machine.



  • @Lexicon @jervis I often wondered about virtual round shares and what are they and why isn't it real shares. I think that if I sent you 3000 coins the the exchange. The pool that mines the transaction divides the virtual share of 3000 to the miners for their work to help send the transaction and then you get paid according to your share work. The newer ninja pools just hide that part.



  • @Burstde I'm still wondering, what is really wrong with the pools running right now (ninja clones)? The only problem I have with Uray is that I don't understand it. Maybe if there's a real description on Uray (maybe there is but I haven't seen it) then maybe I would be inclined to mine in Uray. In a ninja clone, I can easily see how much burst i have at the moment (1456D) or is it paying at the moment (1456U) or how much will I get (percentage) when we win the block. I don't see it in a uray pool or I'm just blind and dumb and stupid enough to not see it, but I can't. I can't even see if we won a block or not.



  • @jervis Thats funny I don't know either as far as who wins the block. I look at the round shares when they are at 1 then goto a ninja pool and look for the miner from my pool, then announce it at the chat(sometimes).
    If I missed a day of watching the pool then I click on each persons address to see which ones found a block under 24 hours ago, then announce it that way.

    Usually for who is inline to be paid its written in the pending payment of the code and I can see it. You can see at least where you are to the left of the current round shares under someones address. So ninja just calculated it for you and showed it as (1456D) So maybe they crash because they need to calculate too much.

    Lex and Tross refined better so try their pools



  • @Burstde I had tried @tross pool before and that's the problem I have. The information that I want is not there that's why I went out and joined a ninja pool. Those informations should be integrated in a Uray pool to be able to compete with a ninja clone (in my perspective). Because, I'm just an average joe. If I see it like that, then maybe some average joes like me that wanted to mine in a ninja clone because of those reasons might be thinking the same way as I am. Even though how cool your codes are or even if you say that your pools (uray) don't crash or payments are faster, if you have don't have those informations that we need, we're painstakingly staying with a pool that is problematic because those factors are in place.

    maybe if you integrate those in a Uray pool, then Ninja clones would up their game and upgrade their codings too.



  • I`m on Tross Pool,,but i agree with Jervis,Ninja is easy to understand,not like Uray,more problems to understand that one.



  • Well the people have spoken.........next week I''l work on it on my cloud pool and after I get my pool running like it was before the internet fiasco.
    then I'll show Tross and Lex



  • The problem is patience ! A nice looking car needs a nice looking engine! Both Lexicon and I have visions of where are sites are going! Our sites will have the exact information and more! Our set up allows flexibility and change! I like diversity not a handful of ninja clones than make me think of I Robot! one looking just like the other. It rather funny cause I was working on block winner code today lol I am not a web designer or code programmer but I like to doodle and sometime it is right. For the time being mine where you get burst not block information.



  • lol. it's only some html nothing big. i'll make some changes. its on the list cause a few friends also found it difficult



  • @tross it's fun too.



  • @jervis this is also on the list. what i usually do to find the block winner is look in recent payments the block winner usually has the highest amount.
    displaying block winner however is also on the list and something i've been looking at. however generally displaying this info is a "nice to have" rather than a need to have. but i can't see how being with a uray pool is problematic with or without the information the members of the pool still get paid. and the underlying code is more or less the same.

    problematic would mean the pool has a big issue that makes its functionality worse than other pools.

    on a another note.
    one thing you won't see of a ninja pool is the giveaways we do. i've spent 10k burst so far sending to the pool to test code due to the qty of miners making it hard to test for bugs and issues. this burst has gone to the miners as a bonus for their time. and me and @tross are planning a joint giveaway in the upcoming weeks where we will be sending the pool 3,000 burst every 3 hours for 1 day each. with the exception of when we are asleep.



  • @bandarfjb wow that's a first. Just out of curiosity and don't change your current reward assignment s. Try burstcoin.uk and pool.burstcoin.de to see if you get The same message.



  • @Burstde @bandarfjb hi both. i've already let him know that the new address should not be blocked. it was due to using No-IP as a Host provider. some ISP's block them.
    i have since bought a VPS and changed hostnames so it should all work now.

    i did mention this in the post immediately after his
    0_1477558151156_upload-cc99a515-3555-41c5-bc45-681c0046ced7

    i also made a few more tweaks last night and made it show the last block winner in the console.

    this will show regardless on if the winner is assigned to my pool or not. next step is having some text next to it stating if they belong to the pool.
    also added some headings to the various box's on the right
    0_1477558322092_upload-c9508300-827e-4b51-a5b3-46df478e21b6



  • had a major issue with the wallet. over the weekend. its just caught back up. so development has been paused. however i plan on starting some changes tonight.

    the problem i had with the wallet and seem to still have is that the wallet downloads 5000 blocks and stops then errors an hour later but as soon as i kill the wallet with ctrl + c it displays the error there and then if i dont wait. i then open it back up and it continues.



  • hi all.

    pool was down today. ive moved hosts to a better vps at a cheaper price. the other vps seemed to crash after half an hour. they emailed me back in regards to the disk speed and they said they are making changes to the node. however they have taken the piss in getting back to my support message so im going to cancel that service today with immediate effect.

    if your having trouble connecting open command prompt. and type "ipconfig /flushdns"

    this should then resolve the address to the new dns records i changed this morning.

    in comparison. the new vps downloaded the entire block-chain in 8 hours. the old one took 4 days! and crashed every 5000 blocks. the new one didn't crash once

    sorry for all the inconvenience

    EDIT:

    i ended up sending the old host an email stating i wanted a full refund. and i managed to get it. #win. makes me feel better knowing that i haven't spend as much on developing this source.



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

    0_1478512154160_upload-c15f3b11-30dd-4588-8de1-fb6f4942ff59 0_1478513805939_upload-6c7b75b3-34a7-48a9-80cd-cf4ad7ae9c29



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

    0_1478722921161_upload-65f4215f-116a-4d41-b9c2-1aa0bf18f170 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
    0_1478722468421_upload-ba1be806-dc56-49fa-b937-cfa1b9ed757d

    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
    
    


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


Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.