Author

Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 298. (Read 837101 times)

sr. member
Activity: 308
Merit: 250
i dont want any rage or something, i just noticed all his messages after each other, on most forums you are warned to use the edit button....
legendary
Activity: 1610
Merit: 1000
-----------------------------
There will be an API for this sort of thing. It's not on the top of my priority list, but fairly high.

---------------------------------------------------

Super. Nothing fancy just a number:) The graphing will be made by us. Later on for those who are not able to graph the stats themselves if you have time, enough CPU on the server you can do it...
10X
legendary
Activity: 1022
Merit: 1000
BitMinter
Looks like he's using GPUMAX. It's a service where you can buy shares (hashrate).
sr. member
Activity: 295
Merit: 250
WOW! pool over 1,1 TH/s

Who is this ACEOFSPDS2005. He's mining between 188-256 GH/s from what I've seen. That single user has been the singular difference.
legendary
Activity: 1753
Merit: 1007
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
The question is if there is a way to get MH/s with JSON per user ID?

There will be an API for this sort of thing. It's not on the top of my priority list, but fairly high.

I agree that the additional statistics on a graph need
I would like to know my average speed over the day too.

Some more stats also coming up, but probably after the API.

I noticed on the beta miner that I can turn on a re-scan interval for added/removed FPGAs.  Is that safe to use now?

It should be ok, although it has not been extensively tested.

This was disabled because a bug in rxtx and nrjavaserial (the 2 serial comm libraries I used first) would cause it to leak file handles. Eventually the miner process had too many file handles and would crash. The beta is instead using purejavacomm, which seems like a stable library.
legendary
Activity: 1753
Merit: 1007
JSON API question

Guy's
I have to admit that pool is great!
I have a simple question. I would like to make a graph of my MH/s from the pool stand point of view

Something like:
https://bitminter.com/api/pool/top50

I was planning to explore that, but unfortunately i am not in the top 50:( If i was i should get info from there without a problems
I have read about all available api's but i could not find such stats per user.

The other option is to "hack" somehow my OWN account - what i mean is to write php script which shall authorize and parse the info from workers page:
https://bitminter.com/members/workers

Unfortunately it is to hard to implement with my knowledge of php.

The question is if there is a way to get MH/s with JSON per user ID?

Thanks in advance!


I agree that the additional statistics on a graph need
I would like to know my average speed over the day too.
sr. member
Activity: 348
Merit: 250
Hi Doc,

I noticed on the beta miner that I can turn on a re-scan interval for added/removed FPGAs.  Is that safe to use now?

Thanks!
legendary
Activity: 1610
Merit: 1000
JSON API question

Guy's
I have to admit that pool is great!
I have a simple question. I would like to make a graph of my MH/s from the pool stand point of view

Something like:
https://bitminter.com/api/pool/top50

I was planning to explore that, but unfortunately i am not in the top 50:( If i was i should get info from there without a problems
I have read about all available api's but i could not find such stats per user.

The other option is to "hack" somehow my OWN account - what i mean is to write php script which shall authorize and parse the info from workers page:
https://bitminter.com/members/workers

Unfortunately it is to hard to implement with my knowledge of php.

The question is if there is a way to get MH/s with JSON per user ID?

Thanks in advance!
legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
A very clear majority wants the change for the PPLNS reward system from N = 1x Difficulty to N = 2x Difficulty.

This change will be made monday the 27th of august, one week from when this is written. It will be done by changing the size of a shift from 0.1x Difficulty to 0.2x difficulty. Still it will be the last 10 shifts that get paid when a block is found.

What does this mean for you as a miner:
  • Variance is reduced. Pay from a block will be spread out over more work, so the highs and lows that a proof of work might get paid will be more evened out. This gives you more stable pay, especially if you don't mine 24/7.
  • Payout time is increased. Since you can get paid for blocks found over a longer period of time, this also means it takes longer from work is done until it is fully paid. Currently it takes about 3.5 hours for work to be fully paid, after the change it would take 7 hours assuming the same hashrate.

Why give 1 week advance notice before such a small change? I don't expect anyone will care greatly about this, but I think it is a good principle to always announce changes to the reward system ahead of time.
sr. member
Activity: 348
Merit: 250
one question: if CDF reaches 100%, we will solve the block?

"There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment. Believing otherwise is what's known as the Gambler's fallacy [1].

It's like trying to flip 53 coins at once and have them all come up heads. Each time you try, your chances of success are the same." from https://en.bitcoin.it/wiki/Blocks

Then CDF looks useless for predicting the end of a block

Nothing is useful for predicting the end of a block. Sorry.
To put it another way, if the block we're working on right now shows a CDF of 75%, it simply means that, on average, we should generate a block prior to this point 75% of the time.
legendary
Activity: 1753
Merit: 1007
OOO! under development!??. Give me link to read more about ;-)
Thanks for info about "hopper". Now i know)
hero member
Activity: 518
Merit: 500
Then I dont understand the algorithm for "pool hoping." These programs are somehow determine which block short and which a long

No, they dont. Pool hoppers determine how long a round has been active, ie, how many shares were found since it started. So  they "predict" the past, not the future. The algorithm to predict the future is still under development Wink.
legendary
Activity: 1753
Merit: 1007
one question: if CDF reaches 100%, we will solve the block?


"There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment. Believing otherwise is what's known as the Gambler's fallacy [1].

It's like trying to flip 53 coins at once and have them all come up heads. Each time you try, your chances of success are the same." from https://en.bitcoin.it/wiki/Blocks

Then CDF looks useless for predicting the end of a block

Nothing is useful for predicting the end of a block. Sorry.
Then I dont understand the algorithm for "pool hoping." These programs are somehow determine which block short and which a long
donator
Activity: 2058
Merit: 1007
Poor impulse control.
one question: if CDF reaches 100%, we will solve the block?

"There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment. Believing otherwise is what's known as the Gambler's fallacy [1].

It's like trying to flip 53 coins at once and have them all come up heads. Each time you try, your chances of success are the same." from https://en.bitcoin.it/wiki/Blocks

Then CDF looks useless for predicting the end of a block

Nothing is useful for predicting the end of a block. Sorry.
legendary
Activity: 1753
Merit: 1007
one question: if CDF reaches 100%, we will solve the block?

"There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment. Believing otherwise is what's known as the Gambler's fallacy [1].

It's like trying to flip 53 coins at once and have them all come up heads. Each time you try, your chances of success are the same." from https://en.bitcoin.it/wiki/Blocks

Then CDF looks useless for predicting the end of a block
donator
Activity: 2058
Merit: 1007
Poor impulse control.
I wasn't sure which types of infinity this type of problem would generate, but if you want to read up on Cantor and post the solution here I'd appreciate it. It's past bedtime for me.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
Well Aleph-1 is > ∞
So it's not all that preposterous Cheesy
donator
Activity: 2058
Merit: 1007
Poor impulse control.
CDF = 1 - (1 - 1/D)^n where D = current difficulty and n = number of shares submitted.

The CDF will reach 1 (or 100%) when (1 - 1/D)^n = 0. This will occur when n is an infinite number. For larger D, it will occur at a larger infinite number Smiley
newbie
Activity: 55
Merit: 0
one question: if CDF reaches 100%, we will solve the block?

"There's no such thing as being 1% towards solving a block. You don't make progress towards solving it. After working on it for 24 hours, your chances of solving it are equal to what your chances were at the start or at any moment. Believing otherwise is what's known as the Gambler's fallacy [1].

It's like trying to flip 53 coins at once and have them all come up heads. Each time you try, your chances of success are the same." from https://en.bitcoin.it/wiki/Blocks
Jump to: