Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 235. (Read 1601465 times)

Veldy, here is my stale %.   Pheonix 1.48.

Are these high? Don't remember from when I was running straight Poc.

12785 (0.75%)   Prop.
13525 (1.00%)   Prop.
11948 (1.09%)   Prop.
11934 (1.13%)   Prop.
11840 (0.90%)   Prop.
13325 (0.75%)   Prop.

Also I've managed to get the same speed on Phoenix versus straight Poc.  There doesn't seem to be any massive difference in hash speed on deepbit either.  I'm using 30 minute average.

To be honest sms confirmation will just generate costs. Ppl should rather secure by sending mined BTC more often than just waiting for them to be stolen in some way.

It's for those who know what they are doing. And there is a warning e-mail that says clearly that it's permanent.
E-mail confirmation is not secure enough because e-mail accounts can be stolen, so I provided just an option for really concerned people.

And BTW, they should make backups of their wallet.dat

This is optional feature, just for those who want it.
Also i'm thinking about some SMS confirmation support, this may add more security.

Since Phoenix doesn't really suits my rigs I don't have much of a personal experience.
But I know that there was a bug that caused submitting a stale share after LP notice (may be already fixed).
And many users have reported that they see higher speed in Phoenix's console than in reality.

@Veldy
By lockup I mean that page as well as miner can't reach server/site/whatever those two are connecting (not sure what exacly is locked in miner, but 'connection problems' appears). Meanwhile all other sites are working.

Quick props to Tycho:  I caught up on this thread from the beginning and didn't really expect your sanity still to be intact by the time I got to the end.  Keep up the good work!

What locked up?  Your router or your mining software?  As for lost wallets; that is really up to you to keep that from happening.  I am sure most people keep a periodic backup in a safe and recoverable place [I even kept my old wallet when I replaced it].  If you are worried about losing your wallet [which you shouldn't be if you are doing as suggested many times in these forums and elsewhere], then don't push that button

Awesome!   I mean, that you would say so, since you do payout invalid blocks and invalid blocks do occur, you didn't have to say so

If you do this, does this mean that you have to create a new account if you need a new address?  I just wiped out my old wallet and started a new wallet and changed my address for the obvious reason, so I won't be locking my address down.  As a collarary to your new feature; are you going to offer the option to delete an account?  It would help avoid stale accounts if one is forced to create a new account [and this would also allow one to use the same email address if you implement it that way].

I think that in THIS case it was caused by a bug in my part. I'm fixing it.

Actually rig is connected by cable, so there is nothing about signal strength. Rhis rig (and my mining career) started 15 days ago, first lockup 5 days ago and last one today. Of course there were other lockups of random pages even months before I started mining.

@Tycho
Making it really permanent will just create tons of PM's from ppl that lost their wallet file and want to change address, cuz of like 10 BTC on page acc

UPDATE:

Now you can lock your bitcoin address forever. Yes, that really means "forever" and there will be no way to unlock it.
Press the button at the very bottom of advanced settings page, check that confirmation e-mail contains YOUR bitcoin address and click the link.

Generally, two workers found the solution for a block at almost an identical time and it is just a matter of which block chain grows the fastest after that [which means, generally, that the first one in wins, but statistically, that might not always be so due to various reasons].  It is natural.  Now, if every block started to show up as invalid ... it would indicate an attack, but I have never seen two in a row or even two in a moderate time frame of hours.

Just the cost of mining ... somebody might solve it almost exactly when you do and it essentially becomes a coin toss whose solution turns up as the valid one.

Something that no other pool does  Although the number of blocks lost as invalid is pretty small all things considered.  Not sure the actual percentage of total payout affected, but looking at deepbit and other pools, I would say it is pretty rare [probably less than once or twice per week].  Tycho ... any idea?  Anyway, a great feature you offer (necessitated by the instant payout feature I suspect).

Well, I know about payment, but how this thing could happen? It's some kind of "stale" share in the pool, but in bitcoin network, right?

I have been doing some pool jumping lately for testing purposes [still haven't tried BTC Guild or the Eligius].  The main testing I am is with miner performance.  I am only testing with two miners; Phoenix 1.48 and GUIMiner - v2011-05-21.  In particular, I care about stale/invalid shares.  Obviously, slush loses on that since there is no long polling and I did not test that [I recall the number was always over 1% when I used the pool].  However, there has been one big surprise.   Phoenix 1.48 generates a LOT more invalid shares than GUIMiner when using deepbit, but works fabulously with BTCMine for instance.  I am wondering if anybody else has noticed this.  After several thousand shares, I would range between 0.45% and 0.8% [over 2% for for the first thousand shares in the worst case].  I am seeing a high number of these now, so I just switched over to GUIMiner and will let it run and see, but over several attempts, the number of invalid shares has been less than half of what Phoenix is spitting out.  Is there an issue with long polling either with Phoenix or deepbit such that the two don't play well together?  I originally thought it might be the larger faster pool, but then it occurred to me that a long polling message should be pushed at the same rate for all pools.

Any idea why this might be?  Anybody else experience such an issue and willing to do a comparison themselves?

Worth noting is that the share count listed by the pool matches perfectly with the client [although with some pools like BTCMine, you have to wait a bit for the share count catch up on the web page which means you have to stop mining for a bit or use a new worker].  Deepbit makes this type of testing a breeze   I like Phoenix, because I plan to use it on my linux box when it is up and running [bad mobo ... fixed tomorrow and online this weekend] and I like it's interface.  I may have to use poclbm [which isn't bad mind you], but would prefer Phoenix.

Tycho - are you aware of any issues with Phoenix and deepbit?

I have not had good luck woth Belkin anything, but as always, your mileage may vary.  Is your mining client working over wireless?  G or N?  Does your router show you the signal strength as seen by the router [not as seen by your client machine]?

For instance, my router shows:

Number Of Wireless Clients – 2.4GHz Band: 3
SSID                   MAC Address   IP Address           Mode   Rate               (Mbps)   Signal (%)
MYSSID             xxxxxxxxxxxxx   192.168.1.xxx   802.11g                 54   80
MYSSID               xxxxxxxxxxxxx  192.168.1.xxx   802.11g                 54   82
MYSSID               xxxxxxxxxxxxx  192.168.1.xxx   802.11n (2.4GHz)    108   66   <== one miner is on this machine in the basement
MYSSID5      xxxxxxxxxxxxx  192.168.1.xxx   802.11n (5GHz)         162   64

As you can see, the transfer rates are good.  Testing on my network [tcpdump, nmap, ping, etc] all show a quality connection and all is good.  My Comcast cable connection is almost custom goodness due to Comcast taking a personal interest in getting everything running properly for me since I was a very early adopter of the DOCSIS 3.0 22Mbps/5Mbps service   Flawless on Comcast's side for months and months.

So, check your router, your network, your DNS, and your connectivity [as well as error rates and signal strength of your cable modem or DSL router (modem) as required].

That's because you're a dumbass.  Try reading a bit more and thinking about it.  If that doesn't work maybe you should go ask in a non-deepbit thread about solo mining.  Just a thought, you might get better responses?  (Although it seems like the ones you got have been perfectly acceptable you just aren't noticing the solution right in front of your nose.)

This block was orphaned by the blockchain. Don't worry, you still received your payment for it.

Both lockups appeared when there was noone at home and nothing else than miner was using network.

Router is Belking F5D7632 ( All I've found on it). Changed DNS and gonna wait for next lockup.

Found out taht installed firmware is from 2005 and newest one from 2007 (but actual version seems to be same). Should I bother to change it?