Bitcoin Forum
May 30, 2024, 01:45:50 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: P2Pool for Fuelcoin.  (Read 1732 times)
infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 01, 2014, 09:26:46 PM
Last edit: July 01, 2014, 10:10:04 PM by infernoman
 #1

Hey guys i have setup a p2pool for fuelcoin and for the past week i was having alot of problems. not knowing about setting the difficulty manually on my miners they were submitting alot of false shares. and after an hour or two the latency to the fuelcoin-qt would lag like crazy. up to 40 seconds at some times, right now i beleive i have everything working okay and i have about 1th/s on the fuel p2pool at http://99.236.215.227:9222/static/index.html

a friend of mine also is mining with me and only has about 10gh/s but he is getting close to the same payouts as i am. so i am looking for a bit of help to get the payouts working properly. maybe my networks.py arent quite setup right. but these options im using seem to have worked the best for me.

another thing i would like the fix is that the local hashrate displays about 5x lower than it should be and im wondering if there are any options i could change to get it to display more correctly.

payouts are spread across 150 blocks. if im reading correctly with a 15 second share period. with a lower share period the share difficulty drops too low and causes alot of latency to the fuelcoin-qt.


here is my networks.py in the p2pool folder

 fuelcoin=math.Object(
        PARENT=networks.nets['fuelcoin'],
        SHARE_PERIOD=15, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=100, # shares
        SPREAD=60, # blocks
        IDENTIFIER='a284bd84f219c63d'.decode('hex'),
        PREFIX='dac528561fd653ec'.decode('hex'),
        P2P_PORT=9111,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**32 - 1,
        PERSIST=False,
        WORKER_PORT=9222,
        BOOTSTRAP_ADDRS='98.174.25.28 173.230.51.38 173.230.49.15 173.79.134.197 63.170.87.173'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-fuel',
        VERSION_CHECK=lambda v: True,
        VERSION_WARNING=lambda v: 'Upgrade Fuelcoin to >=0.8.5!' if v < 80500 else None,
    ),


