|
fernando
|
 |
September 22, 2014, 03:25:15 PM |
|
WOW !! Spork is soooo cooool !!
No more hard-fork nightmares!
Yeah, it is cool... but the adrenaline rush of hard forks was kinda nice also  |
|
|
|
|
|
|
|
|
|
|
|
If you want to be a moderator, report many posts with accuracy. You will be noticed.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
Cryptosis
|
|
September 22, 2014, 03:29:42 PM |
|
i told my jalapeno and some errupters to mine to xpool just to see what is going on... around 10.42 GH
0.05347951 DRK this shift
my shares 517168
Mon Sep 22 2014 07:00:00 175222208 575361656 30.4543 % 2.90 TH 0.00001652 18.11938962 DRK Complete I've been a bit wary of the percentages and the payouts announced in total... They never add up. There have been times when I held over 50% of the pool's hashrate, and got less than 30% of the payout that crackfoo announced in this thread. Still pays more than mining BTC... But there's something wrong. Going by the hashrate is not going to add up usually. This is especially true when A) coins found near the end of the shift and more so if they take a really long time to confirm and B) you pool hop. So, SHA for example. The most profitable coins take 4-5 hours to confirm. Sometimes longer. So if the pool was mining those coins say, for the last 5-6 hours at the end of a shift, only a few of them would get calculated in that shift, but may not actually pay you until the next shift. Since the exchange then also takes several hours to confirm. So there could potentially be ~4 hours of you mining not calculated into the shift, making your hashrate appear lower. But you'll see the effects of that if you stopped mining completely at the end of a shift. You'll most likely get payments for the next couple shifts even though you're not mining. Take scrypt as another example. On my other pool since it has a lot more scrypt power, I added BTM. This had a pretty bad effect in the beginning because each block takes 24+ hours to confirm. So it appeared your speeds were slow and the profitability was low. However ~2 days later, profitability jumps and has been consistently higher than before now that the blocks are consistently rolling in. But this works since the speeds are consistent. The pool is designed to favour loyal miners and discourage pool hoppers. So if you hop on and mine for 3 hours, when the pool is mining a less valuable coin, because the diff was too high & speeds were too low for the $$ ones , then you may not get as much as you thought. I'll keep this in mind. I mine on xpool 24/7/365 with half of my hashpower. Disparity seems greater than what this would explain, but I could be wrong as I have not examined it deeper, just noticed it wasn't adding up. Ive been mining on xpool.ca now for a week and i really like the idea and getting paid in drk, and also the process is a lot different than just straight mining drk so there's way more variables that go into what you receive via payout. It all seems to be on the up and up for me, I'm making way more than i was mining btc, and its 0% fee? I mean that's crazy because there's a lot of work involved by crackfoo and we seem to receive the benefit of his hard work which i am grateful that he has taken the time to setup such a pool. |
|
|
|
|
crackfoo
Legendary
 Offline
