Bitcoin Forum
December 03, 2016, 01:56:10 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 »
  Print  
Author Topic: [0 GH/s 0% fee SMPPS] ArsBitcoin mining pool!  (Read 117377 times)
FreeJAC
Member
**
Offline Offline

Activity: 112


View Profile
July 15, 2011, 03:57:12 PM
 #241

PPS rocks! Now i just need more shares!  Wink

Donate here.... 18NiDLDA3qRxkEPN36xrzsdSgvEkbDKgNr
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480773370
Hero Member
*
Offline Offline

Posts: 1480773370

View Profile Personal Message (Offline)

Ignore
1480773370
Reply with quote  #2

1480773370
Report to moderator
1480773370
Hero Member
*
Offline Offline

Posts: 1480773370

View Profile Personal Message (Offline)

Ignore
1480773370
Reply with quote  #2

1480773370
Report to moderator
1480773370
Hero Member
*
Offline Offline

Posts: 1480773370

View Profile Personal Message (Offline)

Ignore
1480773370
Reply with quote  #2

1480773370
Report to moderator
Artefact2
Full Member
***
Offline Offline

Activity: 124


View Profile WWW
July 17, 2011, 10:11:26 PM
 #242

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)
coblee
Donator
Legendary
*
Offline Offline

Activity: 1078


firstbits.com/1ce5j


View Profile WWW
July 17, 2011, 10:16:32 PM
 #243

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 Offline

Activity: 70


View Profile
July 17, 2011, 11:58:30 PM
 #244

Is the server at max load? I am showing some connection issues every so often.
Just curious...

Sukrim
Legendary
*
Offline Offline

Activity: 1848


View Profile
July 18, 2011, 01:25:47 AM
 #245

From the decimals displayed it seems you are using FLOATS to store Bitcoin values! Angry

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.

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
coblee
Donator
Legendary
*
Offline Offline

Activity: 1078


firstbits.com/1ce5j


View Profile WWW
July 18, 2011, 01:30:15 AM
 #246

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
Sr. Member
****
Offline Offline

Activity: 434



View Profile
July 18, 2011, 03:16:25 AM
 #247

From the decimals displayed it seems you are using FLOATS to store Bitcoin values! Angry

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.

▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
▓▓ ONEDICE.ME ▓▓▓▓▓ BEST DICE EXPERIENCE ▓▓▓▓ PLAY OR INVEST ▓▓▓▓▓▓
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
NetTecture
Full Member
***
Offline Offline

Activity: 140


View Profile
July 18, 2011, 04:22:08 AM
 #248

Well, double Wink 15 digits Wink Or simply a very large decimal with at least 4 digits more than bitcoin can be splitted (12). Wink
digger
Sr. Member
****
Offline Offline

Activity: 322


View Profile WWW
July 18, 2011, 08:38:31 AM
 #249

you pool been included "who found the bitcoin blocks"

http://digbtc.com

doge pool: http://dog.ltcoin.net ,yac pool: http://yac.ltcoin.net ,bbq pool: http://bbq.ltcoin.net ,Litecoin pool, http://ltcoin.net dig feathercoin , http://fc.ltcoin.net bitbar pool: http://btb.ltcoin.net wdc pool: http://wdc.ltcoin.net
BurningToad
Full Member
***
Offline Offline

Activity: 207


View Profile
July 18, 2011, 02:21:07 PM
 #250

Hello,  I'm back from being out of town and will be catching up with emails/forum/etc as I can.

simplecoin
Sr. Member
****
Offline Offline

Activity: 406



View Profile WWW
July 18, 2011, 03:14:07 PM
 #251

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
Full Member
***
Offline Offline

Activity: 207


View Profile
July 18, 2011, 04:03:18 PM
 #252

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
Full Member
***
Offline Offline

Activity: 207


View Profile
July 18, 2011, 04:06:12 PM
 #253

From the decimals displayed it seems you are using FLOATS to store Bitcoin values! Angry

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 Offline

Activity: 1848


View Profile
July 18, 2011, 04:28:52 PM
 #254

From the decimals displayed it seems you are using FLOATS to store Bitcoin values! Angry

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!

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
BurningToad
Full Member
***
Offline Offline

Activity: 207


View Profile
July 18, 2011, 04:45:08 PM
 #255


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 Offline

Activity: 82


View Profile
July 18, 2011, 04:55:22 PM
 #256

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 Offline

Activity: 1848


View Profile
July 18, 2011, 04:58:04 PM
 #257

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.

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
theowalpott
Member
**
Offline Offline

Activity: 82


View Profile
July 18, 2011, 05:07:37 PM
 #258

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 Offline

Activity: 1078


firstbits.com/1ce5j


View Profile WWW
July 18, 2011, 05:11:55 PM
 #259

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
Full Member
***
Offline Offline

Activity: 207


View Profile
July 18, 2011, 05:40:17 PM
 #260

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.
 

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 [13] 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!