the github link just has two zip files, one with precompiled EXEs and one with a powershell script that downloads a zip file of other precompiled EXEs you know that looks shady right? (even if it's not) Where is your source code so people can audit it and build it themselves?
|
|
|
this all sounds great, but where are the actual "Dynex Neuromorphic Chips" ? Without those, this is worthless no?
|
|
|
Claymore 11.3 recently introduced a custom RX550 asm kernel now I see this: We also ordered an RX550 so there will be optimized kernels for it in the next release.
coincidence ?
|
|
|
lol guys, please dont turn this thread into an _SP thread. IF you want to discuss open license abuse...then you know where to go now. W0lf it sounds you are buying a boat. Over here it goes like this : The two happiest days of your life are : The day you buy your boat, and the day you sell your boat Working with someone who does, however... means I end up, a lot of times, on the "need to know" list. I swear every time I see an update from her she's in a different goddamned country. like weekly!
|
|
|
FYI - 2.7a still says debugger detected on my 1080Ti desktop PC I have Visual Studio 2017 installed, making SDL2 c++ apps - perhaps something there caused it ?
|
|
|
I'm getting "Debugger detected" on my gaming rig, which I do have Visual studio installed as I'm a hobbyist visual c++ programmer - could that be why ?
|
|
|
Looks like the hashrate has dropped significantly on what my miner is showing. Just the miner, not in the daemon though, that looks same. Why are the two different.
maybe background processes running are taking up cpu cycles? This coin sure seems relatively dead-ish...
|
|
|
Why are you people complaining to the nemosminer devs about miners crashing when all their script does is calculate which miner to run and run them for you? They don't make the miners, and they can't help your hardware crashing (unless they call the miner with a crazy intensity, which they don't) Either reduce clocks, try different drivers, or complain in the thread of that particular miner dev
|
|
|
A quick googling shows what calling int 21h will do when AX is set to 4C00 I'm guessing a group of MSU students who like assembly?
|
|
|
I am having issues with neoscrypt benchmarking. I have two 1080 ti rigs and on one it just says failed, while on another rig says running, but not opening ccminer (klaust) at all... edit: i have added "-i 15" to neoscrypt in klaust powershell file - still the same
remove the --api-remote from CcminerKlaust.ps1
|
|
|
since there's no source available, if someone wants to really trust it they'll have to monitor what registry/file locations it reads/writes to/from , and also wireshark it
However, if it truly does mine for OP 2% of the time, personally I'd be more inclined to trust that there's no malware in it (because he wouldn't want to lose his potential income stream) not going to try it myself, but only because I use Nemosminer-MPH when I want to hit MiningPoolHub
just saying
|
|
|
wallet? pools? why scrypt? that's asic territory
|
|
|
Hi,
I have coins there but didn't realize minimum payout was .01 - are you going to lower that or make it user-selectable ?
|
|
|
can you please post an example conf file that makes your wallet listen for mining rig getwork commands?
|
|
|
PcChip I'm sorry I didn't use the right terms in trying to explain how I got rid of it but it kept on beeping like the major error sound every half hour or so and that was irritating so I used my way and it worked for me. I respect your way is valid and you probably know alot more, however I'm just trying to save people with less knowledge the spare time and stress of a boogie program.
I believe you're addressing the wrong person
|
|
|
1. Not my choice of the shitty installer. One of our devs said that it was the best open source installer they could find. This problem is being fixed. 2. Some users (not all) are experiencing errors and even malware warnings on windows 10. We believe this to be for the "shitty installer". Which - will be fixed. 3. If the installer didn't create one, you need to manually create a blank file called tcash.conf in the C:\users\%USER%\appdata\tcash\ folder and re-run TorCash. This is also a problem we will fix with the installer in the next release. 4. It was tested and I personally could build perfectly. It won't compile on some machines due to machine-specific code in the GitHub repo. This was a careless mistake we are handling now. 5. Instructions on how to solo-mine are pretty much the same as you would find for any other coin. Just make sure the .conf file is in the right place and turn gen on. Here's for reference: https://coindesk.com/information/how-bitcoin-mining-works/ and https://cryptocurrencytalk.com/topic/9505-how-to-solo-mine/Full instructions will be provided in the wiki that is on it's way. 1. Thanks for your answers, personally I believe you when you say there's no malware in it (but still run it in a VM anyway) 2. did you seriously just link me to "how bitcoin mining works" ? 3. I don't want to set generate = 1, I don't want the wallet mining. I want to point my racks of cards to the wallet rpc port and have them mine for the wallet. Are you saying only wallet mining is working, and calling that "solo mining" ? this is my tcash.conf: rpclisten=1 server=1 rpcallowip=192.168.1.* rpcuser=pcchip rpcpass=x rpcport=12011 daemon=1 listen=1
|
|
|
I'll forgive that, because i don't really care; it was just a dig at you because this is frustrating
what I really care about are the answers to post number 170
I have linux vm's, windows vm's, racks of nvidia GPU's, racks of AMD GPU's and I still can't mine your coin. Why?
|
|
|
your "coded from the ground up"
|
|
|
I wouldn't say it's the *worst* launch ever, but it's pretty close - windows wallet is built with a shitty installer (why??) - windows 10 won't run it without throwing maware warnings (why wasn't this tested before release?) - windows appdata torcash folder doesn't have a .config to modify (should i just guess which of the several folders it goes in?) - linux github source won't build properly (why wasn't this tested before release?)
I'm genuinely curious how anyone is actually solo-mining it right now
how could you not test anything before releasing it?
|
|
|
|