 Show Posts
|
|
Pages: [1]
|
Apparently, I spoke too soon. After 122 hrs of mining, my average gross yield is 138 XVG-scrypt per day on mastermining. Better than the 121 I was getting on MPH, but still nowhere near the 220 predicted by your algo on WTM.
JC
Getting all shares rejected now on mastermining. Testing nlpool. I'm only seeing 3.3% rejection, but that's over time. It's possible that there have been periods of 100% rejection but I wasn't monitoring. |
|
|
|
After 9 hours on MasterMining, I'm on track to be at 206/day. Almost exactly as WhatToMine predicts. Thank you for helping me to find the problem!
Cheers, thats really strange though, never had this kind of problem on mph. Maybe drop the admin an email explaining the problem. Apparently, I spoke too soon. After 122 hrs of mining, my average gross yield is 138 XVG-scrypt per day on mastermining. Better than the 121 I was getting on MPH, but still nowhere near the 220 predicted by your algo on WTM. JC |
|
|
|
I'm going to switch over to that pool and see if I get better results. Will report back in a few days. After 9 hours on MasterMining, I'm on track to be at 206/day. Almost exactly as WhatToMine predicts. Thank you for helping me to find the problem! |
|
|
|
I'm going to switch over to that pool and see if I get better results. Will report back in a few days. |
|
|
|
@johncroc1
Multi-algo coins are tricky to estimate rewards for.
Its possible that pool had bad luck / orphans. In general sha and scrypt parts should be fine though.
I think there was a network issue on verge few days ago, any chance it got better recently?
Still waiting for my asic, can test the rewards after I have it.
WTM's rewards estimate is still running about double what the actual reward is (at least for me) re: XVG-Scrypt. I average 121 coins/day with a low of 108 and a high of 168. The vast majority of days are between 110 and 132. MiningPoolHub's calculated hashrate for me is consistent with my miner's nominal rate (695 mh/s). WTM's rewards estimate for my hashrate is 227. MiningPoolHub reports a network difficulty of ~78K and so does WTM, at the moment. Again, I'm not complaining; only trying to understand and perhaps supply you with information that might help you. I should add that I also mine ETH using GPU rigs and WTM's rewards estimate is very close (~+10%). I've had similar luck (estimate close to reality) with Musicoin. JC |
|
|
|
|
This is not a complaint...rather general curiosity and a desire to better understand:
I have an Innosilicon A4+and am mining Verge at MiningPoolHub. My nominal hashrate (from the miner's UI) is 695 MH/s. The pool indicates my calculated hashrate as variable between ~500-900 MH/s.
whattomine.com's calculation indicates I should be earning ~217 coins per day, but my actual earnings per day averages ~130 coins. Why is there a difference? Is the calculation based on something that's variable from pool to pool (indicating I should maybe change pools)? Is there something you are unaware of that should be changed in your calculation to better reflect potential earnings?
I LOVE whattomine.com and use it almost every day to help me make decisions about GPU purchases, coins to mine, etc. I just want to better understand how it calculates likely earnings, so I can use the information even more confidently than I do now.
JC
|
|
|
|
Once I download the Verge Debian Wallet and extract the contents, I get VERGEd and VERGE-qt. What now?
Are they the compiled executables for the daemon and the gui wallet? Do I just make them executable (chmod u+x)and run them?
yes those are compiled binaries. although if you're running debian you could just compile it yourself, its fairly quick and easy. I'm having trouble. I downloaded from GitHub and compiled my own binaries. I started the wallet and after ten seconds it went gray (as if it was busy doing something). I assumed that was the "wait until I am synched with the network" behavior. It has now been running for several days and is still gray. I don't see that it's making any connections. This machine has several wallets on it, and they all are connecting and syncing just fine. What do I need to do to get my Verge wallet working? Or at least what do I need to report here to get some help troubleshooting? JC what kind of ram/cpu do you have? do you have several wallets running at once? try downloading the chain from vergecurrency.de and putting it in the ~/.VERGE data directory also what version of debian? what version of boost, openssl, and bdb are you using? I7-7700K/16 GB (CPU load is ~5-8% on 7 cores, 40% on the eighth core, All of the RAM is used and about 8 GB of swap) Yes. Running 4 other wallets I will try downloading the block chain and putting it in the directory you suggest Ubuntu 16.04, I keep the OS and installed software very up-to-date (semi-weekly), but I will verify versions of boost, openssl, bdb. Since all of the ram is used, I think I will try starting ONLY the Verge wallet after downloading the block chain and report back the result. Thank you for your help and for giving me some things to check/try! [EDIT] Versions: Boost - 1_58 openssl - 1.0.2g I can't find a way to verify the version of dbd. Whatever comes with Ubuntu 16.04 LTS...I haven't changed it. I realized after all the install/delete cycles I've been through, I did not create a VERGE.conf after my last build. So I tried to run VERGEd to get the output to create one and discovered VERGEd does not provide any output (different behavior than I've had before)... Not sure what might be wrong there but found an old VERGE.conf in the trash and am going to try it. Since this is a new wallet setup I don't have anything to lose if it doesn't work, but am wondering if this is going to mess things up down the road when I'm actually trying to use the wallet to store coins, and also wondering why I do not get output from '''./VERGEd''' and if THAT could be a problem that needs to be fixed before I will be able to get this working. Thoughts? verged has no output unless you send it rpc calls. it does require a VERGE.conf in the datadirectory with at least rpcuser and rpcpassword configured. to make rpc calls, you'd do this: ./VERGEd getinfo (returns general network info) or ./VERGEd getbalance (returns balance of wallet) etc.. Of course. Sorry for the silly question. I should have read the doc more thoroughly. After putting an old VERGE.conf i found in the trash into the data directory, and starting the daemon I get but once it's started I can't talk to it. ~/verge/src/]VERGEd getinfo returns error: couldn't connect to server If I try to start VERGEd with getinfo I also get error: couldn't connect to server Still stumped. Not sure what to try next. I have to tell you, I've been a programmer for 35 years, in multiple languages (from FORTRAN and COBOL to Python). I've been running Debian Linux distros on my personal machines, exclusively, for over 5 years. I have a pretty complicated mining setup with ASICS for SCRYPT coins and GPUs for ASIC-proof algos. I'm not a NOOB, but this Verge wallet thing has me completely flummoxed. No problems setting up any other wallets. Don't get me wrong, I'm not blaming anyone. I'm just wondering what tiny little thing I've missed that keeps causing me all this trouble. |
|
|
|
Once I download the Verge Debian Wallet and extract the contents, I get VERGEd and VERGE-qt. What now?
Are they the compiled executables for the daemon and the gui wallet? Do I just make them executable (chmod u+x)and run them?
yes those are compiled binaries. although if you're running debian you could just compile it yourself, its fairly quick and easy. I'm having trouble. I downloaded from GitHub and compiled my own binaries. I started the wallet and after ten seconds it went gray (as if it was busy doing something). I assumed that was the "wait until I am synched with the network" behavior. It has now been running for several days and is still gray. I don't see that it's making any connections. This machine has several wallets on it, and they all are connecting and syncing just fine. What do I need to do to get my Verge wallet working? Or at least what do I need to report here to get some help troubleshooting? JC what kind of ram/cpu do you have? do you have several wallets running at once? try downloading the chain from vergecurrency.de and putting it in the ~/.VERGE data directory also what version of debian? what version of boost, openssl, and bdb are you using? I7-7700K/16 GB (CPU load is ~5-8% on 7 cores, 40% on the eighth core, All of the RAM is used and about 8 GB of swap) Yes. Running 4 other wallets I will try downloading the block chain and putting it in the directory you suggest Ubuntu 16.04, I keep the OS and installed software very up-to-date (semi-weekly), but I will verify versions of boost, openssl, bdb. Since all of the ram is used, I think I will try starting ONLY the Verge wallet after downloading the block chain and report back the result. Thank you for your help and for giving me some things to check/try! [EDIT] Versions: Boost - 1_58 openssl - 1.0.2g I can't find a way to verify the version of dbd. Whatever comes with Ubuntu 16.04 LTS...I haven't changed it. I realized after all the install/delete cycles I've been through, I did not create a VERGE.conf after my last build. So I tried to run VERGEd to get the output to create one and discovered VERGEd does not provide any output (different behavior than I've had before)... Not sure what might be wrong there but found an old VERGE.conf in the trash and am going to try it. Since this is a new wallet setup I don't have anything to lose if it doesn't work, but am wondering if this is going to mess things up down the road when I'm actually trying to use the wallet to store coins, and also wondering why I do not get output from '''./VERGEd''' and if THAT could be a problem that needs to be fixed before I will be able to get this working. Thoughts? |
|
|
|
Once I download the Verge Debian Wallet and extract the contents, I get VERGEd and VERGE-qt. What now?
Are they the compiled executables for the daemon and the gui wallet? Do I just make them executable (chmod u+x)and run them?
yes those are compiled binaries. although if you're running debian you could just compile it yourself, its fairly quick and easy. I'm having trouble. I downloaded from GitHub and compiled my own binaries. I started the wallet and after ten seconds it went gray (as if it was busy doing something). I assumed that was the "wait until I am synched with the network" behavior. It has now been running for several days and is still gray. I don't see that it's making any connections. This machine has several wallets on it, and they all are connecting and syncing just fine. What do I need to do to get my Verge wallet working? Or at least what do I need to report here to get some help troubleshooting? JC what kind of ram/cpu do you have? do you have several wallets running at once? try downloading the chain from vergecurrency.de and putting it in the ~/.VERGE data directory also what version of debian? what version of boost, openssl, and bdb are you using? I7-7700K/16 GB (CPU load is ~5-8% on 7 cores, 40% on the eighth core, All of the RAM is used and about 8 GB of swap) Yes. Running 4 other wallets I will try downloading the block chain and putting it in the directory you suggest Ubuntu 16.04, I keep the OS and installed software very up-to-date (semi-weekly), but I will verify versions of boost, openssl, bdb. Since all of the ram is used, I think I will try starting ONLY the Verge wallet after downloading the block chain and report back the result. Thank you for your help and for giving me some things to check/try! [EDIT] Versions: Boost - 1_58 openssl - 1.0.2g I can't find a way to verify the version of dbd. Whatever comes with Ubuntu 16.04 LTS...I haven't changed it. |
|
|
|
Once I download the Verge Debian Wallet and extract the contents, I get VERGEd and VERGE-qt. What now?
Are they the compiled executables for the daemon and the gui wallet? Do I just make them executable (chmod u+x)and run them?
yes those are compiled binaries. although if you're running debian you could just compile it yourself, its fairly quick and easy. I'm having trouble. I downloaded from GitHub and compiled my own binaries. I started the wallet and after ten seconds it went gray (as if it was busy doing something). I assumed that was the "wait until I am synched with the network" behavior. It has now been running for several days and is still gray. I don't see that it's making any connections. This machine has several wallets on it, and they all are connecting and syncing just fine. What do I need to do to get my Verge wallet working? Or at least what do I need to report here to get some help troubleshooting? JC |
|
|
|
|
Once I download the Verge Debian Wallet and extract the contents, I get VERGEd and VERGE-qt. What now?
Are they the compiled executables for the daemon and the gui wallet? Do I just make them executable (chmod u+x)and run them?
|
|
|
|
Please forgive me if I'm posting in the wrong way or in the wrong place. I will take whatever guidance is offered. I am trying to install the Verge wallet on Ubuntu 16.04. I'm downloading from and following the instructions at https://github.com/vergecurrency/VERGE. The install seems to go fine, but when I try to start the wallet it seems OK but after about 10 seconds it turns grey and stays in that state for as long as I leave it. Eventually I get an error along the lines of "Fill color must be set to 1 or 0." I won't have the exact wording for a few hours. When it comes up I'll edit this post. In the meantime, based on the information I've provided does anyone have any thoughts about what might be going wrong for me? JC Edit: I can't get the error message. Not sure why. I start the wallet, it goes grey and nothing happens. I've tried uninstalling and reinstalling several times, always the same result (as described above). |
|
|
|
|
