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

[finway]

Because he promised, and this is his duty.

[1713941052]

1713941052

[1713941052]

1713941052

[1713941052]

1713941052

[1713941052]

1713941052

[1713941052]

1713941052

[os2sam]

Because he promised, and this is his duty.

Why implement it at all?  Nobody has made a real argument which proves the need.  So, again, why?

[finway]

Why implement it at all?  Nobody has made a real argument which proves the need.  So, again, why?

That's you, i guess.

[os2sam]

Why implement it at all?  Nobody has made a real argument which proves the need.  So, again, why?

That's you, i guess.

I'm glad to see that you have thought it through so thoroughly.  That's about par for the course though.
Sad,
Sam

[makomk]

There are conscious on supporting BIP16, cause it will make bitcoin more safe.
as you can see, slush & BTCGuild are supporting BIP16,
and more than 5 TOP10 pools are supporting BIP16,
You are acting against it, you're not making bitcoin safe.

Errrm, you might want to read my post in the Technical Discussion subforum. Turns out that once BIP16 is enabled, all other miners will be forced to upgrade pronto or risk losing money. (In fact, arguably it's even worse than that - apparently if BIP16 went live with only 55% of mining power supporting it it'd make 6 confirmation double-spend attacks against old nodes quite a bit easier than they ought to be.)

[finway]

There are conscious on supporting BIP16, cause it will make bitcoin more safe.
as you can see, slush & BTCGuild are supporting BIP16,
and more than 5 TOP10 pools are supporting BIP16,
You are acting against it, you're not making bitcoin safe.

Errrm, you might want to read my post in the Technical Discussion subforum. Turns out that once BIP16 is enabled, all other miners will be forced to upgrade pronto or risk losing money. (In fact, arguably it's even worse than that - apparently if BIP16 went live with only 55% of mining power supporting it it'd make 6 confirmation double-spend attacks against old nodes quite a bit easier than they ought to be.)

OP_EVAL are more disruptive,right? why you like it?

[slider1978]

Hi, why aren't all pools implementing real accounts (payout AND payin) so that they can act like banks with mobile clients that use QR code scanning and transfer money with a click on your smartphone?

Because you haven't started one yet.  That's the beauty of Bitcoin right now...See a need, fill a need, profit. PM me if your interested in a Bitcoin account.

[Definit]

why do i have less shares but more gh/s...is that something that im obviously doing wrong, or missing?

4     Definit (You)       287686   9.99 GH/s
5     ******            33198117   9.53 GH/s

[DeepBit]

why do i have less shares but more gh/s...is that something that im obviously doing wrong, or missing?

4     Definit (You)       287686   9.99 GH/s
5     ******            33198117   9.53 GH/s

Because it's total figure. He just started earlier :)

[DeepBit]

Hi, why aren't all pools implementing real accounts (payout AND payin) so that they can act like banks with mobile clients that use QR code scanning and transfer money with a click on your smartphone?

Yes, it's very easy to implement, but I'm intentionally not doing this because it would require a completely different approach on security and responsibility.
I don't want people to store their savings in the pool because it's NOT a bank.

[eleuthria]

Hi, why aren't all pools implementing real accounts (payout AND payin) so that they can act like banks with mobile clients that use QR code scanning and transfer money with a click on your smartphone?

Most pool owners would prefer you get your coins off their servers rather than hold them for you.  You see probably once a month or more some pool/exchange getting "hacked" and losing coins.  While I don't believe any major pools (Slush, Deepbit, BTCGuild, Eligius, ArsBitcoin, EMC) has had ever had their wallet hacked [which is why I still suspect most/all of the "hacked" pools are just thieves], that doesn't mean it can't happen.  Being a major pool comes with the expectation that if something goes wrong, the pool op will fix it out of their own pocket.

[pirateat40]

Hi, why aren't all pools implementing real accounts (payout AND payin) so that they can act like banks with mobile clients that use QR code scanning and transfer money with a click on your smartphone?

Most pool owners would prefer you get your coins off their servers rather than hold them for you.  You see probably once a month or more some pool/exchange getting "hacked" and losing coins.  While I don't believe any major pools (Slush, Deepbit, BTCGuild, Eligius, ArsBitcoin, EMC) has had ever had their wallet hacked [which is why I still suspect most/all of the "hacked" pools are just thieves], that doesn't mean it can't happen.  Being a major pool comes with the expectation that if something goes wrong, the pool op will fix it out of their own pocket.

You mean Graet is a scammer?  I'm telling mom!!! jk

[Technomage]

Deepbit operator Tycho has said that he will follow the majority in the P2SH debate. The majority has spoken, over 50% of the hashing power (Deepbit excluded) is supporting BIP 16. Everyone is waiting for his move right now. What is going on?

Unless he co-operates soon, there should be a further awareness campaign regarding the issue at hand, directed at Deepbit users. Going forward with P2SH is a significant step forward for the development of Bitcoin, we can't let one man stall it.

I think it was a smart move from Tycho to not be proactive on this issue but I hope that he comes to his senses now and does the right thing. The other pools have spoken.

[rjk]

Deepbit operator Tycho has said that he will follow the majority in the P2SH debate. The majority has spoken, over 50% of the hashing power (Deepbit excluded) is supporting BIP 16. Everyone is waiting for his move right now. What is going on?

Unless he co-operates soon, there should be a further awareness campaign regarding the issue at hand, directed at Deepbit users. Going forward with P2SH is a significant step forward for the development of Bitcoin, we can't let one man stall it.

I think it was a smart move from Tycho to not be proactive on this issue but I hope that he comes to his senses now and does the right thing. The other pools have spoken.

Would you mind linking us to some nice graphs and/or charts to prove that more than 50% of the network already is showing their support?

[Technomage]

Would you mind linking us to some nice graphs and/or charts to prove that more than 50% of the network already is showing their support?

Approximately 36% of the network is currently voting for P2SH. Deepbit has 34% of the network which means that excluding Deepbit there is a 54.54% support for P2SH.

That is the only sane way of calculating it, asking for over 50% of total hashing power without Deepbit's support is insane and I see little chance of any vote going through in my lifetime if that is required. I assume Tycho didn't mean that when he talked about majority support.

True majority support is behind P2SH, I seriously doubt that people mine at Deepbit because they protest to P2SH.

http://blockchain.info/p2sh
http://blockchain.info/pools?timespan=4days

[eleuthria]

Not to mention the p2sh support graph was higher a few days ago than it is currenty, BTC Guild had some technical issues and produced less than half as many blocks as normal in the past two days [not counting today].

[finway]

[Tycho]: BIP16 is waiting for you. 

[Graet]

Hi, why aren't all pools implementing real accounts (payout AND payin) so that they can act like banks with mobile clients that use QR code scanning and transfer money with a click on your smartphone?

Most pool owners would prefer you get your coins off their servers rather than hold them for you.  You see probably once a month or more some pool/exchange getting "hacked" and losing coins.  While I don't believe any major pools (Slush, Deepbit, BTCGuild, Eligius, ArsBitcoin, EMC) has had ever had their wallet hacked [which is why I still suspect most/all of the "hacked" pools are just thieves], that doesn't mean it can't happen.  Being a major pool comes with the expectation that if something goes wrong, the pool op will fix it out of their own pocket.

mm yer, or they havent dislosed they have been comprominsed.... It is easy to suspect with no investagation or knowledge....like [which is why I still suspect most/all of the major pools have at some time been hacked]
-see what i did there? - there is enough fud thrown round the forums, poolops should set an example not make it worse...

When Ozcoin was hacked recently I was prepared to cover any losses, but due to some good people in the community we were helped through this.
Random accusations are random, lets try to keep it to facts )
Graeme

[Fiyasko]

Gah Deepbit whats wrong with you?

Code:

 cgminer version 2.1.2 - Started: [2012-02-22 10:49:29]