and my networks.py in the bitcoin folder

    fuelcoin=math.Object(
        P2P_PREFIX='f5d3a3d0'.decode('hex'),
        P2P_PORT=9111,
        ADDRESS_VERSION=36,
        RPC_PORT=9222,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'FuelCoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 1000*100000000,
        POW_FUNC=data.hash256,
        BLOCK_PERIOD=30, # s
        SYMBOL='FUEL',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Fuelcoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Fuelcoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.fuelcoin'), 'fuelcoin.conf'),
        BLOCK_EXPLORER_URL_PREFIX='https://usecryptos.com/blockexplorer/FUEL/',
        ADDRESS_EXPLORER_URL_PREFIX='https://usecryptos.com/blockexplorer/FUEL/',
        TX_EXPLORER_URL_PREFIX='https://usecryptos.com/blockexplorer/FUEL/',
        SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
        DUMB_SCRYPT_DIFF=1,
        DUST_THRESHOLD=0.03e8,

we are offering a 200k fuel bounty to help us fix the p2pool for fuel. to get it to display the proper hashrates aswell as the payouts.

i am open to opinions about the fuelcoin-qt latency aswell. and anything to lower the bandwidth should help.

i have changed the fuelcoin.conf file to

rpcuser=
rpcpassword=
rpcport=9234
port=9123
rpcthreads=12
addnode=98.174.25.28
addnode=63.170.87.173
addnode=173.230.51.38
addnode=173.230.49.15
addnode=173.79.134.197
addnode=24.125.152.70
addnode=99.236.215.227
server=1
gen=0
listen=1
blockmaxsize=2500000
mintxfee=0.00001
minrelaytxfee=0.00001
maxconnections=10



this p2pool is running on a 6 core intel 3930k overclocked and watercooled with 32gb of ram. the fuelcoin-qt and the p2pool are both running at high priority on a ram accelerated disk that is capable of 5000mbps in/out
and the internet connection i am using is 250mbps down / 15 mbps up

QOS is not currently set as i cant figure out how to get QOS setup on the pfsense server i am running as my router.
the firewall/router is a 2xdual core server running pfsense as the operating system controlling connections.


ANYONE WHO CAN HELP CAN CONTACT ME HERE ON TWITTER @clark_alastair
OR IN THE #GARAGE FREENODE IRC

CartmanSPC
Legendary
*
Offline Offline

Activity: 1270
Merit: 1000



View Profile
July 02, 2014, 12:13:24 AM
 #2

Try taking out:

mintxfee=0.00001
minrelaytxfee=0.00001

and see if that improves your latency. It is mostly likely the source of it.

Edit: Also I'm not familiar with rpcthreads or gen but I don't use them..I also don't use maxblocksize.

infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 02, 2014, 03:36:23 AM
 #3

Try taking out:

mintxfee=0.00001
minrelaytxfee=0.00001

and see if that improves your latency. It is mostly likely the source of it.

Edit: Also I'm not familiar with rpcthreads or gen but I don't use them..I also don't use maxblocksize.

okay i will try that tomorrow. i added those in to try and help with the latency.

can you explain the worker difficulty to me a bit better by chance?
because when i added /220+220 to my worker name the latency started to smooth out. but the shares dont come as often.'

and one more question.. any way i can get the local rate to display properly? because when i rent miners, in the dashboard of the rental. it also only shows the local rate. so the renter usually thinks something is wrong and tries to fix it. resulting in downtime on the rental.

i think the latency has started to even itself out once i added the /220+220 to each antminer address. and the payouts are starting to return to normal. earlier today the 10gh/s miner was making more than my 1th/s miner
infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 02, 2014, 05:18:40 AM
 #4

fuelcoin=math.Object(
        PARENT=networks.nets['fuelcoin'],
        SHARE_PERIOD=15, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=100, # shares
        SPREAD=60, # blocks
        IDENTIFIER='a284bd84f219c63d'.decode('hex'),
        PREFIX='dac528561fd653ec'.decode('hex'),
        P2P_PORT=9111,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**32 - 1,
        PERSIST=False,
        WORKER_PORT=9222,
        BOOTSTRAP_ADDRS='98.174.25.28 173.230.51.38 173.230.49.15 173.79.134.197 63.170.87.173'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-fuel',
        VERSION_CHECK=lambda v: True,
        VERSION_WARNING=lambda v: 'Upgrade Fuelcoin to >=0.8.5!' if v < 80500 else None,
    ),


and my networks.py in the bitcoin folder

    fuelcoin=math.Object(
        P2P_PREFIX='f5d3a3d0'.decode('hex'),
        P2P_PORT=9123,
        ADDRESS_VERSION=36,
        RPC_PORT=9234,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'FuelCoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 1000*100000000,
        POW_FUNC=data.hash256,
        BLOCK_PERIOD=30, # s
        SYMBOL='FUEL',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Fuelcoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Fuelcoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.fuelcoin'), 'fuelcoin.conf'),
        BLOCK_EXPLORER_URL_PREFIX='https://usecryptos.com/blockexplorer/FUEL/',
        ADDRESS_EXPLORER_URL_PREFIX='https://usecryptos.com/blockexplorer/FUEL/',
        TX_EXPLORER_URL_PREFIX='https://usecryptos.com/blockexplorer/FUEL/',
        SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
        DUMB_SCRYPT_DIFF=1,
        DUST_THRESHOLD=0.03e8,

rpcuser=
rpcpassword=
rpcport=9234
port=9123
rpcthreads=12
addnode=98.174.25.28
addnode=63.170.87.173
addnode=173.230.51.38
addnode=173.230.49.15
addnode=173.79.134.197
addnode=24.125.152.70
addnode=99.236.215.227
server=1
gen=0
listen=1
blockmaxsize=2500000
mintxfee=0.00001
minrelaytxfee=0.00001
maxconnections=10



it also seems i had my ports set wrong on the networks.py in the p2pool/bitcoin folder. they were the same ports as the p2pool/networks.py and someone pointed that out to me. i changed the ports on the p2pool/bitcoin folder to correspond with the fuelcoin daemon.

ports 9123 and 9234 are the ports im using for the fuelcoin daemon. but they are originally 9111 and 9222. but i didnt know how to setup the pool properly so i kept them the same originally.

now ports 9123 and 9234 are for the fuelcoin daemon and are listed in the p2pool/bitcoin/networks.py
and im currently using ports 9111 and 9222 for the p2pool.

also just to verify the rpcthreads=12 is how many threads of the cpu that the daemon is able to use. i increased it to put the work load across all 6 cores of my pc. gen=0 is usually for solo mining from the wallet. but when changed to gen=1 it uses your cpu to mine solo from the wallet.
infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 02, 2014, 05:47:58 AM
Last edit: July 02, 2014, 02:47:25 PM by infernoman
 #5

payouts are back to normal. it seems that the miner just happened to get EXTREMELY lucky lmfao. so payouts are good still.

im going to check tomorrow again but the latency seems to have evened out after changing that and a few other things.
now i just need to get the local rate to display properly. and try and get an out of network miner to connect.

why is it that the other p2pools seem to display hashrate okay but this one does not? is it because of the shares submitted?
and do you know of any way i could try to fix the cdisplayed local rate.


nope =/ looks like the latency took a shit last night and the same thing happened. im going to try and remove those options now you told me
infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 02, 2014, 07:42:52 PM
 #6

okay well it seems when the latency takes a shit the payouts also go a bit haywire. the 10 gh/s miner is making 3/4 of each block. while i am only making 1/4...
CartmanSPC
Legendary
*
Offline Offline

Activity: 1270
Merit: 1000



View Profile
July 02, 2014, 09:58:53 PM
 #7

can you explain the worker difficulty to me a bit better by chance?

http://xpool.net/faq.html

infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 02, 2014, 10:18:22 PM
 #8

alright well i am using psuedo share and share difficulty on my antminer s1's but i am getting aggravated that i am not able to figure this out.  the local rate is not displaying properly. and the pool rate is no longer showing correct. i had 1th/s on the pool. and the 10gh/s miner was getting better payouts than i was. so i was basically giving away my mining power. so i desperately need some help with this. unless im using the p2pool for solo mining. right now there is no point to throw my 1 th/s at it.

i thought i had everything figured out last night... payouts were returning to normal. and then the latency spiked to around 4 seconds. while i was sleeping and again the payouts started to reverse. i just dont understand what ive done wrong.
infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 08, 2014, 03:18:14 PM
 #9

i am still having no luck with this. the expected time to share rate is not following the configuration file and the local rate is not following the amount of hashpower i have on the pool. i have the only p2pool that is configured and running currently. the pool rate is also inconsistent with the amount of hashpower i have causing the share difficulty to drop substantially causing the large amount of doa's and causing the latency
infernoman (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1000



View Profile
July 11, 2014, 01:16:56 AM
 #10

it seems that every single one of my p2pools that i try to create for new coins aswell as bitcoin. the local rate is displaying incorrectly. i am trying to load down a p2pool for a different coin to see if the latency problem occurs.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!