Activity: 3458
Merit: 1126
|
|
September 22, 2014, 03:29:58 PM |
|
crackfoo I`ve mined on your pool since 18th september and didn`t jumped off it. Thats why I`m a bit pissed  EDIT: RC5 works fine, looks like perfect release! Now Open source comming be prepared Also, don't forget that you were not using the proper worker name. You were adding additional characters <DRK ADDY>+0.04 etc.... This is NOT supported and will affect reporting. While, my pool will TRY and trim that and pay the address if it turns out to be valid, it can can only record one instance of DRK address in the reporting. So it's possible some times shares get vaporized AFTER payment. Your wallet should get separate payments though. If someone really screws up their worker name and is not even close to a valid DRK address... they've just donated their shares to the next shift. |
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
stonehedge
Legendary
Offline
Activity: 1652
Merit: 1002
Decentralize Everything
|
|
September 22, 2014, 03:33:41 PM |
|
This release is perfect! Or at least it is from where I am standing. I think I might exhale now.
|
|
|
|
|
|
innergy
|
|
September 22, 2014, 03:35:55 PM |
|
I'll keep this in mind. I mine on xpool 24/7/365 with half of my hashpower. Disparity seems greater than what this would explain, but I could be wrong as I have not examined it deeper, just noticed it wasn't adding up.
The pool has been ~11Th/s the past couple shifts so you should be getting 30% +- 3-5% each SHA shift I would expect. Maybe SHA, scrypt and X11 have different profit for the pool.. |
|
|
|
|
|
eahmadov
|
|
September 22, 2014, 03:38:57 PM |
|
This release is perfect! Or at least it is from where I am standing. I think I might exhale now.
You know what they say "third time's a charm" |
|
|
|
|
crackfoo
Legendary
Offline
Activity: 3458
Merit: 1126
|
|
September 22, 2014, 03:42:00 PM |
|
I'll keep this in mind. I mine on xpool 24/7/365 with half of my hashpower. Disparity seems greater than what this would explain, but I could be wrong as I have not examined it deeper, just noticed it wasn't adding up.
The pool has been ~11Th/s the past couple shifts so you should be getting 30% +- 3-5% each SHA shift I would expect. Maybe SHA, scrypt and X11 have different profit for the pool.. Yes, they're all separate. |
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
crackfoo
Legendary
Offline
Activity: 3458
Merit: 1126
|
|
September 22, 2014, 03:49:46 PM |
|
Ive been mining on xpool.ca now for a week and i really like the idea and getting paid in drk, and also the process is a lot different than just straight mining drk so there's way more variables that go into what you receive via payout. It all seems to be on the up and up for me, I'm making way more than i was mining btc, and its 0% fee? I mean that's crazy because there's a lot of work involved by crackfoo and we seem to receive the benefit of his hard work which i am grateful that he has taken the time to setup such a pool.
Thanks! Good to see it's really benefiting miners, and most importantly making it simple to get their DRK. I'm actually going to move into a fee of 1.5%. I was hoping to get more complicated algorithms in place as well as some unique functionality but the lead node.js guy has been out for a couple months now dealing with a divorce. It will improve with time but since it's been running since June 27th with next to nill downtime and very few issues and many hours work, I need to start collecting my own DRK since no donations come in. ^_^ Cheers! |
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
GhostPlayer
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
September 22, 2014, 03:55:32 PM |
|
Update seems trickier than usual if you're before v.10.12.32
Check my link if you're having troubles!
|
|
|
|
|
oblox
Legendary
Offline
Activity: 1442
Merit: 1018
|
|
September 22, 2014, 04:03:48 PM |
|
Update seems trickier than usual if you're before v.10.12.32
Check my link if you're having troubles!
Why? It sounded like it's stopping the masternode, updating daemon on masternode, updating local wallet and starting the masternode on local again. The config file for the cold-remote disables darksend so the different keypool size won't affect older wallets. |
|
|
|
|
splawik21
Legendary
Offline
Activity: 1372
Merit: 1005
DASH is the future of crypto payments!
|
|
September 22, 2014, 04:25:02 PM |
|
crackfoo I`ve mined on your pool since 18th september and didn`t jumped off it. Thats why I`m a bit pissed EDIT: RC5 works fine, looks like perfect release! Now Open source comming be prepared Also, don't forget that you were not using the proper worker name. You were adding additional characters <DRK ADDY>+0.04 etc.... This is NOT supported and will affect reporting. While, my pool will TRY and trim that and pay the address if it turns out to be valid, it can can only record one instance of DRK address in the reporting. So it's possible some times shares get vaporized AFTER payment. Your wallet should get separate payments though. If someone really screws up their worker name and is not even close to a valid DRK address... they've just donated their shares to the next shift. check this PM between us. Since than I changed it and mined. Got a shift payment on 19.10.2014 Fri Sep 19 2014 07:00:00 2730200 157131860 1.7375 % 6.79 MH 0.00024948 0.36759187 DRK Complete and was mining without adding nothing to addres as you said before. so when I saw yesterday more tahtn 8000000 confirmed shares I was calm, but this Mon Sep 22 2014 07:00:00 9600 304751610 0.0032 % 16.57 KH 0.00017977 0.00108049 DRK Complete just took my balls off. I`ll still mine at xpool but I`m not so happy anymore, I should receive ~1coin but it does not metter 1 or 10, what metters that I feel that I didn`t do nothing wrong, thats all... |
BE SMART, USE DASH ( ͡° ͜ʖ ͡°) |
|
|
|
innergy
|
|
September 22, 2014, 04:26:53 PM |
|
Everything looks fine.. let's anonymize some cash.. |
|
|
|
|
|
|
TaoOfSaatoshi
Legendary
Offline
Activity: 2156
Merit: 1014
Dash Nation Founder | CATV Host
|
|
September 22, 2014, 04:31:54 PM |
|
Damn me working nights and needing sleep! I was hoping the release wouldn't be until this afternoon, but I dragged my ass out of bed and updated all my masternodes! To the future, RC5 brothers! Don't forget to take to Twitter and tell the world the good news! And now, back to bed....  |
|
|
|
GhostPlayer
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
September 22, 2014, 04:33:37 PM |
|
Update seems trickier than usual if you're before v.10.12.32
Check my link if you're having troubles!
Why? It sounded like it's stopping the masternode, updating daemon on masternode, updating local wallet and starting the masternode on local again. The config file for the cold-remote disables darksend so the different keypool size won't affect older wallets. Unless you use the local wallet to manage multiple wallets. In that case, either a) update all MN wallets to >.32 or RC5 wallet with 1k keypool... so you can use v.9 in the future as normal, to manage funds, without corruption. b) just update server side, and be very carefully in the future when you want to cash-out. If you accidentally use a <v.31 wallet on a >.32 QT it could end up corrupted (obviously, being the careful people we are, this is not a problem BECAUSE WE HAVE MULTIPLE backups to play with) so I think it is REALLY best to regenerate everything, especially now with the long release of RC5 for masternodes. - v.10.12.32, at least, generated wallet - encrypt - test encryption - regenerate external IP - regenerate 1k address - regenerate masternode pubkey - activate node. This is the only guarantee of a long running, hazardless Masternode, if you plan to cash out, lets say, monthly, you mind end up firing up a <.32 wallet and corrupting your wallet. No bid deal here... just create a blank RC5 wallet and send funds to it. |
|
|
|
|
pbleak
Legendary
Offline
Activity: 924
Merit: 1001
|
|
September 22, 2014, 04:43:13 PM |
|
All good for me. Thanks Evan |
|
|
|
|
oblox
Legendary
Offline
Activity: 1442
Merit: 1018
|
|
September 22, 2014, 04:45:42 PM |
|
Update seems trickier than usual if you're before v.10.12.32
Check my link if you're having troubles!
Why? It sounded like it's stopping the masternode, updating daemon on masternode, updating local wallet and starting the masternode on local again. The config file for the cold-remote disables darksend so the different keypool size won't affect older wallets. Unless you use the local wallet to manage multiple wallets. In that case, either a) update all MN wallets to >.32 or RC5 wallet with 1k keypool... so you can use v.9 in the future as normal, to manage funds, without corruption. b) just update server side, and be very carefully in the future when you want to cash-out. If you accidentally use a <v.31 wallet on a >.32 QT it could end up corrupted (obviously, being the careful people we are, this is not a problem BECAUSE WE HAVE MULTIPLE backups to play with) so I think it is REALLY best to regenerate everything, especially now with the long release of RC5 for masternodes. - v.10.12.32, at least, generated wallet - encrypt - test encryption - regenerate external IP - regenerate 1k address - regenerate masternode pubkey - activate node. This is the only guarantee of a long running, hazardless Masternode, if you plan to cash out, lets say, monthly, you mind end up firing up a <.32 wallet and corrupting your wallet. No bid deal here... just create a blank RC5 wallet and send funds to it. I use a local wallet with datadir shortcut to pull the appropriate config file for the masternode after renaming the matching wallet.dat file. So I should just have to stop the masternode, update masternode daemons remotely, update the local client to RC5, use the shortcuts for each node after putting in the appropriate wallet file, masternode start and done. If I am cashing out, I would be sending to an RC5 generated wallet. Granted, I haven't updated yet (still at work) but this is the process I am going to follow after work as to not have to regen everything. The config file with masternode=1 prevents darksend from being enabled so there should be no difference in terms of keypool sizing. |
|
|
|
|
pbleak
Legendary
Offline
Activity: 924
Merit: 1001
|
|
September 22, 2014, 04:54:28 PM |
|
Price is muted. Tech works. Not sure what to think. People are unaware?
|
|
|
|
|
|
camosoul
|
|
September 22, 2014, 04:56:30 PM |
|
Price is muted. Tech works. Not sure what to think. People are unaware?
Traders are always unaware. All they pay attention to are candlesticks. Unless it pumps for no reason at all, they'll never know anything is happening. |
.
.OROCOIN.
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ | |
█
█
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ | |
█
█
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ | |
█
█
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ █ █
█ |
|
|
|
stonehedge
Legendary
Offline
Activity: 1652
Merit: 1002
Decentralize Everything
|
|
September 22, 2014, 04:57:48 PM |
|
Price is muted. Tech works. Not sure what to think. People are unaware?
1) Not enough time to convince the observers that everything is fine yet. 2) Relatively few people are on RC5...only 140 masternodes so far. Maybe waiting until more have updated and reported back 3) Nervous because of previous update problems 4) People may be unaware as you say Personally, I'd be happy with a nice steady creep up to 0.008 and a fast takeup rate by the community. The sooner people update, the sooner we can enforce. |
|
|
|
|
|
