|
Artefact2
|
 |
July 17, 2011, 10:11:26 PM |
|
Hello there,
I think there is a problem with your statistics page. Some of the blocks you claim you found were definitely not found by you.
For example: your stats say you found block #136661, yet it was found by Eligius (just look at it, lots of generation addresses of miners mining on Eligius, also the coinbase says "Eligius").
I just want to report this issue, and if you eventually plan to fix it (it would be nice) ! Thanks.
(An easy fix would be to display the block hashes instead of trying to "guess" the block number, since the hash is always accurate.)
|
A pool-biased blockchain representation, by me: pident (WTFPL) |
|
|
|
|
|
|
|
|
|
|
|
If you see garbage posts (off-topic, trolling, spam, no point, etc.), use the "report to moderator" links. All reports are investigated, though you will rarely be contacted about your reports.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
coblee
Donator
Legendary
 Offline
Activity: 1653
Merit: 1286
Creator of Litecoin. Cryptocurrency enthusiast.
|
|
July 17, 2011, 10:16:32 PM |
|
Yeah, it's a known problem. I think it currently just checks every 5 minutes. If a block is found, it just assumes the latest found block is it. I think that's a bug with SimpleCoin, but not sure. I assume BurningToad is planning to fix it.
|
|
|
|
The_JMiner
Member
Offline
Activity: 70
Merit: 10
|
|
July 17, 2011, 11:58:30 PM |
|
Is the server at max load? I am showing some connection issues every so often.
Just curious...
|
|
|
|
Sukrim
Legendary
Offline
Activity: 2618
Merit: 1006
|
|
July 18, 2011, 01:25:47 AM
Last edit: July 18, 2011, 04:29:39 PM by Sukrim |
|
From the decimals displayed it seems you are using FLOATS to store Bitcoin values!  I'm off here until this is either explained or fixed. (Never. Ever. Use. Floats!) Edit: The decimals I am displaying on the site have nothing to do with how they are stored on the back end. The site has things rounded to 8 decimal points for most things, 12 for the PPS share count, but underneath it is not rounded, and is stored as doubles.
|
|
|
|
coblee
Donator
Legendary
Offline
Activity: 1653
Merit: 1286
Creator of Litecoin. Cryptocurrency enthusiast.
|
|
July 18, 2011, 01:30:15 AM |
|
He's using floats to try to be perfectly fair and everyone gets their exact share. It gets rounded when you withdraw and not just rounded down when you earn your share.
It's probably not worth it to be that precise since 1 satoshi is not worth much. But why are you so against it that you would quit mining here? Is using floats going to cheat you of something?
|
|
|
|
|
RandyFolds
|
|
July 18, 2011, 03:16:25 AM |
|
From the decimals displayed it seems you are using FLOATS to store Bitcoin values! I'm off here until this is either explained or fixed. (Never. Ever. Use. Floats!) What's wrong with them? I think the system is more fair than just truncating and keeping those fractions, however minute they may be. C'mon...we've all seen Office Space. If it's a security thing, please elaborate, as I am sure we are all interested. |
|
|
|
|
|
NetTecture
|
|
July 18, 2011, 04:22:08 AM |
|
Well, double  15 digits Or simply a very large decimal with at least 4 digits more than bitcoin can be splitted (12). |
|
|
|
|
|
|
|
BurningToad (OP)
|
|
July 18, 2011, 02:21:07 PM |
|
Hello, I'm back from being out of town and will be catching up with emails/forum/etc as I can.
|
|
|
|
|
simplecoin
|
|
July 18, 2011, 03:14:07 PM |
|
Yeah, it's a known problem. I think it currently just checks every 5 minutes. If a block is found, it just assumes the latest found block is it. I think that's a bug with SimpleCoin, but not sure. I assume BurningToad is planning to fix it.
It is an issue with the simplecoin framework, inherited from the mining pool framework. This is near the top of my issues log. Hopefully I will have a fix in place before long. |
Donations: 1VjGJHPtLodwCFBDWsHJMdEhqRcRKdBQk
|
|
|
|
BurningToad (OP)
|
|
July 18, 2011, 04:03:18 PM |
|
Is the server at max load? I am showing some connection issues every so often.
Just curious...
The issue is various stats calulations and database work that can cause intermittent connection issues (especially on block confirms.) I think I may need to remove some of the per-round stats (like shares per round) and put in shares per day instead. This would be a quick fix until I can use some more efficient methods. However, I think this would be good to do so we are losing as few shares as possible to connection issues. |
|
|
|
|
BurningToad (OP)
|
|
July 18, 2011, 04:06:12 PM |
|
From the decimals displayed it seems you are using FLOATS to store Bitcoin values! I'm off here until this is either explained or fixed. (Never. Ever. Use. Floats!) The decimals I am displaying on the site have nothing to do with how they are stored on the back end. The site has things rounded to 8 decimal points for most things, 12 for the PPS share count, but underneath it is not rounded, and is stored as doubles. Right now the pool actually overpays each time you get a payout as well, as it rounds your balance UP, for example, 1.021022222 will become 1.02102223 on payout, then your balance goes to zero. |
|
|
|
Sukrim
Legendary
Offline
Activity: 2618
Merit: 1006
|
|
July 18, 2011, 04:28:52 PM |
|
From the decimals displayed it seems you are using FLOATS to store Bitcoin values! I'm off here until this is either explained or fixed. (Never. Ever. Use. Floats!) The decimals I am displaying on the site have nothing to do with how they are stored on the back end. The site has things rounded to 8 decimal points for most things, 12 for the PPS share count, but underneath it is not rounded, and is stored as doubles. Sad to hear that, added to the post above as well! |
|
|
|
|
BurningToad (OP)
|
|
July 18, 2011, 04:45:08 PM |
|
Sad to hear that, added to the post above as well!
Sad to hear what? That I don't display a gajillion decimal points on the site? Or, doubles aren't precise enough for you either? |
|
|
|
theowalpott
Member
Offline
Activity: 80
Merit: 10
|
|
July 18, 2011, 04:55:22 PM |
|
I'm assuming he means "glad to hear that".
The other thing that you could do is store everything as integers (ie multiply 1 bitcoin by 1e8), and always keep the single share value as an integer value too. Still gonna lose 1 unit either way in the rounding for the per share value.. but maybe it'd keep Sukrim happy?
|
1FwGATm6eU5dSiTp2rpazV5u3qwbx1fuDn
|
|
|
Sukrim
Legendary
Offline
Activity: 2618
Merit: 1006
|
|
July 18, 2011, 04:58:04 PM |
|
Sorry, but storing monetary values in floats is just... something I really don't like. At all.
Having more than 8 decimals ready is nice, but using floats for that is just not the style of coding I support at all. Bitcoins are atomic units.
|
|
|
|
theowalpott
Member
Offline
Activity: 80
Merit: 10
|
|
July 18, 2011, 05:07:37 PM |
|
Then how do you deal with the fact that 1 share is unlikely to be an exact number of bitcoins, even if you use nano, or even pico-bitcoins?
At some point you must round up or down, and in that case someone loses and someone gains from it. Storing numbers to the limit of double precision and then round UP (as BT says), seems to be pretty fair to me. Especially as the limit of bitcoins is 8 decimals?
|
1FwGATm6eU5dSiTp2rpazV5u3qwbx1fuDn
|
|
|
coblee
Donator
Legendary
Offline
Activity: 1653
Merit: 1286
Creator of Litecoin. Cryptocurrency enthusiast.
|
|
July 18, 2011, 05:11:55 PM |
|
I will tell you why it makes sense to store it as a double. Currently, each PPS share is worth 0.000031989190 BTC. If you round that to a satoshi, then you only get 0.00003198 BTC. You lose .9190 satoshis for every share. If you look at ArsBitcoin's lifetime shares, you will see the number one person having 3,647,233 shares. If he lost .9190 satoshis for every share, he would have earned 0.03351797 BTC less. It's not much, but it's still something.
I personally think BurningToad should round down (not up!) and keep the change as fees. But I applaud him for trying to be as fair as possible.
|
|
|
|
|
BurningToad (OP)
|
|
July 18, 2011, 05:40:17 PM |
|
The issue is various stats calulations and database work that can cause intermittent connection issues (especially on block confirms.) I think I may need to remove some of the per-round stats (like shares per round) and put in shares per day instead. This would be a quick fix until I can use some more efficient methods. However, I think this would be good to do so we are losing as few shares as possible to connection issues.
I have made a change to stop the hash rate drop at 120 confirmations. This should mean that there are less connection issues and everyone should be able to get more shares in. The cost at the moment, is the per-round user share history at https://arsbitcoin.com/blocks.php. I will display some new stats soon for daily shares submitted and exact PPS number in a table. The PPS numbers are in that chart now, but I think a table would be nice too. The remaining sources of occasional connection issues are: 1) Sometimes the 5 min stats calcs can cause issues. This is usually when there hasn't been a new block on the bitcoin network in a while (30 min+) which is a trigger for some behind the scenes work. I can improve this in the future. 2) Database backups can still cause issues. Someone already provided me a solution for this, but I have not had time to implement yet. |
|
|
|
|
BurningToad (OP)
|
|
July 18, 2011, 05:44:34 PM |
|
I will tell you why it makes sense to store it as a double. Currently, each PPS share is worth 0.000031989190 BTC.
Actually, behind the scenes, each share is currently worth: 0.000031989190292329. Once again, the number is rounded for display on the site only. |
|
|
|
|
