Author

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

newbie
Activity: 56
Merit: 0
Ok guys thanks alot got it up and running. Now how do you edit the give author more in the conf also if i would like to setup a fee how do you do that what are the commands etc. is there a list of commands you can use in the config file. PS running on win7

Thanks in advance.
full member
Activity: 213
Merit: 100
Hi all just abit offtopic. I started using p2pool got it setup and running on my local node. Now just a quick qustion how to make my node public so that i can have some of my friends connect to it.

Thanks in advance.

Email the owner of this site he'll post it up for you on his node finder

http://nodes.p2pool.co/
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Hi all just abit offtopic. I started using p2pool got it setup and running on my local node. Now just a quick qustion how to make my node public so that i can have some of my friends connect to it.

Thanks in advance.
Not off topic at all.  Assuming you have a BTC p2pool node setup, you'll need to open up port 9332.  To be a "good" citizen, you should have the following ports open:

8333 - BTC peers
9333 - p2pool peers
9332 - p2pool miners

Note that opening up 8333 and 9333 will allow multiple peers to connect and you will see higher bandwidth usage.
newbie
Activity: 56
Merit: 0
Hi all just abit offtopic. I started using p2pool got it setup and running on my local node. Now just a quick qustion how to make my node public so that i can have some of my friends connect to it.

Thanks in advance.
sr. member
Activity: 266
Merit: 250
Can you post your logs of when the problem started? This looks exactly like the problem I referred to earlier.Also, are you using the relatnetworkclient?
legendary
Activity: 1512
Merit: 1012
Well ... solved by a reboot of P2Pool but i don't like this issue.  Roll Eyes

legendary
Activity: 1512
Merit: 1012
 Angry and again ... i have a problem with the shares of P2Pool.
Shares don't rise on P2Pool command ... and Bitcoin Core debug.log indicate insane "input already spend".

 Huh someone have an explaination, or, it's again a corrupted share chain in my folder (local).

legendary
Activity: 1512
Merit: 1012
I have noticed happen with p2pools that go a long time between finding blocks.

P2Pool power : http://minefast.coincadence.com/p2pool-stats.php = 1,5 PH/s
Bitcoin power : https://bitcoinwisdom.com/bitcoin/difficulty = 365 PH/s


no problem here.  Wink
full member
Activity: 213
Merit: 100
With it's current luck and problems looks like it's dwindling.  Cry to see this go.
hero member
Activity: 561
Merit: 500
kittehcoin.info
Hm this is interesting and worth investigating. However, now I have no idea how to use p2pool over TOR?

I don't have an answer for the original question, sorry, but will say that p2pool over tor is a horrible idea.

One of the main trade-offs for using the onion router is speed for privacy, you loose a great deal of speed to gain incremental privacy.

As a miner on p2pool, the competition is tough and speed is everything; latency from miner to node, node to peers, bitcoin's GBT latency, etc...

Tor, while an awesome project, slows things down by its very privacy centric routing nature.

Tor - great for privacy, horrible for mining bitcoin.
You are probably right so I ll have to give up on running p2pool on this specific coin. Thank you all for trying to help me, very kind from all of the ppl here.
legendary
Activity: 1270
Merit: 1000
I know this is the wrong forum for this but there is something I have noticed happen with p2pools that go a long time between finding blocks.

The Share data Timestamp gets out of sync with the Block Timestamp (share example below).

Code:
P2Pool > Share 5d2b2435
Parent: 84811fe2
Far parent: 43fe4ebd
Children: a62c35b8
Type: Share
Local data
Verified: true
Time first seen: Thu Jul 16 2015 12:14:49 GMT-0700 (Pacific Daylight Time) (1437074089.855)
Peer first received from: null
Share data
Timestamp: Tue Apr 28 2015 02:51:43 GMT-0700 (Pacific Daylight Time) (1430214703)
Difficulty: 0.00732421875
Minimum difficulty: 0.00024413713253701452
Payout address: WZVMSJTXSGSTxUNvEbrswYjxaVN78U39Aw
Donation amount: 0.00%
Last stale: null
Nonce: 2849031433
Desired version: 13
Absolute height: 2738339
Absolute work: 381219517042610
Block
Hash: 070892fbf1f9a16577bf5369d29226f0d54fca74566485fe9dcd147a5d2b2435
Header
Version: 2
Previous block: 6f09e34bb7ebc14aba03c8b3e6f17e18856bd911ccf2a105c2a5624df2af25db
Merkle root: dfeb25ec89a937f0081284e5257067eda1d76a39d3a4f4d3bd5feaed03b68353
Timestamp: Sun Jul 12 2015 10:32:24 GMT-0700 (Pacific Daylight Time) (1436722344)
Difficulty: 66.48263727902803
Nonce: 2261320128
Generation transaction
Hash: dfeb25ec89a937f0081284e5257067eda1d76a39d3a4f4d3bd5feaed03b68353
Coinbase (hex): 03470d1f2cfabe6d6d205454b1fe5ead378f44859adc946bb2cfa216c3348e76bcf2533241f13bb8960800000000000000
Coinbase (text): ?G??,??mm TT??^?7?D????k?????4?v??S2A?;??????????
Value: 40 WDC
Last txout nonce (used by Stratum miners): 0000000000000001
Other transactions

After enough blocks are found it eventually syncs back up.
The main problem with this is that the share difficulty stays at the lowest possible rate until it does sync causing p2pool to overload itself when large miners come on.

A not so important side effect is that if you have irc announce on it does not report found blocks until it is back in sync.

If anyone is inclined to look into this I would be forever thankful.

Bounty: 0.08 BTC  Cool
legendary
Activity: 1258
Merit: 1027
Hm this is interesting and worth investigating. However, now I have no idea how to use p2pool over TOR?

I don't have an answer for the original question, sorry, but will say that p2pool over tor is a horrible idea.

One of the main trade-offs for using the onion router is speed for privacy, you loose a great deal of speed to gain incremental privacy.

As a miner on p2pool, the competition is tough and speed is everything; latency from miner to node, node to peers, bitcoin's GBT latency, etc...

Tor, while an awesome project, slows things down by its very privacy centric routing nature.

Tor - great for privacy, horrible for mining bitcoin.
sr. member
Activity: 266
Merit: 250
Hm this is interesting and worth investigating. However, now I have no idea how to use p2pool over TOR?

Can't help you there I'm afraid, but I'm also interested in how to set it up.......gonna google for a while  Smiley
hero member
Activity: 561
Merit: 500
kittehcoin.info
Hm this is interesting and worth investigating. However, now I have no idea how to use p2pool over TOR?
sr. member
Activity: 266
Merit: 250
Doesn't joincoin use TOR? I've never tried using p2pool over TOR, but I'm sure it requires a slightly different configuration, ie:

Code:
 -tor=         Use proxy to reach tor hidden services (default: same as -proxy)

Just a thought......
hero member
Activity: 561
Merit: 500
kittehcoin.info
Hehe, yes I did try but still the same problem.

legendary
Activity: 2212
Merit: 1038
lol, give it a try if Joincoin is in fact using Core =* could be mucking up the works. Try deleting it or changing it to =::/0
hero member
Activity: 561
Merit: 500
kittehcoin.info
Yes I know that wildcards are not used anymore but still there is a:
Quote
rpcallowip=127.0.0.1
and
Quote
rpcconnect=127.0.0.1
I m really thankful for your time trying to help and this becoming real interesting task Smiley
Last two days I m working on this Smiley
legendary
Activity: 2212
Merit: 1038
I missed the fact the .conf file was posted, doh.

Ok, one more try...

Is Joincoin based on Bitcoin-Core?

I see 'rpcconnect=*' and 'rpcallowip=*' I recall something about this no longer being allowed syntax... let me see...

Change to 'rpcconnect=::/0' and 'rpcallowip=::/0' and see what happens. Also if you're using wild cards like that all those additional addresses are redundant.
hero member
Activity: 561
Merit: 500
kittehcoin.info
There is no such value in .conf file, but what could be confusing here is taking P2P_PREFIX from his specific coin.
According to this:
Quote
pchMessageStart[0] = 0xf1;
pchMessageStart[1] = 0xb4;
pchMessageStart[2] = 0xdc;
pchMessageStart[3] = 0x9e;
P2P_PREFIX should look like this:
Quote
P2P_PREFIX = 'f1b4dc9e'.decode('hex') #pchmessagestart
Jump to: