[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[norgan]

What's with that last payout? There were two close together then one got revoked and now My wallet is now marked with a warning.
1JKVhFcR8GmwJFixRSeg46eXc7yEq7jzBB

[1714053706]

1714053706

[1714053706]

1714053706

[1714053706]

1714053706

[1714053706]

1714053706

[jonnybravo0311]

IYFTech, you are correct - regtable69, you need to define the math.Object for your coin in both p2pool/networks.py and p2pool/bitcoin/networks.py.

t.y  is it a case of duplicating the info from one to the other?

No.  Your best bet is to reach out to rav3n and see if you can get some help there.  Since his fork has virtually every coin, he's definitely a good resource.  For example, here's the math.Object values for BTC:

p2pool/networks.py:

Code:

    bitcoin=math.Object(
        PARENT=networks.nets['bitcoin'],
        SHARE_PERIOD=30, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=3, # blocks
        IDENTIFIER='fc70035c7a81bc6f'.decode('hex'),
        PREFIX='2472ef181efcd37b'.decode('hex'),
        P2P_PORT=9333,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**32 - 1,
        PERSIST=True,
        WORKER_PORT=9332,
        BOOTSTRAP_ADDRS='forre.st vps.forre.st portals94.ns01.us 54.227.25.14 119.1.96.99 204.10.105.113 76.104.150.248 89.71.151.9 76.114.13.54 72.201.24.106 79.160.2.128 207.244.175.195 168.7.116.243 94.23.215.27 218.54.45.177 5.9.157.150 78.155.217.76 91.154.90.163 173.52.43.124 78.225.49.209 220.135.57.230 169.237.101.193:8335 98.236.74.28 204.19.23.19 98.122.165.84:8338 71.90.88.222 67.168.132.228 193.6.148.18 80.218.174.253 50.43.56.102 68.13.4.106 24.246.31.2 176.31.208.222 1.202.128.218 86.155.135.31 204.237.15.51 5.12.158.126:38007 202.60.68.242 94.19.53.147 65.130.126.82 184.56.21.182 213.112.114.73 218.242.51.246 86.173.200.160 204.15.85.157 37.59.15.50 62.217.124.203 80.87.240.47 198.61.137.12 108.161.134.32 198.154.60.183:10333 71.39.52.34:9335 46.23.72.52:9343 83.143.42.177 192.95.61.149 144.76.17.34 46.65.68.119 188.227.176.66:9336 75.142.155.245:9336 213.67.135.99 76.115.224.177 50.148.193.245 64.53.185.79 80.65.30.137 109.126.14.42 76.84.63.146'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool',
        VERSION_CHECK=lambda v: 50700 <= v < 60000 or 60010 <= v < 60100 or 60400 <= v,
        VERSION_WARNING=lambda v: 'Upgrade Bitcoin to >=0.8.5!' if v < 80500 else None,
    )

And in p2pool/bitcoin/networks.py

Code:

bitcoin=math.Object(
        P2P_PREFIX='f9beb4d9'.decode('hex'),
        P2P_PORT=8333,
        ADDRESS_VERSION=0,
        RPC_PORT=8332,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            (yield check_genesis_block(bitcoind, '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f')) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//210000,
        POW_FUNC=data.hash256,
        BLOCK_PERIOD=600, # s
        SYMBOL='BTC',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Bitcoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Bitcoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.bitcoin'), 'bitcoin.conf'),
        BLOCK_EXPLORER_URL_PREFIX='https://blockchain.info/block/',
        ADDRESS_EXPLORER_URL_PREFIX='https://blockchain.info/address/',
        TX_EXPLORER_URL_PREFIX='https://blockchain.info/tx/',
        SANE_TARGET_RANGE=(2**256//2**32//1000 - 1, 2**256//2**32 - 1),
        DUMB_SCRYPT_DIFF=1,
        DUST_THRESHOLD=0.001e8,
    )

What's with that last payout? There were two close together then one got revoked and now My wallet is now marked with a warning.
1JKVhFcR8GmwJFixRSeg46eXc7yEq7jzBB

Orphaned block.  That's what happened.

[norgan]

Thanks, I had not seen that before.

[jonnybravo0311]

Thanks, I had not seen that before.

No problem.  First time it's happened in a while.  p2pool.info shows blocks for the past couple months, and this morning's is the only orphan in that time.

[windpath]

Thanks, I had not seen that before.

No problem.  First time it's happened in a while.  p2pool.info shows blocks for the past couple months, and this morning's is the only orphan in that time.

I show this mornings block (300503) as in the main chain with 47 confirmations currently....

Edit: Also noticed the "double spend" warning on blockchain.info, this happened with block 300230 as well, may be related to the last non-standard transaction at the end of every P2Pool generation payout?

[pembo210]

..
Edit: Also noticed the "double spend" warning on blockchain.info, this happened with block 300230 as well, may be related to the last non-standard transaction at the end of every P2Pool generation payout?

Yeah, just noticed that too.. Every address in this transaction has the warning attached now.
https://blockchain.info/tx/108e67b1534d16031d3ec38d6eb89bd2a472ed0bb81d4673cc92dfd0706a4574

[windpath]

..
Edit: Also noticed the "double spend" warning on blockchain.info, this happened with block 300230 as well, may be related to the last non-standard transaction at the end of every P2Pool generation payout?

Yeah, just noticed that too.. Every address in this transaction has the warning attached now.
https://blockchain.info/tx/108e67b1534d16031d3ec38d6eb89bd2a472ed0bb81d4673cc92dfd0706a4574

It goes away after 120 confirmations....

[jonnybravo0311]

Which is an accurate assessment of things.  P2Pool relayed block 300520, and all addresses that had submitted shares were paid from the 25BTC reward and transaction fees based upon the normal p2pool payout logic.  Well, it turns out that block 300520 was also submitted by someone else, and that block made it into the main chain, while the p2pool block did not and became orphaned.  Thus the potential double spend.

[windpath]

Cookin' with fire today, the luck gods made up the lost block from this morning

Block 300561
https://blockchain.info/block/00000000000000001519014c914724f3c0b45948d68fef21e62d8b35789e2254

[regtable69]

IYFTech, you are correct - regtable69, you need to define the math.Object for your coin in both p2pool/networks.py and p2pool/bitcoin/networks.py.

t.y  is it a case of duplicating the info from one to the other?

No.  Your best bet is to reach out to rav3n and see if you can get some help there.  Since his fork has virtually every coin, he's definitely a good resource.  For example, here's the math.Object values for BTC:

p2pool/networks.py:

Code:

    bitcoin=math.Object(
        PARENT=networks.nets['bitcoin'],
        SHARE_PERIOD=30, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=3, # blocks
        IDENTIFIER='fc70035c7a81bc6f'.decode('hex'),
        PREFIX='2472ef181efcd37b'.decode('hex'),
        P2P_PORT=9333,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**32 - 1,
        PERSIST=True,
        WORKER_PORT=9332,
        BOOTSTRAP_ADDRS='forre.st vps.forre.st portals94.ns01.us 54.227.25.14 119.1.96.99 204.10.105.113 76.104.150.248 89.71.151.9 76.114.13.54 72.201.24.106 79.160.2.128 207.244.175.195 168.7.116.243 94.23.215.27 218.54.45.177 5.9.157.150 78.155.217.76 91.154.90.163 173.52.43.124 78.225.49.209 220.135.57.230 169.237.101.193:8335 98.236.74.28 204.19.23.19 98.122.165.84:8338 71.90.88.222 67.168.132.228 193.6.148.18 80.218.174.253 50.43.56.102 68.13.4.106 24.246.31.2 176.31.208.222 1.202.128.218 86.155.135.31 204.237.15.51 5.12.158.126:38007 202.60.68.242 94.19.53.147 65.130.126.82 184.56.21.182 213.112.114.73 218.242.51.246 86.173.200.160 204.15.85.157 37.59.15.50 62.217.124.203 80.87.240.47 198.61.137.12 108.161.134.32 198.154.60.183:10333 71.39.52.34:9335 46.23.72.52:9343 83.143.42.177 192.95.61.149 144.76.17.34 46.65.68.119 188.227.176.66:9336 75.142.155.245:9336 213.67.135.99 76.115.224.177 50.148.193.245 64.53.185.79 80.65.30.137 109.126.14.42 76.84.63.146'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool',
        VERSION_CHECK=lambda v: 50700 <= v < 60000 or 60010 <= v < 60100 or 60400 <= v,
        VERSION_WARNING=lambda v: 'Upgrade Bitcoin to >=0.8.5!' if v < 80500 else None,
    )

And in p2pool/bitcoin/networks.py

Code:

bitcoin=math.Object(
        P2P_PREFIX='f9beb4d9'.decode('hex'),
        P2P_PORT=8333,
        ADDRESS_VERSION=0,
        RPC_PORT=8332,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            (yield check_genesis_block(bitcoind, '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f')) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//210000,
        POW_FUNC=data.hash256,
        BLOCK_PERIOD=600, # s
        SYMBOL='BTC',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Bitcoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Bitcoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.bitcoin'), 'bitcoin.conf'),
        BLOCK_EXPLORER_URL_PREFIX='https://blockchain.info/block/',
        ADDRESS_EXPLORER_URL_PREFIX='https://blockchain.info/address/',
        TX_EXPLORER_URL_PREFIX='https://blockchain.info/tx/',
        SANE_TARGET_RANGE=(2**256//2**32//1000 - 1, 2**256//2**32 - 1),
        DUMB_SCRYPT_DIFF=1,
        DUST_THRESHOLD=0.001e8,
    )

What's with that last payout? There were two close together then one got revoked and now My wallet is now marked with a warning.
1JKVhFcR8GmwJFixRSeg46eXc7yEq7jzBB

Orphaned block.  That's what happened.

cheers dude i kinda figured it out just need to isolate a few lines of code which are spuriously placed. supposedly in the main.h but missing. found similar code in another file. think what i will do is reverse engineer a coin so take one from ravens source grep all the codes/lines in ravens and take note of the lines there on and which files. maybe just maybe il have a huc and bns p2pool running. just hope i can handle the traffic 8mb ram octocore amd. 75mb tinterwebs. should be plenty right>?

Code:

 RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            (yield check_genesis_block(bitcoind, '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f')) and
            not (yield bitcoind.rpc_getinfo())['testnet']

its that im struggling with mainly lol.
and then the algo for it as each one seems fdifferent

[squashpile]

Rock and Roll

Very nice
Block #300600 up
https://blockchain.info/block/000000000000000004c7e013d3f07843c6862111256e6276710fe701eea63101

[jonnybravo0311]

Cookin' with fire today, the luck gods made up the lost block from this morning

Block 300561
https://blockchain.info/block/00000000000000001519014c914724f3c0b45948d68fef21e62d8b35789e2254

And another one!  300600.  If only my miners weren't acting like they are on strike today and only finding like 7 shares in the past 30 hours...

EDIT: squashpile beat me to it

[squashpile]

heh
Your last post post got me fired up!

Cookin' with fire today, the luck gods made up the lost block from this morning

Block 300561
https://blockchain.info/block/00000000000000001519014c914724f3c0b45948d68fef21e62d8b35789e2254

And another one!  300600.  If only my miners weren't acting like they are on strike today and only finding like 7 shares in the past 30 hours...

EDIT: squashpile beat me to it

[jonnybravo0311]

cheers dude i kinda figured it out just need to isolate a few lines of code which are spuriously placed. supposedly in the main.h but missing. found similar code in another file. think what i will do is reverse engineer a coin so take one from ravens source grep all the codes/lines in ravens and take note of the lines there on and which files. maybe just maybe il have a huc and bns p2pool running. just hope i can handle the traffic 8mb ram octocore amd. 75mb tinterwebs. should be plenty right>?

Code:

 RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            (yield check_genesis_block(bitcoind, '000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f')) and
            not (yield bitcoind.rpc_getinfo())['testnet']

its that im struggling with mainly lol.
and then the algo for it as each one seems fdifferent

That is checking to make sure you're actually connecting to the proper daemon on the designated port.  So, if you've defined the SpongeBobCoin, you'd do something like this:

Code:

 
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
    'spongebobcoinaddress' in (yield bitcoind.rpc_help()) and 
    (yield bitcoind.rpc_getinfo())['testnet']
))

Someone more knowledgable than me would be able to help you out further.

Regarding your question about HUC and BNS... mdude77 tried to get HUC up and running merge mining with BTC on p2pool, but ended up taking it down because of random disconnects and errors with the coin.  He might be able to give you specifics on what the problems were with the setup.  I'm not sure if you'd face similar problems just running a standard p2pool node with it, however.

[norgan]

yeeehh harrrrr p2pool is like a bucking bull at a rodeo. buck an orphan off but slam down a couple to make up for it. AND someone has started hashing on my node so boosted the hash rate by quite a bit. Good for node sats

[norgan]

only unfortunate thing is my merged coins do not seem to be paying out to the wallets. I see new work for merged coming in but doesn't seem to be dumping any in the wallets. IT used to work. Any known gotchas that may stop merged coins from paying out?

[jonnybravo0311]

only unfortunate thing is my merged coins do not seem to be paying out to the wallets. I see new work for merged coming in but doesn't seem to be dumping any in the wallets. IT used to work. Any known gotchas that may stop merged coins from paying out?

You have to find shares of high enough difficulty to solve a block of the merged coins.  If you happen to find the share that solves the BTC block, then by default you'll also find blocks of every coin you're merge-mining because the BTC hash will satisfy every other one.

Effectively you're solo mining the merged coins.

[regtable69]

hi guys iv finally got a coin live. just cannot get it to connect from my miner on another network. how the heck do i do it lol iv forwarded parts and that cant find a decent guide without doge coin being mentioned 7 billion times

[norgan]

hi guys iv finally got a coin live. just cannot get it to connect from my miner on another network. how the heck do i do it lol iv forwarded parts and that cant find a decent guide without doge coin being mentioned 7 billion times

What coin are you trying to set up?

[regtable69]

hi guys iv finally got a coin live. just cannot get it to connect from my miner on another network. how the heck do i do it lol iv forwarded parts and that cant find a decent guide without doge coin being mentioned 7 billion times

What coin are you trying to set up?

i was trying to set up bonus and hunter coin. but the bonus dev has told me the coder knows theres major issues with his code reg p2p pools. and huc well its a beast!
i have just set up a joulecoin p2p pool currently testing it with my rig that is hosted at a friends house. everythings set up i think router wise. p2pool is spitting out spurious crud looking for workers so fingers crossed it works