--------------------------------------------------------------------------------
 (5s):331.2 (avg):609.3 Mh/s | Q:28505  A:25074  R:64  HW:0  E:88%  U:8.43/m
 TQ: 1  ST: 0  SS: 51  DW: 1363  NB: 332  LW: 0  GF: 112  RF: 149
 Connected to http://pit.deepbit.net:8332 with LP as user ___________
 Block: 000001b45780cb1cb1d5f66ee975187f...  Started: [12:20:59]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  64.0C  40%    | 314.3/304.2Mh/s | A:12581 R:32 HW:0 U:  4.23/m I: 3
 GPU 1:  65.0C  40%    | 439.1/305.2Mh/s | A:12493 R:32 HW:0 U:  4.20/m I: 3
--------------------------------------------------------------------------------

[2012-02-24 12:24:18] Pool 0 not providing work fast enough
[2012-02-24 12:24:53] Pool 0 communication resumed, submitting work
[2012-02-24 12:24:53] Accepted 00000000.4e68a616.2f23a60a GPU 1 thread 1
[2012-02-24 12:24:53] Accepted 00000000.063b83c7.84ad558f GPU 0 thread 2
[2012-02-24 12:24:53] Accepted 00000000.c7960201.c8289535 GPU 0 thread 0
[2012-02-24 12:24:54] Accepted 00000000.6b58e6e8.b8ff2c1d GPU 1 thread 1
[2012-02-24 12:24:56] Pool 0 communication failure, caching submissions
[2012-02-24 12:24:57] Pool 0 communication resumed, submitting work
[2012-02-24 12:24:57] Accepted 00000000.7348486d.dd80b66c GPU 0 thread 2
[2012-02-24 12:25:07] Pool 0 not providing work fast enough
[2012-02-24 12:25:19] Pool 0 http://pit.deepbit.net:8332 not responding!
[2012-02-24 12:25:19] Pool 0 communication failure, caching submissions

Edit: It was prolly my fault

[cmg5461]

Gah Deepbit whats wrong with you?

Code:

 cgminer version 2.1.2 - Started: [2012-02-22 10:49:29]
--------------------------------------------------------------------------------
 (5s):331.2 (avg):609.3 Mh/s | Q:28505  A:25074  R:64  HW:0  E:88%  U:8.43/m
 TQ: 1  ST: 0  SS: 51  DW: 1363  NB: 332  LW: 0  GF: 112  RF: 149
 Connected to http://pit.deepbit.net:8332 with LP as user ___________
 Block: 000001b45780cb1cb1d5f66ee975187f...  Started: [12:20:59]
--------------------------------------------------------------------------------
 [P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
 GPU 0:  64.0C  40%    | 314.3/304.2Mh/s | A:12581 R:32 HW:0 U:  4.23/m I: 3
 GPU 1:  65.0C  40%    | 439.1/305.2Mh/s | A:12493 R:32 HW:0 U:  4.20/m I: 3
--------------------------------------------------------------------------------

[2012-02-24 12:24:18] Pool 0 not providing work fast enough
[2012-02-24 12:24:53] Pool 0 communication resumed, submitting work
[2012-02-24 12:24:53] Accepted 00000000.4e68a616.2f23a60a GPU 1 thread 1
[2012-02-24 12:24:53] Accepted 00000000.063b83c7.84ad558f GPU 0 thread 2
[2012-02-24 12:24:53] Accepted 00000000.c7960201.c8289535 GPU 0 thread 0
[2012-02-24 12:24:54] Accepted 00000000.6b58e6e8.b8ff2c1d GPU 1 thread 1
[2012-02-24 12:24:56] Pool 0 communication failure, caching submissions
[2012-02-24 12:24:57] Pool 0 communication resumed, submitting work
[2012-02-24 12:24:57] Accepted 00000000.7348486d.dd80b66c GPU 0 thread 2
[2012-02-24 12:25:07] Pool 0 not providing work fast enough
[2012-02-24 12:25:19] Pool 0 http://pit.deepbit.net:8332 not responding!
[2012-02-24 12:25:19] Pool 0 communication failure, caching submissions

Edit: It was prolly my fault

I'm having the same problems.  I'm at like.. 25% rejection rate on my rig.