Lex Pool (A rewritten pool based on uray source)



  • Pool down?



  • Hello Guys,

    I'm trying to get a pool started but I'm having two issues. The first one is a Running out of memory error:

    FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

    I was able to workaround it by starting the pool like this:
    node --max-old-space-size=4096 burst-pool.js

    However, I see that some people are able to start it without that and even with npm start.

    The second is the website not displaying data reported before but nothing has worked for me. I tried downloading the socket.io.js, disabling firewall, etc.

    I'm using node v4.7.1 and npm v2.15.11

    Config:

    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 : '??????',
         poolPublicRS : 'BURST-####',
           poolPublic : '###',
           poolFeePaymentAddr : '####',
        defaultPaymentDeadline : 1440,
        poolFeePaymentTxFeeNQT : 100000000,
        httpPort : 80,
        websocketPort : 4443,
        enablePayment : true,
        minimumPayout : 50.0,
        clearingMinPayout : 2.0,
        lastSessionFile : 'last-session.json',
        cumulativeFundReduction : 0.5,
        logWebsocketToConsole : false,
        maxRoundCount : 97,
        sharePenalty : 0.001,
        maxRecentPaymentHistory : 50
    };
    
    /*
    SubmitNonce = {
          secretPhrase, (private-key) ---> secretAccount (public-key)   <----------+
      +-- nonce,                                                                   |
      |   accountId ---> getRewardRecipient() ---> rewardId (public-pool-address) -+
      |            |                                  ^
    } |            |                                  |
      V            V                                  |
    nonce + genAccount                                |
      |            |                                  |
      +____________+                                  |
             |                                        |
             V                                        |
         Deadline                                     |
             |    (if smallest)                       |
             V                                        |
         Forge() ------> getRewardRecipient() --------+
     */
    

    Thanks!!



  • Sounds like computer too small for both wallet and pool. I have never seen that problem!



  • @tross said in Lex Pool (A rewritten pool based on uray source):

    Sounds like computer too small for both wallet and pool. I have never seen that problem!

    Thanks. What are the requirements? I tried on an old Xeon server with 12 GB of RAM and on a new gen Core i7 with 16GB. I can split the wallet and pool to make sure.

    Any ideas on the web not displaying anything?



  • @ElMoreno said in Lex Pool (A rewritten pool based on uray source):

    @tross said in Lex Pool (A rewritten pool based on uray source):

    Sounds like computer too small for both wallet and pool. I have never seen that problem!

    Thanks. What are the requirements? I tried on an old Xeon server with 12 GB of RAM and on a new gen Core i7 with 16GB. I can split the wallet and pool to make sure.

    Any ideas on the web not displaying anything?

    for some reason, the code is supplied with a socket.io file that doesn't work. At least not for me. Look back in this thread when I was asking a lot of questions, Lex told me to download a different socket.io and it started to work( web page update).



  • I have a quick question for those running this. How exactly are the pending payments calculated? I was under the impression that even though the pool does not find a block, based upon user submitted shares, the pending payments would go up. I ask because I'm currently testing this pool software and after several hours, pending payments is still 0.



  • @Lunyyft ,

    Good luck with this original version of the code. If you look at upgraded versions, like ckr you will see pending payments are only recorded when the pool wins a block and the share for the miner is below the min payout.



  • @rds thanks for the heads up.



  • @Lunyyft said in Lex Pool (A rewritten pool based on uray source):

    @rds thanks for the heads up.

    No problem. What you may have been thinking is that the "shares" for ultimate block payout are continuously calculated regardless of the block being won or not, not deferred payments.



  • http://burstrenegade.zone/

    Example of CKR pool version. Its like a fork from Lexicons pool code. Both are good and each has an advantage. CKR pool code stores Historic shares for (My pool) 362 rounds and will stay until which they should slowing go down. Couple other things are also different so will have to check it out yourself!


Log in to reply
 

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