Thanks for the reply m8. but i am lost now  where about do you find this start up command. =) just abit step by step new to this. You type it in a command console to start p2pool. Have a read of the readme, particularly the section on running p2pool: https://github.com/forrestv/p2poolor type in: python run_p2pool.py --help ..to see a list of commands  |
|
|
|
ok just to make sure . i did edite the bitcoind conf file whit :
--give-author 2
-f 1
when i lunched the p2pool it said donating 1% to the author. Did i do something wrong. ? ?
Not in the bitcoind conf file, add it to the p2pool start up command, like so: ~/p2pool/run_p2pool.py --give-author {yourdonation] --fee [yourfee]Add your number without the [], leaving a space between commands. |
|
|
|
Hmmm....I didn't use libdb5.1-dev libdb5.1++-dev - I used 4.8 instead, as I do with all my wallets. Maybe try with that instead? It compiled fine on both 32bit & 64bit Xubuntu for me  |
|
|
|
I'm still getting disconnects I'm afraid, but not constant as before: 127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
Received transaction of size 4027 from relay server
Sent transaction of size 4027 to relay server
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
Received transaction of size 407 from relay server
Sent transaction of size 407 to relay server
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
Received transaction of size 519 from relay server
Sent transaction of size 519 to relay server
Received transaction of size 1057 from relay server
Sent transaction of size 1057 to relay server
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
Received transaction of size 225 from relay server
Sent transaction of size 225 to relay server
Received transaction of size 225 from relay server
Sent transaction of size 225 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 226 to relay server
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
Received transaction of size 226 from relay server
Sent transaction of size 226 to relay server
Received transaction of size 373 from relay server
Sent transaction of size 373 to relay server
Received transaction of size 226 from relay server
Sent transaction of size 226 to relay server
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
127.0.0.1 Disconnect: failed to read message header (Transport endpoint is not connected)
|
|
|
|
I wonder if they had one big client or how the sale went.
Presuming they actually sold anything at all, I've not heard of or seen anything concrete yet, just pure speculation. Their lack of communication both here & via email is a little disturbing, my little red flags are growing bigger & bigger every day I'm actually not expecting anything from them soon, if at all. At least that way, if they do decide to post/email/produce something - it will be a pleasant surprise, albeit an expensive one. |
|
|
|
That done the trick - up & running again  |
|
|
|
New windoze wallet won't sync - tried removing peers.dat but still nothing..... Did you break it?  Hmmm let me double check, what system are you running it on? I ran it and it seemed fine... Windoze 7 64bit. Not tried the NIX wallet yet. |
|
|
|
New windoze wallet won't sync - tried removing peers.dat but still nothing..... Did you break it? |
|
|
|
|
Like this:
addnode=104.131.25.221
addnode=108.61.10.90
addnode=137.135.57.119
addnode=144.76.239.66
addnode=144.76.64.123
addnode=158.255.89.244
addnode=162.216.4.199
addnode=162.243.47.14
addnode=167.114.156.87
addnode=178.33.209.208
addnode=178.62.145.250
addnode=185.50.213.123
addnode=188.138.33.239
addnode=188.138.94.6
addnode=192.95.29.153
addnode=192.99.245.21
|
|
|
|
Merged UNO would be great...
You can do it, just add: --merged http://[uno_user_name]:[uno_rpc_password]@127.0.0.1:45888/ to the end of your p2pool startup syntax I'll try & get an updated guide posted in the next few days - time permitting. |
|
|
|
could you post a 'quick guide to' merged mining on p2pool/s?
i tried mining at mmpool but never saw any stats/return
right now im mining at eligius & im not particularly loving it
I'm actually just finishing off an updated p2pool mult-merge mine node setup guide now, should be up in a day or two. There are a couple of guides out there already, but they are a little outdated with a few coins/repos missing - but this one is definitely worth a read if you want to familiarize yourself until mine is ready: https://bitcointalk.org/index.php?topic=651819.0;topicseenmmpool is a good pool with an honest dev, unfortunately it has been under ddos attack recently  As for eligius......well.....hmmmm.....no comment |
|
|
|
Sorry thats my bad, I have some s3's im offloading and and got a email in regards a failed sale and thought it was you.
Working 50 hours in a week will do that.
We are all good.
This is getting silly  I'm out. |
|
|
|
|
Yeah, but if a load of these suddenly came online, diff would quickly jump sooner than 350 days I think.....
|
|
|
|
Postage cost is per unit.
Postage cost is what it is and believe me when I say this I make no money on it.
I know, postage prices are a rip-off eh? I still need a price though......... |
|
|
|
If you live in the U.K its going to be about $55
Is that for 2? Give me a ball park figure for 2 Including postage....... |
|
|
|
So.....try again? If you can give me a price for postage then I'm sure we can sort something out Cheers. |
|
|
|
HINT. Answer - is it: a) Greed? b) Uncaring disregard for the Bitcoin Eco-system? c) Shoddy coding? d) Pure greed? e) All of the above? Answers on the offending pools threads please |
|
|
|
Well, it's the pool operators choice of course...but I see it as their loss is p2pools gain. Anyone who wants to merge mine can simply set up their own p2pool node & mine however many merge-mineable coins they want on standard, run-of-the-mill hardware. Merge mining with p2pool increases the hash rate & stability of whatever altcoin they are mining as well as helping decentralize & secure the Bitcoin network at the same time. It's a win/win situation all round. I'm currently merge mining 11 sha256 coins & the number is growing as more & more coins realize the potential growth & stability that merge mining provides - it's also a great way to learn the mining basics, & the p2pool community thread is very knowledgeable as well as helpful too. My 2 satoshi  |
|
|
|
|
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?
|
|
|
|
|
Show Posts
