Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 107. (Read 2591920 times)

sr. member
Activity: 266
Merit: 250
Should probably ask in the emark thread in the altcoins section.

-------------------------------------------------------------

Is anyone running the Bitcoinclassic wallet with p2pool here? I was checking the github repo out & after seeing the trolling being done by a certain core dev & ex-pool admin it makes me want to start using it...... Cheesy
legendary
Activity: 986
Merit: 1027
Miner-Control.de Pooler
Hy,

i made a p2pool for the altcoin emark.

But the Block value is wrong, and i dont know how to correct this or all my variables are correct.

Right block value is 50DEM
in p2pool the block is 0.50DEM

The pool speed is wrong, too. i think i have the only pool running.....

https://miner-control.de/p2pool/emark/

Code:
from p2pool.bitcoin import networks

PARENT = networks.nets['emark']
SHARE_PERIOD = 24 # seconds
CHAIN_LENGTH = 7*24*60*60//10 # shares
REAL_CHAIN_LENGTH = 7*24*60*60//10 # shares
TARGET_LOOKBEHIND = 20 # shares
SPREAD = 15 # blocks
IDENTIFIER = '6012865EBAD2C803'.decode('hex') #654d61726b
PREFIX = ''.decode('hex')
P2P_PORT = 5556
MIN_TARGET = 0
MAX_TARGET = 2**256//2**32 - 1
PERSIST = False
WORKER_PORT = 5557
BOOTSTRAP_ADDRS = 'miner-control.de'.split(' ')
ANNOUNCE_CHANNEL = '#p2pool-alt'
VERSION_CHECK = lambda v: 60007 <= v
VERSION_WARNING = lambda v: 'Upgrade eMark to >= 1.1.0.0!' if v < 60007 else None


Code:
import os
import platform

from twisted.internet import defer

from .. import data, helper
from p2pool.util import pack


P2P_PREFIX = 'e4e8e9e5'.decode('hex')
P2P_PORT = 5556
ADDRESS_VERSION = 53
RPC_PORT = 6666
RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'eMarkaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        ))
SUBSIDY_FUNC = lambda height: 50*210000000
POW_FUNC = data.hash256
BLOCK_PERIOD = 120 # s
SYMBOL = 'DEM'
CONF_FILE_FUNC = lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'eMark') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/eMark/') if platform.system() == 'Darwin' else os.path.expanduser('~/.eMark'), 'eMark.conf')
BLOCK_EXPLORER_URL_PREFIX = 'http://85.214.246.63:3009/block/'
ADDRESS_EXPLORER_URL_PREFIX = 'http://85.214.246.63:3009/address/'
TX_EXPLORER_URL_PREFIX = 'http://85.214.246.63:3009/tx/'
SANE_TARGET_RANGE = (2**256//2**32//1000000 - 1, 2**256//2**32 - 1)
DUMB_SCRYPT_DIFF = 1
DUST_THRESHOLD = 0.001e8

full member
Activity: 238
Merit: 100
if anybody interested to mine in central Europe, Czech republic, there is a node http://185.73.103.2:9332/
fee 0.9%, author donation 0.1%
johndoe stats @ http://185.73.103.2:9332/static/jd/

plans

to add spare hw to backup it using load balancing tools
to backup it via another independent internet connection
to build website @ sexy domain name

removed any fees from p2pool node http://185.73.103.2:9332
legendary
Activity: 2212
Merit: 1038
It's been a while but my hash rate graph has finally stopped looking like the EEG from a cardiac arrest patient.  Cheesy
legendary
Activity: 1258
Merit: 1027

Important update for users of http://minefast.coincadence.com

Whether you use it as a backup node or primarily mine on minefast.coincadence.com please update your miners today!

We have an exciting announcement coming in the next few days, all I can say at this point is that the domain name will change.

To keep mining uninterrupted please update your miners to use the IP address of the server rather then the domain, the IP will remain the same during the switch and you will not have any downtime.

Set your miners pool URL to:

stratum+tcp://54.235.94.19:9332

Everything else remains unchanged.

sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
My p2pool node appears to be healthy, not seeing anything in the console output that looks weird.  The http://ngspoe.carpenter-farms.us:9332/static/ page looks fine, but I'm not seeing my node in http://poolnode.info/

It was there for the past day, just not seeing it now.  Any ideas?

Update:  next day, still not showing up.

Update2:  Seeing my minors fail over to their backup pool, briefly, several times an hour.  This ROUGHLY aligns with namecoin blocks being found by the failover site (e.g. block change requests).  I've also become concerned about the variance issue - I know that in theory it doesn't matter, but with multiple days per block, it feels like the difficulty change will unduly impact us.  Not sure I have the skills to run this pool effectively.
legendary
Activity: 2212
Merit: 1038
And now I'm running my browser sandboxed...
legendary
Activity: 1258
Merit: 1027
OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.

Are you running the latest source from the github page?  There was a patch released post version 15 that fixed the connecting of version 14 peers.  That might be the issue you are having.  The swarm of remaining version 14 peers will keep on trying to connect and send you shares, creating problems on your node.

I can't figure out how to sandbox python, I'm unable to install the boost library on my MSYS build so I can't compile the source myself and forrest hasn't released an MSVC windows binary for latest commit yet.

Also I'm having issues fashioning tin foil helmets for my computers...

Have you considered docker? https://www.docker.com/
legendary
Activity: 2212
Merit: 1038
OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.

Are you running the latest source from the github page?  There was a patch released post version 15 that fixed the connecting of version 14 peers.  That might be the issue you are having.  The swarm of remaining version 14 peers will keep on trying to connect and send you shares, creating problems on your node.

I can't figure out how to sandbox python, I'm unable to install the boost library on my MSYS build so I can't compile the source myself and forrest hasn't released an MSVC windows binary for latest commit yet.

Also I'm having issues fashioning tin foil helmets for my computers...
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles

Cassey,

That figure is the fee payments that you would get... the expected earnings are listed further down the page against the coin address used by your miner(s)


Ah, that makes more sense.  Thanks!
member
Activity: 193
Merit: 10
you do not need to bind with every existing node. I run my node satisfied with 3 out 1 in connections and relaynode by Matt. I use github bitcoind with no conf change with <0.2s gbt latency (0.165s daily average just now, monthly average 0.188s) and github p2pool 15.0-11 keeping both in last version.

Good to know, thanks.  Over the past 24ish hours I've seen it vary from 6 out, 0 in to 7 out, 1 in.  No idea what drives that, but it sounds like those numbers are somewhat healthy.

The http://ngspoe.carpenter-farms.us:9332/static/ page is confusing me a bit.  As of this post, I've found 41 shares, 8 have been orphaned (which I kind of understand), but my payout should a block be found is forecasted at 0 btc?  Shouldn't I expect to get some small payout (my shares/totalshares * BTC reward)Huh

Cassey,

That figure is the fee payments that you would get... the expected earnings are listed further down the page against the coin address used by your miner(s)
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
you do not need to bind with every existing node. I run my node satisfied with 3 out 1 in connections and relaynode by Matt. I use github bitcoind with no conf change with <0.2s gbt latency (0.165s daily average just now, monthly average 0.188s) and github p2pool 15.0-11 keeping both in last version.

Good to know, thanks.  Over the past 24ish hours I've seen it vary from 6 out, 0 in to 7 out, 1 in.  No idea what drives that, but it sounds like those numbers are somewhat healthy.

The http://ngspoe.carpenter-farms.us:9332/static/ page is confusing me a bit.  As of this post, I've found 41 shares, 8 have been orphaned (which I kind of understand), but my payout should a block be found is forecasted at 0 btc?  Shouldn't I expect to get some small payout (my shares/totalshares * BTC reward)Huh
newbie
Activity: 58
Merit: 0
OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.

Are you running the latest source from the github page?  There was a patch released post version 15 that fixed the connecting of version 14 peers.  That might be the issue you are having.  The swarm of remaining version 14 peers will keep on trying to connect and send you shares, creating problems on your node.
full member
Activity: 238
Merit: 100
if anybody interested to mine in central Europe, Czech republic, there is a node http://185.73.103.2:9332/
fee 0.9%, author donation 0.1%
johndoe stats @ http://185.73.103.2:9332/static/jd/

plans

to add spare hw to backup it using load balancing tools
to backup it via another independent internet connection
to build website @ sexy domain name
full member
Activity: 238
Merit: 100
Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come Smiley

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

Thanks.  Somehow I missed that port reference from the guide I was using to install.  I had 9332 open, but not 9333.  It is now opened and dnatted to my p2pool VM.  Not sure it matters but I'll restart the p2pool just to be safe.  I'll drop max connections some while its down.

you do not need to bind with every existing node. I run my node satisfied with 3 out 1 in connections and relaynode by Matt. I use github bitcoind with no conf change with <0.2s gbt latency (0.165s daily average just now, monthly average 0.188s) and github p2pool 15.0-11 keeping both in last version.
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come Smiley

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

Thanks.  Somehow I missed that port reference from the guide I was using to install.  I had 9332 open, but not 9333.  It is now opened and dnatted to my p2pool VM.  Not sure it matters but I'll restart the p2pool just to be safe.  I'll drop max connections some while its down.
legendary
Activity: 1258
Merit: 1027
Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come Smiley

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...
sr. member
Activity: 470
Merit: 250
Better to have 100 friends than 100 rubles
Hi all.  Thought I'd check out p2pool for my local 16.5TH of mining.

Happy to say it all went smoothly for doing straight bitcoin mining.  Saw a few python exceptions during startup, but once it got initialized, it appears to be working fine.

I'm not having as much luck with merged mining bitcoin and namecoin.

Syntactically all appears fine, and initialization proceeds as above.  However I see:



Reoccurring frequently in the console output.  All my miners are also showing a Diff of 1, which is a change.

Any thoughts?

Edit:  Also seem to be stuck at 8 connections, even though I'm starting up with " --max-conns=256" and my bitcoind has 19 connections.

Pool stats at:  http://ngspoe.carpenter-farms.us:9332/static/

Update:  Found my stupid mistake, was specifying namecoins coin port instead of the rpcport on the --merged line.  The Diff of 1 also cleared itself up after a few minutes.

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?
legendary
Activity: 1512
Merit: 1012
P2Pool is a support (backup) for all pools of bitcoin around the world ... usually farm start, on P2Pool, different grid to measure the performance, and then switch to local stratum server.

P2Pool never die at the end, because, it's the last wall of mining process (DDoS proof).

The power of P2Pool, you earn the SAME AMOUNT of bitcoins when you are on a big pool or on the P2Pool ... after 3 months.  Roll Eyes

I mine on P2Pool since 2 years.
member
Activity: 88
Merit: 10
Else p2pool will die in some month.

P2Pool is here since 2011 ... little boy !
Tell me "Big boy" why P2pool is here since 2011, but now falls in a deep hole. And when the falls end and pool rise up?
Today global power is from 0.7 to 1Ph and 123 hours of waiting - do You think this is normal and nothing to worry about?
If you really think that you have leed balls.
Jump to: