Pages:
Author

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

sr. member
Activity: 369
Merit: 250
DeepBit, when is the round time going to be fixed? o.o
This information was not important because precise block timestamps are provided anyway in the first column. But ok, I enabled it.

Thank you, it's just nice to see it, rather than calculating it in my head Cheesy
donator
Activity: 532
Merit: 501
We have cookies
That sounds correct for the short 29 share round but I would of at least expected a few hundred shares out of the 96659 round. The fact that I didn't even get 1 with 11 gh/s is what seems wrong.
You should get more than 260 shares from 96659-shares round. But this also may depend on your miner, your hardware (if you using something non-standard) and your luck.
This round was 2-minutes long, so if you don't get even a single share this may mean that something may be wrong with your miner. May be it was switched to your backup pool for some reason ?

Did you get any shares from 5868-long round ?
member
Activity: 87
Merit: 10
Lucky you. I didn't get any shares that round with 11gh/s and I also didn't get any out of the round with 96659 shares. I got 29 shares out of the 5868  round so I don't understand how I could not get at least 1 share out of the round with 96659. I'll have to keep a eye on this as it seems strange to me.
With such a short round it mostly depends on how "lucky" was the getwork you got at the start and how fast did you received it.
Even someone with a slower miner can win if his share was found at the start of the nonce range for that specific getwork.

That sounds correct for the short 29 share round but I would of at least expected a few hundred shares out of the 96659 round. The fact that I didn't even get 1 with 11 gh/s is what seems wrong.
donator
Activity: 532
Merit: 501
We have cookies
DeepBit, when is the round time going to be fixed? o.o
This information was not important because precise block timestamps are provided anyway in the first column. But ok, I enabled it.
sr. member
Activity: 369
Merit: 250
DeepBit, when is the round time going to be fixed? o.o
donator
Activity: 532
Merit: 501
We have cookies
Lucky you. I didn't get any shares that round with 11gh/s and I also didn't get any out of the round with 96659 shares. I got 29 shares out of the 5868  round so I don't understand how I could not get at least 1 share out of the round with 96659. I'll have to keep a eye on this as it seems strange to me.
With such a short round it mostly depends on how "lucky" was the getwork you got at the start and how fast did you received it.
Even someone with a slower miner can win if his share was found at the start of the nonce range for that specific getwork.
member
Activity: 87
Merit: 10
12.04 01:48:21   -    1   26     1.86538462

holy shit!  that share just made my day!



Lucky you. I didn't get any shares that round with 11gh/s and I also didn't get any out of the round with 96659 shares. I got 29 shares out of the 5868  round so I don't understand how I could not get at least 1 share out of the round with 96659. I'll have to keep a eye on this as it seems strange to me.
legendary
Activity: 1190
Merit: 1000
www.bitcointrading.com
12.04 01:48:21   -    1   26     1.86538462

holy shit!  that share just made my day!

legendary
Activity: 3583
Merit: 1094
Think for yourself
Wow, I got twice as much BTC last night than normal!  Luck FTW!

Did you find any shares in that 26 share block?  I wouldn't have minded getting a couple of those Smiley.  But alas I didn't. Sad
Sam
legendary
Activity: 1190
Merit: 1000
www.bitcointrading.com
Wow, I got twice as much BTC last night than normal!  Luck FTW!
donator
Activity: 532
Merit: 501
We have cookies
I found a funny bug in Deepbit JSON API. When I pay out the exact amount on the balance, leaving balance at 0.0, I get this (incorrect) value of confirmed_reward:

"confirmed_reward":1.0e-8

Can anyone fix this?
Thanks for your report :)
I'll fix it.
sr. member
Activity: 529
Merit: 271
I found a funny bug in Deepbit JSON API. When I pay out the exact amount on the balance, leaving balance at 0.0, I get this (incorrect) value of confirmed_reward:

"confirmed_reward":1.0e-8

Can anyone fix this?
donator
Activity: 532
Merit: 501
We have cookies
I was a bit short sighted on that one. You are right that it should only affect the difficulty.
The only way it could be affecting my rewards were if it were confusing Deepbit every time it orphaned a block but I don't see that as a possibility.
No, MM is not affecting our mining in any way.
Only luck and difficulty are important.

If you aren't loosing any shares then your reward should be correct.
hero member
Activity: 560
Merit: 500
Quote
The difficulty just went up.

Not by the same percentage as the drop in rewards though. It looks like difficulty increased by about 10% which should give me about .32BTC per day not .20-.25

[Edit]

After some research this appears to be a direct result of the so called mystery miner. Time will tell if this can be reverse or if it is going to be a permanent problem for Bitcoin.
Well besides the difficulty difference, you might also be losing to hoppers. How would the mystery miner affect it, unless he is somehow stealing your hashes (not possible)?

