[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too

[piuk]

Tycho, Any chance you could tag Deepbit's coinbases? Make it easier to detect the Mystery one block miner.

[1713485635]

1713485635

[1713485635]

1713485635

[1713485635]

1713485635

[1713485635]

1713485635

[1713485635]

1713485635

[DeepBit]

Tycho, Any chance you could tag Deepbit's coinbases? Make it easier to detect the Mystery one block miner.

Not yet, sorry.

This site uses block hashes provided by me, so it's always accurate: http://blockorigin.pfoe.be/

[P4man]

Tycho, Any chance you could tag Deepbit's coinbases? Make it easier to detect the Mystery one block miner.

You can use the transaction count of 1 as filter to detect the Mystery miner. Its a crutch but would be fairly accurate for now.

[rjk]

Tycho, Any chance you could tag Deepbit's coinbases? Make it easier to detect the Mystery one block miner.

You can use the transaction count of 1 as filter to detect the Mystery miner. Its a crutch but would be fairly accurate for now.

Deepbit's blocks always go to 1VayNert.... don't they? Could tag them that way.

[iamapi]

I can't connect to http://f1.deepbit.net:8332 but I can connect to http://f2.deepbit.net:8332
However, the miner will always try to connect to f1 then f2, could I connect to f2 directly?

Tycho, Any chance you could tag Deepbit's coinbases? Make it easier to detect the Mystery one block miner.

Not yet, sorry.

This site uses block hashes provided by me, so it's always accurate: http://blockorigin.pfoe.be/

[DeepBit]

I can't connect to http://f1.deepbit.net:8332 but I can connect to http://f2.deepbit.net:8332
However, the miner will always try to connect to f1 then f2, could I connect to f2 directly?

Which miner and what settings are you using ?
Usually setting pool address as http://pit.deepbit.net:8332 is enough for automatic connection.

[kano]

Tycho, Any chance you could tag Deepbit's coinbases? Make it easier to detect the Mystery one block miner.

You can use the transaction count of 1 as filter to detect the Mystery miner. Its a crutch but would be fairly accurate for now.

Deepbit's blocks always go to 1VayNert.... don't they? Could tag them that way.

Eh? No, DeepBit still uses something like bitcoind to put a new address in each new block.

DeepBit: you considered changing that after the last few pool hacks that have occurred elsewhere?
i.e. your mining bitcoinds (or equivalent) can have a wallet with no value if you change it to accept your own fixed address to payout to that's not in that wallet.
... of course this requires the payout code to also be somewhere else ... which should be ... well ... more secure than if it isn't already

[iamapi]

Ufasoft miner

I set the pool address as http://pit.deepbit.net:8332
It will first try to connect to http://f1.deepbit.net:8332, then switch to f2 after f1 failed.
But it will switch back to f1 after some time!
How to avoid this?

I can't connect to http://f1.deepbit.net:8332 but I can connect to http://f2.deepbit.net:8332
However, the miner will always try to connect to f1 then f2, could I connect to f2 directly?

Which miner and what settings are you using ?
Usually setting pool address as http://pit.deepbit.net:8332 is enough for automatic connection.

[iamapi]

The log:
116.9 MHash/s     Switching back to http://f1.deepbit.net:8332
117.1 MHash/s     Error 80072EE2:  The operation timed out

117.1 MHash/s     Error 80072EE2:  The operation timed out

Switching to http://f2.deepbit.net:8332
03/14/12 10:06:43 Result: D56619B1 accepted
116.7 MHash/s     Switching back to http://f1.deepbit.net:8332
116.7 MHash/s     Error 80072EE2:  The operation timed out

116.9 MHash/s     Error 80072EE2:  The operation timed out

Switching to http://f2.deepbit.net:8332
03/14/12 10:22:53 Result: 29F2DFB2 accepted
03/14/12 10:22:54 Result: 26ED1AC9 accepted
117 MHash/s     Switching back to http://f1.deepbit.net:8332
117 MHash/s     Error 80072EE2:  The operation timed out

117 MHash/s     Error 80072EE2:  The operation timed out

Ufasoft miner

I set the pool address as http://pit.deepbit.net:8332
It will first try to connect to http://f1.deepbit.net:8332, then switch to f2 after f1 failed.
But it will switch back to f1 after some time!
How to avoid this?

I can't connect to http://f1.deepbit.net:8332 but I can connect to http://f2.deepbit.net:8332
However, the miner will always try to connect to f1 then f2, could I connect to f2 directly?

Which miner and what settings are you using ?
Usually setting pool address as http://pit.deepbit.net:8332 is enough for automatic connection.

[DeepBit]

How to avoid this?

Looks like a little problem on my side. Hope to fix it soon.

[DeepBit]

Eh? No, DeepBit still uses something like bitcoind to put a new address in each new block.

DeepBit: you considered changing that after the last few pool hacks that have occurred elsewhere?
i.e. your mining bitcoinds (or equivalent) can have a wallet with no value if you change it to accept your own fixed address to payout to that's not in that wallet.
... of course this requires the payout code to also be somewhere else ... which should be ... well ... more secure than if it isn't already :)

Sorry, I don't understand what do you mean :)
Only a small amount is stored online for payments, the rest is in our cold storage.

[kano]

Eh? No, DeepBit still uses something like bitcoind to put a new address in each new block.

DeepBit: you considered changing that after the last few pool hacks that have occurred elsewhere?
i.e. your mining bitcoinds (or equivalent) can have a wallet with no value if you change it to accept your own fixed address to payout to that's not in that wallet.
... of course this requires the payout code to also be somewhere else ... which should be ... well ... more secure than if it isn't already

Sorry, I don't understand what do you mean
Only a small amount is stored online for payments, the rest is in our cold storage.

I'm obviously talking stuff you clearly already know but I'll word it this way to explain what I mean:

At the moment you must be using bitcoind (or a similar program) to generate the getwork answers.
(I'll just assume it is bitcoind, but it could be another program that does the same work required to create a getwork)
When someone requests a getwork, somewhere at the end of the request chain bitcoind replies with the header and the midstate with a payment address that is unused.
When someone sends back a proof of work >= block difficulty, that will of course be to that same payment address, then the next available payment address will be used for all subsequent getwork requests ... until the next block etc.
Thus the bitcoind that is providing the getworks also contains the wallet with the addresses that all the blocks are paid into (and waiting to mature for the next 100 blocks)

If you modify bitcoind to accept an address to pay the blocks into rather then using it's wallet to supply addresses, then the bitcoind does not actually contain any wallet addresses with value and that payment address could be in a wallet anywhere you like
Thus if anyone hacks into the server (or has admin access to it like Linode allowed to happen to slush) they cannot steal much since they firstly will need to restart bitcoind with a new address - which would be rather obvious when it happens - and only any blocks generated after that with the wrong address would be lost - and it's not too hard to see that the address has changed and thus the server has been hacked into and needs something done about it.

[cmg5461]

Statistics don't seem to be updating o.o

Code:

171081 2012-03-14 05:23:03 00000000000002a74060d0dd7f97a6484ac047b0d39c33dc7fe86caee73a8e0d
171079 2012-03-14 04:49:00 000000000000022c9ddc7ade486b22dcf5673c0083d4f89333d30e09bacf147b
171077 2012-03-14 03:45:46 000000000000060baca81bb980618d3def95edfe3b7c70dfa4b9c6a85631d8df
171066 2012-03-14 02:01:29 0000000000000a2b80893930de6f5eddb3fc59a767363963a76b2018cb2a38de
171061 2012-03-14 01:12:17 000000000000040da70c1ac9e7b2fc4e97ab72fa8bd266ba35ecec00e2dd6b49

and from deepbit

Code:

Time/Link Found in Your Total Reward
13.03 20:12:58 0h 06m 177 361842   0.02372444

[DeepBit]

Statistics don't seem to be updating o.o

Code:

171081 2012-03-14 05:23:03 00000000000002a74060d0dd7f97a6484ac047b0d39c33dc7fe86caee73a8e0d
171079 2012-03-14 04:49:00 000000000000022c9ddc7ade486b22dcf5673c0083d4f89333d30e09bacf147b
171077 2012-03-14 03:45:46 000000000000060baca81bb980618d3def95edfe3b7c70dfa4b9c6a85631d8df
171066 2012-03-14 02:01:29 0000000000000a2b80893930de6f5eddb3fc59a767363963a76b2018cb2a38de
171061 2012-03-14 01:12:17 000000000000040da70c1ac9e7b2fc4e97ab72fa8bd266ba35ecec00e2dd6b49

Your source is incorrect. Statistics are updated properly.

[forsetifox]

The block stats show "Average in last 24 hours: 2133680 (+42.5%)" which means terrible luck I think?
According to my rewards I think that makes sense. However I've never seen so many long polls showing up in cgminer today. >.> What's up with that?

[slider1978]

The block stats show "Average in last 24 hours: 2133680 (+42.5%)" which means terrible luck I think?
According to my rewards I think that makes sense. However I've never seen so many long polls showing up in cgminer today. >.> What's up with that?

Longpolls mean a new block is starting, but doesn't mean that deepbit found the block.

[forsetifox]

A new block on the entire bitcoin network?

[DeepBit]

A new block on the entire bitcoin network?

Yes.

[slider1978]

A new blog on the entire bitcoin network?

Add this to your favorites

http://blockchain.info/

[DeepBit]

A new blog on the entire bitcoin network?

Add this to your favorites
http://blockchain.info/

As I said earlier, this site is not 100% accurate, use http://blockorigin.pfoe.be/