Lex Pool (A rewritten pool based on uray source)



  • @pr0cesor hi buddy ive been away from this thread for a while however if you follow the guide above it should get you started on setting up.



  • @Lexicon That's sad m8, pissing me off reading something like this. Did u contact the webmaster of the pool? Is there anything we can do to shut it down or at least to force him giving u credit instead of stealing ur work?



  • This post is deleted!


  • This post is deleted!


  • @Lexicon Yeah I saw it, why don't u make an announcement in return about the pool and the code he is using. His pool does not deserve miners if he does not know what honesty means.



  • @Lexicon hi, been running your pool code locally, i cannot seem to understand the payouts,
    from what i can gather, the pool is treated like another miner?
    a block is found, miners get paid,pool gets paid and yet an amount is retained in pool account. Could you shed any light on this.



  • @iKnow0 the pool keeps a threshold for each user to save on tx fee's that could be what your seeing. also rounding tends to leave a bit over as well.



  • @Lexicon where can i set the threshold in the config or is it hard coded?



  • @iKnow0 If you are using the Lex's their is only one line to worry about.

    cumulativeFundReduction : 0.5,

    Lower than .5 will give more to the reward finder. Then to the miners. These pools are designed to pay every miner once they reach their threshold. Again pay happens when a block is found. More blocks more miner get paid.
    TX fee is included with reward and is shown on the pool console. this one might be different but gives you and idea. Everyone get a share of that block.
    0_1488654083580_upload-98daed97-7528-4327-b933-6ec6b62dd7b5



  • @Burstde So on my pool, if I want to give less reward to the block finder, and more to the miners, would I set that number higher or lower?



  • @Lexicon Hi Lex,
    I've been trying to get the my pool running, but for some reason I don't get any data on my website.
    My wallet is running and syncd, pool is running and grabbing blocks.
    Tried all versions of nodejs listed in this thread (v4.4.7 and forward) with no success.
    I've also tried running Uray's pool but the same result.

    Here's a screenshot of my screens with everything running

    Looking forward to your reply :)

    0_1492791385310_Screenshot from 2017-04-21 18-10-24.png



  • A bigger image is easier to see lol I do the same.

    Copy and paste the pool conf BUT ERASE THE PASSPHRASE PLEASE!

    Also what ports do you have forward?



  • module.exports = {
        wallets : [
            {
                walletIP : '127.0.0.1',
                walletPort : 8125,
                walletUrl : 'http://127.0.0.1:8125'
            }
        ],
        redirection : {
            enabled : false,
            target : 'http://lhc.ddns.net:8124'
        },
        walletIndex: 0,
        blockMature : 1,
        txFeePercent : 0.0005,
        devFee : true,
        devFeePercent : 0.01,
        poolFee : 0.0015,
        poolDiff : 1000000,
        poolDiffCurve : 0.75,
        poolPort : 8124,
        poolPvtKey : 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
        poolPublicRS : 'BURST-FK53-NKRM-42M2-32XJP',
        poolPublic : '1928561693545645153',
        poolFeePaymentAddr : '1928561693545645153',
        defaultPaymentDeadline : 1440,
        poolFeePaymentTxFeeNQT : 100000000,
        httpPort : 80,
        websocketPort : 4443,
        enablePayment : true,
        minimumPayout : 250.0,
        clearingMinPayout : 2.0,
        lastSessionFile : 'last-session.json',
        cumulativeFundReduction : 0.5,
        nextBlockFundSaving : 0.5,
        logWebsocketToConsole : false,
        maxRoundCount : 97,
        sharePenalty : 0.001,
        maxRecentPaymentHistory : 50
    };
    

    and here is the port forward config from my router

    D 	Service Port 	Internal Port 	IP Address 	Protocol 	Status 	Modify
    1	80	            8080	192.168.1.20	TCP	        Enabled	Modify Delete
    
    


  • Do you have port 8080, 8125, 8124, 8123, 4443 Port forward for your pool and wallet? install latest jre and nodejs 4.4.7 and it should at least work locally. The rest you already know I assume.



  • I've got the latest jre and nodejs 4.4.7
    Tried setting the http port to 8080 in the pool config but then the script fails with this error

    gazda@ubuntu16:/var/www/burstpool$ sudo node burst-pool.js
    genesis base target = 18325193796
    current timestamp 1492949663312
    genesis-block blocktime 85227263
    genesis-block timestamp 1407722400312
    burst pool running on port 8124
    websocket running on port 4443
    Error: listen EADDRINUSE :::8080
        at Object.exports._errnoException (util.js:907:11)
        at exports._exceptionWithHostPort (util.js:930:20)
        at Server._listen2 (net.js:1253:14)
        at listen (net.js:1289:10)
        at Server.listen (net.js:1385:5)
        at EventEmitter.app.listen (/var/www/burstpool/node_modules/express/lib/application.js:559:24)
        at initWebserver (/var/www/burstpool/burst-pool-protocol.js:202:9)
        at Object.module.exports.start (/var/www/burstpool/burst-pool-protocol.js:262:13)
        at /var/www/burstpool/burst-pool.js:236:30
        at /var/www/burstpool/node_modules/async/lib/async.js:254:17
    clean
    

    Is that maybe the problem? Also, I honestly don't know where I should be setting up these port forwards for my localhost, somewhere in apache?
    Would you share your web server config with me please?



  • ok 2 things I had to do to get my pool to work on my vpu (ubuntu) 1 I had to start the pool as root 2 I had to make sure all was in lower case in the client folder (think charts.js was Charts.js) If I think of anything else I will tell you.

    Actually you only have to do that. When my vps is going for maintenance I go to webmin download pool and just have to start it and it works. My server at home is windows so the code works both ways. Those other ports have to be open too or it will only work local.



  • I try a test pool at home on a different port like 8081. edited works with other port. I would try what I said about root.

    edit I talked to lexicon and he reminded me its Charts has to be in lower case in the client file!



  • "charts" is the solution. :-)
    Thank you both for your time.



  • I too am have the no data on the site problem opened all the port mentioned above changed the C to c although I don't think it matters on windows I also made sure I ran burst-pool.js as admin and I am kinda out of ideas at this point any help would be greatly appreciated.
    0_1495344570714_cmd.png 0_1495344584943_localwallet.png 0_1495344607915_node.png 0_1495344628575_sitelocal.png 0_1495344652341_sync.png

    //module.exports = {
        wallets : [
            {
                walletIP : '127.0.0.1',
                walletPort : 8125,
                walletUrl : 'http://127.0.0.1:8125'
            }
        ],
        redirection : {
            enabled : false,
            target : 'http://lhc.ddns.net:8124',
        },
        walletIndex: 0,
        blockMature : 1,
        txFeePercent : 0.0005,
    	devFee : true,
    	devFeePercent : 0.01,
        poolFee : 0.01,
        poolDiff : 1000000,
        poolDiffCurve : 0.75,
        poolPort : 8124,
        poolPvtKey : 'Wallet Passphase here',
         poolPublicRS : 'BURST-BYHH-ETPK-49NE-BJUVV',
           poolPublic : '11380403184201955823',
           poolFeePaymentAddr : '8753115353486582411',
        defaultPaymentDeadline : 1440,
        poolFeePaymentTxFeeNQT : 100000000,
        httpPort : 80,
        websocketPort : 4443,
        enablePayment : true,
        minimumPayout : 250.0,
        clearingMinPayout : 2.0,
        lastSessionFile : 'last-session.json',
        cumulativeFundReduction : 0.5,
        logWebsocketToConsole : false,
        maxRoundCount : 800,
        sharePenalty : 0.001,
        maxRecentPaymentHistory : 50``


  • try node.js 4.4.7 otherwise looks correct. I would change the maxroundcount to 360 I ran 180 for the longest time but dropped it to cut down whats loading every block.


Log in to reply
 

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