I was a bit short sighted on that one. You are right that it should only affect the difficulty.

The only way it could be affecting my rewards were if it were confusing Deepbit every time it orphaned a block but I don't see that as a possibility.
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
Quote
The difficulty just went up.

Not by the same percentage as the drop in rewards though. It looks like difficulty increased by about 10% which should give me about .32BTC per day not .20-.25

[Edit]

After some research this appears to be a direct result of the so called mystery miner. Time will tell if this can be reverse or if it is going to be a permanent problem for Bitcoin.
Well besides the difficulty difference, you might also be losing to hoppers. How would the mystery miner affect it, unless he is somehow stealing your hashes (not possible)?
hero member
Activity: 560
Merit: 500
Quote
The difficulty just went up.

Not by the same percentage as the drop in rewards though. It looks like difficulty increased by about 10% which should give me about .32BTC per day not .20-.25

[Edit]

After some research this appears to be a direct result of the so called mystery miner. Time will tell if this can be reverse or if it is going to be a permanent problem for Bitcoin.
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
Is it just me or is Deepbit finding a lot less blocks than it used to? I went from average rewards of .35BTC per day to .20-.25 with no change in hashing power. I originally thought my ISP might causing issues because I would see random server down-times but that hasn't happened in at least week. My average reward per block hasn't changed much but my total rewards haven't gone back up to their previous levels, making me suspect that the pool is finding less blocks than it used to.

Can anyone confirm this?>
The difficulty just went up.
hero member
Activity: 560
Merit: 500
Is it just me or is Deepbit finding a lot less blocks than it used to? I went from average rewards of .35BTC per day to .20-.25 with no change in hashing power. I originally thought my ISP might causing issues because I would see random server down-times but that hasn't happened in at least week. My average reward per block hasn't changed much but my total rewards haven't gone back up to their previous levels, making me suspect that the pool is finding less blocks than it used to.

Can anyone confirm this?>
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
No, it's not how it works.
If I send normal TX and the block with it gets orphaned, this TX will be automatically re-mined again.
But if block with coinbase TX is orphaned, this TX won't be re-mined automatically and I'll need to check it after 100 blocks and if it's lost then there is another 20 hours period to wait.
This is the main point. Since Deepbit pays for invalid blocks, coinbase payments will not work properly without a lot of additional hassle.
donator
Activity: 532
Merit: 501
We have cookies
1. 120-blocks limit is not a network-enforced rule, only the "official" client works that way. Network-enforced period is somewhere around 101 blocks.
I find that rather disturbing that you of all people would make that statement.
Well, it's expected that I know how mining works :)


The code in the current client indeed does say:
Code:
static const int COINBASE_MATURITY = 100;
& in GetBlocksToMaturity():
return max(0, (COINBASE_MATURITY+20) - GetDepthInMainChain());
and the earliest src I have on my computer at the moment: bitcoin-0.3.19, says that also.
Of course I can write my own client to create a transaction worth 100 times my BTC balance, but no one's clients would accept it because that breaks the "Bitcoin rules"
Why do you think it says "COINBASE_MATURITY = 100" instead of 120 ? :)
Official client won't create TXes with coins younger than 120, but will happily accept at 101.
Code:
            // If prev is coinbase, check that it's matured
            if (txPrev.IsCoinBase())
                for (const CBlockIndex* pindex = pindexBlock; pindex && pindexBlock->nHeight - pindex->nHeight < COINBASE_MATURITY; pindex = pindex->pprev)
                    if (pindex->nBlockPos == txindex.pos.nBlockPos && pindex->nFile == txindex.pos.nFile)
                        return error("ConnectInputs() : tried to spend coinbase at depth %d", pindexBlock->nHeight - pindex->nHeight);


Quote
And no, you won't "certainly" have the BTC at 120 blocks because the block can be orphaned. This should be checked by a special routine and re-sent if something happens.
Yeah OK, of course orphaned blocks can mean delays, however that is the whole point of the 100+20 code to ensure that the probability of a coinbase generation ever being orphaned once it gets to 120 confirms is so unlikely that it doesn't matter.
No, it's not how it works.
If I send normal TX and the block with it gets orphaned, this TX will be automatically re-mined again.
But if block with coinbase TX is orphaned, this TX won't be re-mined automatically and I'll need to check it after 100 blocks and if it's lost then there is another 20 hours period to wait.


Quote
2. I'll repeat my question for the THIRD time: Why do you think that coinbase payments are better than sendmany ?
I thought I had already answered that :P
Edit: even when compared to a sendmany, a coinbase payment is smaller per payment.
No, it's not. Why do you think it is ?
Pages:
Jump to: