 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
I have updated p2pool.io to use jtoomim's 1mb_segwit fork. p2pool.io:9332 is still based on Bitcoin core. I have also deployed ltc.p2pool.io:9327 for Litecoin mining using the same fork and have plans to add several more coins very soon. has been moved back to forrestv's p2pool/p2pool@master branch. (The original P2Pool) |
|
|
|
I have updated p2pool.io to use jtoomim's 1mb_segwit fork. p2pool.io:9332 is still based on Bitcoin core. I have also deployed ltc.p2pool.io:9327 for Litecoin mining using the same fork and have plans to add several more coins very soon. |
|
|
|
Currently active nodes:
addnode=91.121.221.92:35698
addnode=212.47.229.49:35698
addnode=174.98.184.129:57412
addnode=51.15.53.179:35698
addnode=81.162.194.236:1791
addnode=63.247.147.166:59779
addnode=5.187.70.71:8814
addnode=76.169.51.184:54859
I can look into possibly adding a master seed node to one of my servers. Let's bring TAKCoin back! |
|
|
|
I've been running P2Pool in a Docker container for over a year now with great success so I've decided to make my Docker container public. Nothing super special here, but this should allow you to easily run P2Pool Core regardless of what platform you're on and not have to worry about binaries. (As long as you have Docker installed) I currently have a tag up for 17.0 on Docker Hub, but can add more later once future releases are made. https://hub.docker.com/r/acejam/p2pool/https://github.com/acejam/docker-p2pooldocker run -p 9332:9332 -p 9333:9333 acejam/p2pool:17.0 ${p2pool_command_options_here} |
|
|
|
|
I'm having trouble understanding why this is an issue to begin with. Isn't DNS peer discovery one of the ways in which Bitcoin works? Why are hosts sending out notices claiming Botnets and other malicious activity? Excessive connection attempts?
It looks like one of these SIPA DNS records may have mapped to one of my server's IP. Why is that my problem? I can't control how others configure their DNS records.
I have reduced my connections from 50 down to 15. However I don't want to have to setup any type of proxy, especially a TOR one, as that will just create a slew of new problems to deal with.
|
|
|
|
Once approche would be to reduce the amount of connection with the `--maxconnections` argument. Or your a tor SOCK5 proxy for outgoing connections. Similar like the patch i wrote for the seeder: https://github.com/sipa/bitcoin-seeder/pull/29I believe I'm currently running with maxconnections set to 25. However I'm not running the above bitcoin-seeder app, so I'm not sure how that PR would do anything for me. (I'm only running bitcoin core and P2Pool) |
|
|
|
|
I also just received one of these letters from my host. I have been running a full node and P2Pool for years now.
Any ideas on how to prevent these? I'm very confident that my server isn't compromised, but my host thinks it is.
|
|
|
|
Looks like p2pool.org:9332 and minefast[2].CoinCadence.com:9332 are both down. This is why a high availability P2Pool cluster like http://p2pool.io/ is better.  (for those who need to use a public P2Pool node) |
|
|
|
Do NOT open port 8332 unless you intentionally want to allow RPC commands to your bitcoin daemon! That means that an outsider could send a command to empty all coins on the wallet and send them to himself. Yes, I know you can mitigate this by limiting the allowed IPs in the config file, but my point is, why expose yourself to unnecessary risk? Port 8333 should be open so bitcoind can connect to other nodes.
For p2pool, open port 9332 if you want to see the Web interface or connect miners to your pool from outside your firewall. If you don't want either, you can safely keep it closed. Open port 9333 so p2pool can connect to other p2pool nodes. This port should generally be open.
For other coins, again, you want to keep the RPC port closed, but the other, generic port open. I don't know which of those ports are which from your list; check your coins' documentation.
rpcallowip=192.168.1.* OR rpcallowip=127.0.0.1 |
|
|
|
I tried to find out something more about this problem, but I couldnīt. My problem is, that I donīt get any IN connections. http://84.42.144.19:9332/static/Version: 13.4 Pool rate: 292TH/s (17% DOA+orphan) Share difficulty: 1280000 Peers: 8 out, 0 inLocal rate: 8.85GH/s (5.1% DOA) Expected time to share: 7.2 days Shares: 0 total (0 orphaned, 0 dead) Efficiency:  I use P2Pool release 13.4 for Windows ( https://bitcointalk.org/index.php?topic=18313.0) I have open all ports OUT, and these ports IN: 8333,9332,9333 Thank you in advance for any help. As of right now, your node uptime is 25 minutes. You're connected to 7 other nodes. Other P2Pool nodes and clients out there are simply connected to other nodes. The longer your node is up, the more incoming connections you will gain. However, having zero incoming connections isn't a bad thing, so don't treat it like one.  I have P2Pool nodes in my cluster than have been up for 60+ days and have 40+ incoming connections. They also use noticeably more bandwidth than the ones that only have 5 or 10 connections. |
|
|
|
As of today there are 2 solo pools that I know of .
"Solo pool" is an oxymoron. |
|
|
|
IS node
LOST CONTACT WITH BITCOIND for 3.1 minutes! Check that it isn't frozen or dead!
restarted bitcoind. this is the 2nd time that this has happened. i'll need to investigate ADD: i'd advise making the EU node your failover, that way you won't lose any shares if this happens again. People aren't smart. Failover should always be server-side. |
|
|
|
|
Are you still mining on P2Pool? Looks like privatecoinpurse.info:9332 is down.
|
|
|
|
The EU node runs fine with the same specifications. However, these severs can easily be upgraded with any hardware needed.
I found the only merged coin which was a drain on resources, was Huntercoin; which has been removed from the node.
Once you get more traffic, that will change quite a bit. |
|
|
|
Where is middle east node located?
It will be Isreal; however my first instance was created with too little memory (I was tired and missed points on the setup), so i've scratched it and will be installing 2CPU 4GB RAM and 50GB SSD with unlimited bandwidth. Are you merged mining? If so, you're going to need more RAM than that. |
|
|
|
|
