Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 236. (Read 2591928 times)
January 12, 2015, 10:07:27 AM
I'm not sure I get it either tbh. I think there are much more pressing issues with p2pool that need to be addressed too.
January 12, 2015, 09:59:20 AM
What exactly does this do?
M
M
Looks like it pulls and rotates the default mining addresses from bitcoind.
I saw that too. Why would you want that?
Anyone else try this? I'm getting errors all over the place:
My mistake. It's a pretty easy fix, non-impactful. I'm working on it now and should have it in a pullreq for forrest soon.
The reason you would want something like this is because normally, p2pool pays out to the same address over and over when it constructs its coinbases. But this isn't ideal: if you are ever identified, then your entire mining history might be laid bare for the world to see. You must maintain perfect opsec, forever, if you desire stronger financial privacy under this method of mining.
If you rotate keys on a programmable basis, then you get payouts to *different* addresses with no additional effort on your behalf and it is somewhat more difficult to correlate which addresses are grouped with one another until you spend them and group them yourself.
You could have achieved an approximation of this by having miners who were inputting some different addresses and accepting miner-supplied payout addresses, but then you have to do it by hand and it was really annoying.
In my opinion, p2pool users now have arguably more privacy even then solo miners, by using this option, at the expense of a larger coinbase.
(fwiw, considering the spam nonsense going into the blockchain right now, I hardly think miners demanding additional privacy is at the top of the list of UTXO bloat.)
What am I missing?
January 12, 2015, 09:55:26 AM
iv got a few unused servers as well. been mining a few months and was thiking about starting my own pool. Would there be a way to join our servers as one pool. lol if not no worries... how do u start your own pool. im on about 1th+
Here's an excellent guide:
https://bitcointalk.org/index.php?topic=651819.0;topicseen
By setting up your own node you are joining one large pool - that's the beauty of it.
Edit: Use the manual instructions though, I think the scripts for auto setup are a little outdated.
January 12, 2015, 09:49:10 AM
iv got a few unused servers as well. been mining a few months and was thiking about starting my own pool. Would there be a way to join our servers as one pool. lol if not no worries... how do u start your own pool. im on about 1th+
January 12, 2015, 06:52:52 AM
What exactly does this do?
M
M
Looks like it pulls and rotates the default mining addresses from bitcoind.
I saw that too. Why would you want that?
Anyone else try this? I'm getting errors all over the place:
My mistake. It's a pretty easy fix, non-impactful. I'm working on it now and should have it in a pullreq for forrest soon.
The reason you would want something like this is because normally, p2pool pays out to the same address over and over when it constructs its coinbases. But this isn't ideal: if you are ever identified, then your entire mining history might be laid bare for the world to see. You must maintain perfect opsec, forever, if you desire stronger financial privacy under this method of mining.
If you rotate keys on a programmable basis, then you get payouts to *different* addresses with no additional effort on your behalf and it is somewhat more difficult to correlate which addresses are grouped with one another until you spend them and group them yourself.
You could have achieved an approximation of this by having miners who were inputting some different addresses and accepting miner-supplied payout addresses, but then you have to do it by hand and it was really annoying.
In my opinion, p2pool users now have arguably more privacy even then solo miners, by using this option, at the expense of a larger coinbase.
(fwiw, considering the spam nonsense going into the blockchain right now, I hardly think miners demanding additional privacy is at the top of the list of UTXO bloat.)
This makes sense and I agree. Now I'm unsure how to use it?
M
January 12, 2015, 01:57:50 AM
What exactly does this do?
M
M
Looks like it pulls and rotates the default mining addresses from bitcoind.
I saw that too. Why would you want that?
Anyone else try this? I'm getting errors all over the place:
My mistake. It's a pretty easy fix, non-impactful. I'm working on it now and should have it in a pullreq for forrest soon.
The reason you would want something like this is because normally, p2pool pays out to the same address over and over when it constructs its coinbases. But this isn't ideal: if you are ever identified, then your entire mining history might be laid bare for the world to see. You must maintain perfect opsec, forever, if you desire stronger financial privacy under this method of mining.
If you rotate keys on a programmable basis, then you get payouts to *different* addresses with no additional effort on your behalf and it is somewhat more difficult to correlate which addresses are grouped with one another until you spend them and group them yourself.
You could have achieved an approximation of this by having miners who were inputting some different addresses and accepting miner-supplied payout addresses, but then you have to do it by hand and it was really annoying.
In my opinion, p2pool users now have arguably more privacy even then solo miners, by using this option, at the expense of a larger coinbase.
(fwiw, considering the spam nonsense going into the blockchain right now, I hardly think miners demanding additional privacy is at the top of the list of UTXO bloat.)
January 11, 2015, 08:50:47 PM
Well, glad I checked here before pulling the latest version - but of a cock-up eh?
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
I had the same thing this past week, did it look like this? https://bitcointalksearch.org/topic/m.10066280
Similar, but it was a handshake error every 30 seconds, or thereabouts.
I'm wondering if Bitmains "p2p"(?) pool isn't trying to connect to the real p2pool & p2pool is recognising that the share chains don't match, so drops it.....would this be possible?
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
Similar, but it was a handshake error every 30 seconds, or thereabouts.
I'm wondering if Bitmains "p2p"(?) pool isn't trying to connect to the real p2pool & p2pool is recognising that the share chains don't match, so drops it.....would this be possible?
January 11, 2015, 08:30:05 PM
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
Similar, but it was a handshake error every 30 seconds, or thereabouts.
Port was 9333.
January 11, 2015, 07:31:22 PM
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
Similar, but it was a handshake error every 30 seconds, or thereabouts.
Port was 9333.
January 11, 2015, 07:28:29 PM
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
Similar, but it was a handshake error every 30 seconds, or thereabouts.
January 11, 2015, 07:05:18 PM
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
Similar, but it was a handshake error every 30 seconds, or thereabouts.
January 11, 2015, 05:24:15 PM
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
January 11, 2015, 04:53:43 PM
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
Wouldn't surprise me......
Because it was constantly showing up in my p2pool window & being dropped.
January 11, 2015, 04:14:54 PM
I posted an issue on Github about the commit breaking things.
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
Thanks for this link, was able to get my node back up again after faffing around with that latest release.......
When I git pulled it, it had been up for over 12 hours - I can't believe we were the only people to have had problems with it, surely? I mean, wouldn't forrestv have tested it first?
I can't remember ever having problems with new releases, not as severe as this one anyway.I'd still love to know who my Chinese friend is who's hammering my node from 1.202.128.218:9333 - I ended up having to block it
bmt ? lol just jk btw hahaha
how do u know someone is hammering your node & wut is he/she doing to yr node ?
January 11, 2015, 02:59:57 PM
I posted an issue on Github about the commit breaking things.
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
Thanks for this link, was able to get my node back up again after faffing around with that latest release.......
When I git pulled it, it had been up for over 12 hours - I can't believe we were the only people to have had problems with it, surely? I mean, wouldn't forrestv have tested it first?
I can't remember ever having problems with new releases, not as severe as this one anyway.I'd still love to know who my Chinese friend is who's hammering my node from 1.202.128.218:9333 - I ended up having to block it
January 11, 2015, 02:12:05 PM
I posted an issue on Github about the commit breaking things.
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
If you have a server dedicated to P2P with bitcoind running and have your payouts going to another wallet on a different server why would you need to implement address rotation with bitcoind? I read the post on github and do not see why this would have been a benefit. Obviously I need a better education with this aspect. Can someone just point me in the right direction so I can read up on this please.I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
You would have no need for this.
Address reuse is generally frowned upon from both a security and privacy standpoint, if you were using the node bitcoind wallet this would be a big security improvement.
Quote
Privacy
Address reuse harms the privacy of not only yourself, but also others - including many not related to the transaction. In some cases, these risks are serious enough that they are likely in violation of reasonable consumer protection laws.
Security
Bitcoin does not, at a low level, have any concept of addresses, only individual coins. Address reuse, at this layer, requires producing multiple digital signatures when you spend bitcoins. Multiple situations have been found where more than one digital signature can be used to calculate the private key needed to spend bitcoins. Even if you spend all the bitcoins claimed by this private key at once, it is still possible to double-spend them in theft before they confirm. While the situations for finding the private key from signatures have been fixed, it is not prudent to assume there aren't more such situations yet unknown.
In the case of spending all the TXOs in a single transaction, there is an additional risk if someone is actively monitoring the network for vulnerable transactions: upon receiving such a transaction, they can split up their double spends such that there is only one ECDSA verification per transaction (making a single transaction for each TXO); this will cause the attacker's transactions to relay across the rest of the nodes faster than the legitimate one, increasing success of a double spend.
https://en.bitcoin.it/wiki/Address_reuse
January 11, 2015, 02:00:11 PM
Need a little help.
How do you show blocks found that is more than a day ago? I've been looking at the code but I can't seem to find it or rather, changes I make doesn't seem to make it happen. So, as you can tell, I'm not a programmer and am only good at changing letters here and there.
Reason being, it looks really really really bad when recent blocks is blank.......
Thanks much.
How do you show blocks found that is more than a day ago? I've been looking at the code but I can't seem to find it or rather, changes I make doesn't seem to make it happen. So, as you can tell, I'm not a programmer and am only good at changing letters here and there.
Reason being, it looks really really really bad when recent blocks is blank.......
Thanks much.
http://minefast.coincadence.com/p2pool-stats.php
Coincadence gives pool stats and all blocks ever mined from p2pool. It is very useful. However, if you are asking how to modify your p2pool server website to show more than just one day of blocks than that code is in p2pool/web.py. Find the area of code which is "web_root.putChild('recent_blocks', ..." and in there it defines the time period. Several lines down it should say something like "24*60*60" which represents 24 hours, 60 minutes, and 60 seconds. If you would like to show more than one day of data just multiply this number larger by the number of days you would to display.
January 11, 2015, 01:49:11 PM
I posted an issue on Github about the commit breaking things.
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
If you have a server dedicated to P2P with bitcoind running and have your payouts going to another wallet on a different server why would you need to implement address rotation with bitcoind? I read the post on github and do not see why this would have been a benefit. Obviously I need a better education with this aspect. Can someone just point me in the right direction so I can read up on this please.I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
You would have no need for this.
Address reuse is generally frowned upon from both a security and privacy standpoint, if you were using the node bitcoind wallet this would be a big security improvement.
Quote
Privacy
Address reuse harms the privacy of not only yourself, but also others - including many not related to the transaction. In some cases, these risks are serious enough that they are likely in violation of reasonable consumer protection laws.
Security
Bitcoin does not, at a low level, have any concept of addresses, only individual coins. Address reuse, at this layer, requires producing multiple digital signatures when you spend bitcoins. Multiple situations have been found where more than one digital signature can be used to calculate the private key needed to spend bitcoins. Even if you spend all the bitcoins claimed by this private key at once, it is still possible to double-spend them in theft before they confirm. While the situations for finding the private key from signatures have been fixed, it is not prudent to assume there aren't more such situations yet unknown.
In the case of spending all the TXOs in a single transaction, there is an additional risk if someone is actively monitoring the network for vulnerable transactions: upon receiving such a transaction, they can split up their double spends such that there is only one ECDSA verification per transaction (making a single transaction for each TXO); this will cause the attacker's transactions to relay across the rest of the nodes faster than the legitimate one, increasing success of a double spend.
https://en.bitcoin.it/wiki/Address_reuse
January 11, 2015, 01:39:49 PM
I posted an issue on Github about the commit breaking things.
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
If you have a server dedicated to P2P with bitcoind running and have your payouts going to another wallet on a different server why would you need to implement address rotation with bitcoind? I read the post on github and do not see why this would have been a benefit. Obviously I need a better education with this aspect. Can someone just point me in the right direction so I can read up on this please.I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
January 11, 2015, 01:23:39 PM
I posted an issue on Github about the commit breaking things.
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
I did not try it before I posted, sorry was just excited to see it
You can pull the code from just before this commit here:
https://github.com/forrestv/p2pool/tree/dfad3cd69c1d2567e41b05e3f5929d654f2014b1
Jump to: