 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
Hello, A few months ago, when I wanted to profit on those Pump&Dump schemes without participating, I started working on an automated bot, which would trade based based on radical price changes. The actual bot never materialized, but I've ported the engine I've implemented to a web application with a nice graphical programming tool, and would love to get your feedback https://trader.semtexzv.com Can currently interact with Bitfinex & Binance. Currently, you can create automated strategies, backtest them, and I'm going to be releasing real-time trading soon. Anyways, I'd love to get your feedback on what's working, or not, what would you like implemented and any general thoughts. Thanks  |
|
|
|
Hello, I'm a software dev with a lot of free time, and have decided to revive my Master's thesis, and make some real piece of software out of it. I'd love to get your feedback on it. I've started implementing a trading platform/trading bot that attempts to be as accesible as possible. Whole thing is running in the cloud, is properly secured and only data I collect is email from your login, If you don't like the login process, please let me know. https://trader.semtexzv.comNote: This is an alpha level software, there are bugs and the thing might crash. |
|
|
|
Yeah, nicehash works again, but Prospector failed:
ERROR Could not connect to stratum+tcp://skunk.eu.nicehash:3362/ after 10 attempts, exiting
EU servers seem to be screwy, I could mine on USA servers just fine Hi all anyone Know configuratio to put to restart miner when its crash ?
My miner after one or 2 horas running crash and dont restart by itself
I started and its up there some conf calle reminer.exe -- somthing like that anyone could to help me pls?
thanks
Well I need to know more, what does the miner output when it crashes ? It should auto restart on recoverable errors. |
|
|
|
I have ran this miner for a month, mining sigt. I had fantastic result 135 Mh/s vs 111 with claymore. I didn't see anything fishy just great result and stable.
Shame that developer abandoned it Yep and i lost all my coins on the mining site too as it shut down.... oh well live and learn... make sure to move coins to my wallet asap ... i suppose Nicehash is back up, Miner should be working again. |
|
|
|
I have ran this miner for a month, mining sigt. I had fantastic result 135 Mh/s vs 111 with claymore. I didn't see anything fishy just great result and stable.
Shame that developer abandoned it Developer is finishing his higher education, and will come back once he has time |
|
|
|
wasted a lot of time.... installed clean win 7 in virtual machine installed .net 4 installed sandboxie installed avg (this time i used avg) added folder to exception list unpacked miner started in sandbox same result from sandboxie https://i.imgur.com/J2Vu8CE.pngwithout sandboxie https://i.imgur.com/UHHzVZx.pngupdate program ...... just copy itself О_О with that name to that appdata folder https://i.imgur.com/hoUmAt9.pngsame md5 anyway. name is way too suspicious and detection made me panic. This miner does not require Dotnet, if it does, it's not my miner. Anyways, I changed my github info, and uploaded a new version, in case my github was compromised. |
|
|
|
I tried this miner also but had some very strange behaviour and gave up.
what kind of behavior ? i'm just curious what i missed (?) with this "prospector" ? Look at my post in the prospector thread: https://bitcointalk.org/index.php?topic=2033185.msg22376578#msg22376578. Somehow after the first start the config.toml file was created and after that... nothing. Try running the miner from command line, and them posting it's output to the main thread, I need to know what the issue is, to get it fixed |
|
|
|
I don't know what you are running, But this miner definitely does not create any files named svchost.... This must be result of something other running on your computer. Also, the false positives are a result of Packer that I use to protect the source code. |
|
|
|
Hi dev! When do you release new version of prospector with support of more coin ? For information, Signatum mining has ending => no dev fee I have my hands full with Day job + uni. I guess I will have free time to spend on the miner during christmas  |
|
|
|
So I want to try this miner. First Google Chrome won't download it, because of potential danger. I ignored that. Then my Windows Defender goes crazy about this file. Ok, it could be a false positive, so I put it in my exclusion list. I start the executable and it creates a config.toml file, which I adjust with my settings. But after this first start the executable just won't run anymore?! Even after a reboot the executable won't start.
I can't be the only one experiencing this problem? Why can't I find anything about this in this thread?
Start the executable through command line and report the error text here, I started to rework error reporting, so the miner will wait for user input on errors, but I must have missed something. |
|
|
|
It's working with RX Vega 64.
AT 43.62MH/S in average.
Sigt ? Thats really cool |
|
|
|
Allright my bad I say that because i've tracked leaks with similar footprint in ethminer. Did you started from scratch in Rust or there was a code base alldeay ? From scratch, First commit is on 15th of April. |
|
|
|
This is the error I'm getting on most of the rigs. I have no idea what its all about.
17:37:21 - INFO prospector 0.0.12-ALPHA starting
17:37:21 - ERROR Could not load CUDA: Unknown error - Unknown error
17:37:21 - INFO OpenCL Initialized
17:37:21 - INFO Configuration successfuly loaded from config.toml
17:37:21 - INFO Not launching CPU miner
17:37:21 - INFO Device 0-0 disabled
17:37:21 - INFO Device 0-1 disabled
17:37:21 - INFO Starting api server on localhost:42000/api/v0/
17:37:21 - INFO Signatum: Subscribed, waiting for jobs
17:37:21 - INFO Signatum: Miner received subscription response
17:37:21 - INFO Signatum: Authorized by the pool
17:37:21 - INFO Signatum: Miner changed difficulty
17:37:21 - INFO Signatum: Miner received new job
17:37:24 - INFO Error, no reports
17:37:27 - INFO Error, no reports
17:37:30 - INFO Error, no reports
17:37:33 - INFO Error, no reports
17:37:36 - INFO Error, no reports
17:37:39 - INFO Error, no reports
17:37:42 - INFO Error, no reports
17:37:45 - INFO Error, no reports
17:37:48 - INFO Error, no reports
17:37:51 - INFO Error, no reports
17:37:54 - INFO Error, no reports
17:37:57 - INFO Error, no reports
17:38:00 - INFO Error, no reports
17:38:03 - INFO Error, no reports
17:38:04 - INFO Signatum: Miner received new job
17:38:06 - INFO Error, no reports
17:38:09 - INFO Error, no reports
17:38:11 - INFO Signatum: Miner received new job
17:38:12 - INFO Error, no reports
17:38:15 - INFO Error, no reports
17:38:18 - INFO Error, no reports
17:38:21 - INFO Error, no reports
17:38:24 - INFO Error, no reports
17:38:27 - INFO Error, no reports
17:38:30 - INFO Error, no reports
17:38:33 - INFO Error, no reports
17:38:36 - INFO Error, no reports
17:38:39 - INFO Error, no reports
17:38:42 - INFO Error, no reports
17:38:45 - INFO Error, no reports
17:38:48 - INFO Error, no reports
17:38:51 - INFO Error, no reports
17:38:54 - INFO Error, no reports
17:38:57 - INFO Error, no reports
17:39:00 - INFO Error, no reports
17:39:03 - INFO Error, no reports
17:39:06 - INFO Error, no reports
17:39:06 - INFO Signatum: Miner received new job
17:39:09 - INFO Error, no reports
17:39:12 - INFO Error, no reports
17:39:15 - INFO Error, no reports
17:39:18 - INFO Error, no reports
17:39:21 - INFO Error, no reports
17:39:24 - INFO Error, no reports
17:39:27 - INFO Error, no reports
17:39:30 - INFO Error, no reports
17:39:33 - INFO Error, no reports
17:39:36 - INFO Error, no reports
This happens because there are no miners running |
|
|
|
My bet is that you forked ethminer which contains loads of leaks... bad boys !
Nope. Ethminer is written in C++, Prospector is written in Rust. Memory leak on prospector only happens on specific AMD drivers and to very small amount of people. This leak is not a standard memory leak. This is some fatal flaw in the driver, or OpenCL libraary that I'm using. |
|
|
|
On all my rigs with 460/470/480 there is a memory leak from version 0.0.7 to the current win 8.1 and win 10  I believe this is related to drivers. Can you do a memory dump, and upload it somewhere ? ( TaskManager , right click on prospector -> create dump file). That could help. |
|
|
|
Yup, 19 again
(hope fix wasnt hash=hash+3, hehe)
Nope  . During the rewrite, I made a lot of the components more generic and shared between multiple miners. One configuration variable was not updated to specific value needed for signatum. |
|
|
|
0.0.11-ALPHA is out - WOHOO :-)Finally. This release contains first CUDA miner - ZCash, and a complete rewrite of several internal components. These changes should provide a great foundation for future improvements. Download: https://github.com/semtexzv/Prospector/releasesZcash was only tested on NiceHash, and I currently do not have any GPUs whatsoever to test other pools, if you mine ZCash on a pool other than NiceHash, please report here. Enjoy . My two RX560 went down from 19MH/s combined to 16MH/s combined mining signatum compared to version 0.10 I updated the latest release, please let me know if it fixes the issue. |
|
|
|
0.0.11-ALPHA is out - WOHOO :-)Finally. This release contains first CUDA miner - ZCash, and a complete rewrite of several internal components. These changes should provide a great foundation for future improvements. Download: https://github.com/semtexzv/Prospector/releasesZcash was only tested on NiceHash, and I currently do not have any GPUs whatsoever to test other pools, if you mine ZCash on a pool other than NiceHash, please report here. Enjoy . My two RX560 went down from 19MH/s combined to 16MH/s combined mining signatum compared to version 0.10 There weren't any changes to signatum mining code. Don't know what could have caused this :/. Edit: Probably found the issue, Uploading new build now. |
|
|
|
0.0.11-ALPHA is out - WOHOO :-)Finally. This release contains first CUDA miner - ZCash, and a complete rewrite of several internal components. These changes should provide a great foundation for future improvements. Download: https://github.com/semtexzv/Prospector/releasesZcash was only tested on NiceHash, and I currently do not have any GPUs whatsoever to test other pools, if you mine ZCash on a pool other than NiceHash, please report here. Enjoy .
|
|
|
|
|
*Development update*
Over the last week, I have rewritten parts of internal architecture of the miner. These changes will not show, but will siginificatnly speed up further development.
I also created new CUDA library, that will alow this miner to better utilize Nvidia Cards.
I will publish this version this week.
|
|
|
|
|
