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

[[Tycho]]

Great explanation and if I follow correctly, over say a 24 hour period, the blocks that I fully participate in my reward share % should converge towards my pool speed % ( which again is based on the (un)lucky MH/s meter ).

Yes.

[SteveB]

There is no doubt that everybody likes a free lunch.

May I also have a free dessert after the free lunch? 

There always will be someone to accept free txes.
We just have to find a way to fight off the bad guys who are flooding to make fees mandatory

Let's hope a solution can be found before it is too late.

[[Tycho]]

There always will be someone to accept free txes.
We just have to find a way to fight off the bad guys who are flooding to make fees mandatory :)

Let's hope a solution can be found before it is too late.

I'm glad that this problem appeared before bitcoin become widely recognized, so we have time to work on it.

[marcus_of_augustus]

I don't see why we cannot just make default fees miniscule as to be insignificant, i.e. 1millibitcent (0.00001 BTC) or similar, but more than zero to discourage spamming TXs.

[jkminkov]

if I run bitcoin server, does that helps free transactions

[marcus_of_augustus]

[Tycho],

just for informational purposes and in the interests of transparency, do you have a personal rig connected to your pool?

Or any rig, connected to other pools, or solo mining?

[[Tycho]]

if I run bitcoin server, does that helps free transactions ???

Not really if you aren't mining at many GH/s. Including free transactions in block helps, but you need to create new blocks in order to do this, like my pool is doing.

[Tycho],just for informational purposes and in the interests of transparency, do you have a personal rig connected to your pool?
Or any rig, connected to other pools, or solo mining?

Yes, i'm mining at about ~900 MH/s.

[jgarzik]

FYI, the longpoll specification should say POST, not GET.

It is incorrect for GET to be receiving data in the body of the HTTP request (the JSON-RPC payload).  This confuses HTTP libraries.

[[Tycho]]

FYI, the longpoll specification should say POST, not GET.
It is incorrect for GET to be receiving data in the body of the HTTP request (the JSON-RPC payload).  This confuses HTTP libraries.

As i already answered in IRC, everything is correct, since there is no body in this request.

We may create a different thread for discussing long polling because it's dev thing.

[dooman]

Currently I'm not able to login to deepbit site with my account 

[nster]

Currently I'm not able to login to deepbit site with my account 

I'm logged in fine

[dooman]

Currently I'm not able to login to deepbit site with my account  

I'm logged in fine

It says wrong password. I have tried every pass I usually use but it didn't worked.

Is there a way to reset my password?

[[Tycho]]

Currently I'm not able to login to deepbit site with my account  ???

I'm logged in fine

It says wrong password. I have tried every pass I usually use but it didn't worked.
Is there a way to reset my password?

I was modifying login function this morning, this may be a reason for someone to temporary see login problems.
Are you still unable to login at this moment ? PM me your login name and i'll fix it.

[dacoinminster]

I checked out this pool this morning, because I am interested in diversifying so I don't have all my eggs in one basket.

Only one thing stops me from moving some of my workers over here. My setup makes the unchangeable numeric naming of workers really inconvenient. I'll have to remember which number is which worker, and each worker migrated here would have to use a number rather than its already-assigned name. I thought about just creating a bajillion workers on your site and then just having each worker run a checksum on its name to determine its number on your server, but that only solves half the problem and might annoy you guys.

If you allow me to customize alphanumeric worker names, then I'll migrate some workers here right away.

Other than that, the pool looks awesome.

Thanks!

[wootwoot]

I am having a strange issue with yesterdays payout. It says 0/unconfirmed and at the bottom of the bitcoin client it reads "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

[[Tycho]]

I am having a strange issue with yesterdays payout. It says 0/unconfirmed and at the bottom of the bitcoin client it reads "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."

What is the version of your client ? PM me your login name.

[[Tycho]]

Only one thing stops me from moving some of my workers over here. My setup makes the unchangeable numeric naming of workers really inconvenient. I'll have to remember which number is which worker, and each worker migrated here would have to use a number rather than its already-assigned name. I thought about just creating a bajillion workers on your site and then just having each worker run a checksum on its name to determine its number on your server, but that only solves half the problem and might annoy you guys.

If you allow me to customize alphanumeric worker names, then I'll migrate some workers here right away.

I don't understand what you wanted to do with checksums. My "flood protection" wouldn't allow creating a lot of workers in a short timespan.
Will it be enough for you if i'll allow customizing the name part after "_" character ?

[dacoinminster]

Will it be enough for you if i'll allow customizing the name part after "_" character ?

That is exactly what I want! That way I can set up:

me_5770
me_5870-FriendBob
me_5870-I7PC
me_5870-oldPC
me_5970-GPU0
me_5970-GPU1

etc

Please let me know as soon as I can do something like that!

Thanks.

[hacim]

I'm having a new problem that just started:

backend (http://127.0.0.1:5847/) connect error:
Connection to http://127.0.0.1:5847 refused

I have my bitcoind running locally, and the username/password are set properly, and I haven't changed anything. It just started.

[LordZer]

Keep getting this randomly...
 


[2011-02-25 17:17:35] JSON-RPC call failed: {
   "code": -1,
   "message": "backend (http://127.0.0.1:5847/) connect error:Connection to http
://127.0.0.1:5847 refused"
}
[2011-02-25 17:17:35] json_rpc_call failed, retry after 30 seconds