Show Posts
|
Pages: [1] 2 3 »
|
Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...
Full config with one 6950@6970 : x11 = 195w khc = 240w stop killing your gpus!!! running full voltage??? 280x x11 6.5mhs 144W khc 151khs 137W Neoscrypt 325khs 157W Lol. You have values with your hardware, i have values with mine. On MY config with 1 6950 with shaders unlocked, I have : x11 : @850/1300, ~1.9MHs, ~190w khc : @825/1200, ~110kHs, ~240w neoscrypt : @875/1300, ~6khs, ~165w Compare what it can be ! EDIT : on idle, full config is at ~90w ... You can likely lower the power usage and definitely the temps by underclocking the mem clock. With this algo it doesn't seem to need a high mem clock like scrypt. I have the mem clock set to under 400mhz on all of my rigs with no loss of kH.
|
|
|
I'm working on the sgminer fork A new algorithm of time what to do? Lol, it's going to take some time.
|
|
|
all the "cool" coins are now X something, xmr, xpy... so should we start calling this one xhc and xryptohash
This is not a scrypt or standardized x[y] scrypt coin. It is a new algo that can be modified to combat the idea of the asic, and with pid to control diff, it is in a class by itself, beyond that it complies with new standards. It does not need an 'X' to be 'cool', it has that all on it's own. This is why I decided to bring my GPUs out of retirement. It looks like someone has bought up quite a few sells on lazycoins.
|
|
|
Update. I'm compiling the new Wallet 0.3.3 but, this new version will require everybody to be running it when the blockchain hits the 5000 blocks
I've stopped generating TX every 10 seconds in order to give time for miners to upgrade the new Wallet.
ETA for the new Wallet v0.3.3 is 3 hours from now. Around 4:00AM GMT
Thanks for your patience.
Sounds good. The transaction fees seem quite high. Is there reasoning behind this? Also, every time I encrypt a wallet I need to use the --salvagewallet flag. The qt never seems to quit cleanly. This is the 3rd time it's happened.
|
|
|
I am getting about 3 blocks rejected for everyone that I find on my 280x. Anyone else having this issue?
I also can only get my 280X to mine. My 270X will not mine just HW errors and my other pc with Nvidia cards also nothing but HW.
I have the same problem. I have a rig with two 280x cards and one 7970 and only the 7970 does not have hardware errors. It's also the card that my monitor is plugged into.
|
|
|
Yeah, everything was in the correct place. I did a clean install and now everything appears to be functioning properly. Very strange.
|
|
|
I have been unable to mine, but it appears blocks are still being generated. I get stuck at either "Waiting for work from pool 0" or "Pool 0 127.0.0.1:32912 not responding!." I have tried inputting "getwork" into the debug cli and I get a reply that says "out of memory error 7." I've also tried redownloading the blockchain, and changing the username/password in the kryptohash.conf and nothing seems to help. Everything was working before the wallet update.
Occasionally I get "Pool 0 slow/down or URL or credentials invalid" when I frost execute my batch file, but not every time. I'm going to try a clean install of the wallet.
|
|
|
[2014-12-03 10:35:14] Started cgminer 3.7.5 [2014-12-03 10:35:14] Started cgminer 3.7.5 [2014-12-03 10:35:14] Probing for an alive pool [2014-12-03 10:35:19] Pool 0 slow/down or URL or credentials invalid
Kryptohash.conf server=1 rpcport=38912 rpcuser=z38630610.1 rpcpassword=x rpcconnect=127.0.0.1
solo.bat setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1 cgminer.exe --kryptohash -o 127.0.0.1:38912 -u z38630610.1 -p x --shaders 2816 --shaders-mul 8
system:windows7 64bit
dev,help
Change the title to kryptohash.conf. Lose the capital letter.
|
|
|
Attempting to solo mine with the miner provided, and the settings and conf settings, results in waiting for work from pool 0.
I have the same problem. Edit: It seems to be working but I'm getting 30Kh/s per 7950. Because the blockchain is new, I'm generating 1 transaction every 2 mins to generate work for miners. Unlike Bitcoin and other Alt Coins, the Kryptohash wallet isn't going to send miners "dummy" work when the mempool is empty. This is why you see cgminer waiting for work from pool 0. Once there is enough transactions or difficulty reaches the 3 minutes target, I would expect the miners to always have work. About the 7950. That one should be giving you more than 100Kh/s. What parameters are you using for the cgminer? On my 7950 I have --shaders 256 --shaders-mul 8. Inputting 2048 for shaders gives me 0kh/s. I'm averaging 15Kh/s right now. I've tried fooling with the intensity, worksize, and number of threads, but I appear to be making it worse. use --shaders 1792 --shaders_mul 8 Don't use intensity, threads, etc. Those parameters aren't going to work with KHC Also, I'm increasing the transactions per minute to generate more work for miners. Great. Now I'm up to a 120Kh/s average. I hit a block but a minute later the kryptohash client crashed.
|
|
|
Attempting to solo mine with the miner provided, and the settings and conf settings, results in waiting for work from pool 0.
I have the same problem. Edit: It seems to be working but I'm getting 30Kh/s per 7950. Because the blockchain is new, I'm generating 1 transaction every 2 mins to generate work for miners. Unlike Bitcoin and other Alt Coins, the Kryptohash wallet isn't going to send miners "dummy" work when the mempool is empty. This is why you see cgminer waiting for work from pool 0. Once there is enough transactions or difficulty reaches the 3 minutes target, I would expect the miners to always have work. About the 7950. That one should be giving you more than 100Kh/s. What parameters are you using for the cgminer? On my 7950 I have --shaders 256 --shaders-mul 8. Inputting 2048 for shaders gives me 0kh/s. I'm averaging 15Kh/s right now. I've tried fooling with the intensity, worksize, and number of threads, but I appear to be making it worse.
|
|
|
Attempting to solo mine with the miner provided, and the settings and conf settings, results in waiting for work from pool 0.
I have the same problem. Edit: It seems to be working but I'm getting 30Kh/s per 7950.
|
|
|
guys are you kidding?? cloakpal is just a simple website without functionality!!!
It definitely works, but you must be in a country that is supported to use the SMS service. You also need to sign up.
|
|
|
You should change it to a Nexus 5.
|
|
|
Drkman is a dolt. There is no reason to respond to this guy. In the year and a half I've been involved with crypto, I have never seen this much bullshit. Anyway, I'm still holding and cannot wait to see the future of Cloak. The devs are rock solid.
|
|
|
2014-07-11 15:11:39 <MrRGnome> so alty, since you're encouraging them you must have mined a good amount of cloak to make it worth the incentives 2014-07-11 15:12:01 <@alty> of course, I got over 200K 2014-07-11 15:12:15 <@alty> not from mining
Your dumb ass point being? btw I truly don't give 2 fucks how much he has. If he has 200k. good for him. He's a lot smarter than you or I. Actually the quote was he got it from mining. I thought it was worth asking and alty was completely upfront. Nice that you edited it. The quote is that he did NOT get it from mining. I don't see why any of this matters.
|
|
|
This is the most suspicious and weird coin I've ever been in. I don't know what's going on, everything is confusing, people are being hacked, exchanges are being hacked. Lets hope everything checks out and the price hits above DRK's highs.
Right, because the coin has nothing to do with what you've just mentioned. Vericoin was attacked on MintPal, it has nothing to do with cloak, and there have been a few isolated incidents with malware and stolen coins.
|
|
|
New wallet not open in mac os 10.9.4, how to fix it?
Download it in Chrome. I think there is something wrong with Safari and Mega.
|
|
|
I tried downloading the client with a different browser and now everything is working fine. Must have been corrupted.
|
|
|
The latest OSX wallet doesn't open for me.
I receive this error message: "LSOpenURLsWithRole() failed with error -10810"
|
|
|
|