I picked this bad boy up for 2BTC about a week ago,

now I'm willing to sell it for 3.5BTC which includes shipping in the continental US.   will ship to Canada for a small bit more

shipping outside of NA/Canada == you pay me first in bitcoins, no escrow

sigh.  nm.

but:

the proper thing to do with all of these would be to mine for maybe a couple of weeks, then sell it off to some random chump that pays way more than it's worth.  they're all over the place in the marketplace section

he said he wanted it to be fairly priced..  even if you don't care about profit, i haven't seen any of those that are priced fairly

set maxconns to 1

then connect=5.9.24.81  (and change it back after it's finished)

i have plenty of bandwidth unless some DoS is going on

Whoops.  No, I was just flat out wrong.  I just looked:

    p2pool_group.add_argument('--max-conns', metavar='CONNS',
        help='maximum incoming connections (default: 40)',
        type=int, action='store', default=20, dest='p2pool_conns')
    p2pool_group.add_argument('--outgoing-conns', metavar='CONNS',
        help='outgoing connections (default: 6)',
        type=int, action='store', default=10, dest='p2pool_outgoing_conns')


--outgoing-conns is the correct thing to use.  i've always just modified the source to change the settings.. not sure where I got --max-outgoing from...  and the --p2pool-node additions don't count towards that total

i'll edit the original message

that'd be based off your hardware then,  i thought the avalons could handle variable difficulty.  maybe it's considering sub 256 stuff as rejects

just thought i'd mention that that's a good price for a 5970, if anyone was looking for one (based off $350 bitstamp btc price atm)..  they still go for around $215 on ebay

ed: well, assuming the shipping charges were actual cost.. and, actually, change 'good' to 'a fair price'..  after I checked ebay =p

bitcoinaddress/x+y

Yeah, the x variable wouldn't do anything unless it was over the base share difficulty which is at 216k right now.  At 15ghash, you shouldnt increase that unless, eh, you're feeling really lucky.  Would have to be over 216,000 to have any impact ..

The Y amount is just used to calculate your hashrate on the webpage.  With pushpool it mattered a lot more, with stratum it doesn't really matter much.  I guess it consumes a little more bandwidth if you're using 1 share difficulty instead of 10-20.  You might as well use the higher #...

there are a lot of these in the marketplace section

Aha!

someone buy them from me then 

i have a fancy motherboard.

an msi 990fxa-gd80

that has been sitting here doing nothing for about 6 months

i have the original box and all that stuff

I'll pay $75, about $5 more than it'd make in 6 months

expired

Now if people will do it... =p

Also, you might have high latency to those three p2pools I suggested to --addnode, just look at the list on http://p2pool-nodes.info/ and find some other well connected ones if so.  I wouldn't add any w/ an average getblocktemplate time of over .3s, since those are probably overloaded as is... well, either that, or they may be experiencing this issue (as referenced above):



immediate action is recommended in such cases

... and I thought I'd add that most orphans directly after a block is solved are unavoidable, as p2pool will (usually) orphan the share that was directly before the block solve (or it may have been a few seconds after, which is the reason for it doing that... but 95% of the time it's a legit share that just gets jacked). 

p2pool problem:

People see this 20% DOA/stale shit and are like "OMG, 20% less monies!1", instead of saying 'lol, someone has some shitty setup that's improving my relative efficiency, they are losing hundreds of thousands of ugandan dollars'.    too bad that in the long run, you want people to not be dumb and be able to set up p2pool properly.

tip #1:  TI-99's and Commodore 64's are not adequate to run p2pool servers on.  either spend a couple hundred bucks getting a subpar computer that can run p2pool decently, pay $10 or $20 to OVH for server hosting, or (gasp) mine on a remote server.  there are plenty out there that are at 0%.  mine is at 1%, but that 80% efficiency you're getting to your Commodore is a lot worse than paying a 1% fee.  try http://p2pool-nodes.info/ and http://p2pool.hostv.pl/

tip #2:  

run p2pool with

./run_p2pool.py (any other flags) --p2pool-node 5.9.24.81 --p2pool-node 198.12.127.2 --p2pool-node 64.120.253.194 --outgoing-conns 5

that means if all 3 of those servers are up (and not full on incoming connections, being DDoSed, DoSed, or being raided by the Interpol for stealing massive amounts of bitcoins), you'll have 8 outgoing connections.  if none are up, you'll have 5.  default is 6.  that's not bad, right?   if you have enough bandwidth, then allow some incoming connections.  i think 40 is too much, but 20-25 is ok.

tip #3:  after about 30 minutes, look at your share history.  see which nodes you're actually receiving shares from.  if they're incoming connections, test port 9333 by trying to telnet to it first.  include those in your --p2pool-node list.  


tip #4:  high getblocktemplate latency isn't a huge deal...  except it's symptomatic of also having horrible performance issues, probably either RAM or CPU related and also often caused by having an old version of bitcoind, filled with horse staple battery transactions.  migrate off of the Atari 400 and/or fix your bitcoind, and/or reduce maxblocksize from 1000000 to 500000 or 250000.

tip #5:  use xxx:9332/pings .. if someone is at 2000ms latency, then either their bandwidth is saturated or their Amiga is having issues.  tcpkill them for a new connection..  somewhat related, use xxx:9332/peer_txpool_sizes to see all the people that are trying to help out horse staple battery get those transactions processed

tip #6: don't pay 2% fees to a pool with 70% efficiency

aha!  forgot to mention bitcoind

tip #7: compile bitcoind with outgoing connections of 1, run bitcoind with listen=1, maxconnections=2, with one node on connect... well, that's what I do, since I can monitor it constantly.. you'd probably want to change maxconnections to 3 or 4, in case one of the nodes craps out, be it due to the Interpol, cult of the dead cow, or whatever else.  an example conf file,

server=1
daemon=1
rpcuser=bleat
rpcpassword=bleatbleat
#datadir=/home/zevus/ramdisk
maxconnections=2
rpcallowip=127.0.0.1
rpcport=31337
port=31338
#timeout=150
#dbcache=xxx
par=8
listen=1       (<--- necessary cause of p2pool)
gen=0
upnp=0
keypool=0  (you don't store bitcoins on this wallet, right?  right?)
dns=0
detachdb=1
logtimestamps=1
bantime=30
banscore=501
#blockminsize=0
#blockprioritysize=0
blockmaxsize=250000

#Myself
connect=5.9.24.81
#connect=198.12.127.2
#connect=64.120.253.194

..... now, I don't think w/o compiling it yourself you can modify the 8 outgoing connections?  i think in that case, maxconnections of 9, listen=1, and just using 'connect' and firewalling the incoming bitcoind port would still work?  it's not supposed to connect to other nodes, anyway...  (besides the one you use connect= on, which is the difference between that and addnode)

ed: fixed --max-outgoing to real flag of --outgoing-conns

3.5 is insane, crazy, fool price.  The price someone that didn't know about bitcoins until a month ago would pay

and if someone is paying 3.5, now would be the time to sell your 60ghash units

lol

That's not reasonable at all, at the difficulty level now, you'd expect around $9.50, in about 6 1/2 days that'll drop, in 10-11 days that'll drop some more, and in 10-11 days that'll drop some more.

End result would be something around $8 if we use the extremely generous MtGox exchange rate.  If you think bitcoins are going to go up, then you should buy bitcoins, not give money away.

It's 30ghash for $600,

so,   quite horrible

and this investment you're making back, it'll come to a standstill in a couple of months

you know, the whole .1, .075, 0.056, 0.042, 0.032, 0.024, 0.018, 0.013, 0.010 thing.

approx. 10-11 days in between each


that's not a lot of monies.