PS - why does my name say “spammer” beside it…?
Posts made by jimmy24651
-
RE: Neoscrypt ASIC mining - outlook...?
-
RE: Neoscrypt ASIC mining - outlook...?
@AcidD
@Bushstar
@ChekaZ
@WellenreiterI don’t remember who all else should be tagged… but this is a good start!
-
Neoscrypt ASIC mining - outlook...?
https://bittech.cn.com/#hproduct
This is about to be a thing.
What is the outlook from the team regarding ASIC mining?
-
RE: Can't start mining...?
Well, you’re definitely not mining.
You are connected, because the miner is showing new blocks as they come in. I can’t be 100% certain of this, but it seems as though the antivirus is what is causing your problem. Some of these guys who know more about the technical side may be able to look at your log file and let you know for sure, but for now (since it may take them a little while to see this), I would definitely try just totally disabling your antivirus to see if that corrects the problem. If it does, at least you know what you’re looking for. Past that, I don’t know enough about your antivirus to really give you any advice on how to get around it.
-
RE: Can't start mining...?
@chekaz I believe that the newer versions of the wallet make solo mining with the strategy you offered impossible. I solo mined for quite a while just as you stated, but once the wallet got to .13 (I believe), it was no longer possible. From the questions I asked on here, I think it had something to do with getwork vs getblock or something like that.
-
RE: Can't start mining...?
@ClickinOrka
When I first started trying to mine, I beat my head up against a wall (figuratively) for quite a few days before I finally found success. Stick with it, and you’ll eventually get it working.As far as your comment that there’s no way this should be this complicated, that’s exactly how I felt when I got started. The longer I messed around with it, the less I felt this way. Once you get it working, you’ll feel a great sense of accomplishment, and every thing you try afterwards will be that much easier. FTC was the first coin I ever mined, so I learned the most from it. Since then, I have mined pretty much every coin you can think of, at least a little. Trust me when I tell you that all of the coins I mine since then have been much easier…not because it is hard to mine FTC, but because I learned so much with FTC, I was able to apply that knowledge across the board.
The first thing you have to bear in mind is that most miner programs were developed with a specific type of GPU in mind. Since you said you’re using a GTX, I would start with CCMiner, and ChekaZ recommended. CCMiner is the most efficient miner I found to work.
- Join a pool. My favorite pool is the “official” pool which is ran by the developers on this forum. This pool charges no fee, so if you end up sticking with mining, I would highly recommend donating to the pool as a thank you to these guys!
-Download whatever version of CCMiner you choose (typically, the newer ones are faster)
My favorite miner is here: https://github.com/ghostlander/cudaminer-neoscrypt create a text document in the same folder with the miner.
- Put this line in the body of the text file:
“cudaminer-x64.exe” -o “stratum+tcp://pool.feathercoin.com:6056” -u “worker” -p “password”
All of the fields which I put quotation marks around are going to be specific to your mining program, your pool, and your worker name on the pool. You need to remove all quotation marks from your actual file. After entering all of this info, you want to save the file with .bat at the end, rather than .txt
This is what my .bat file looks like -
cudaminer-x64.exe -o stratum+tcp://pool.feathercoin.com:6056 -u jimmy24651.4 -p xjimmy24651 is my login on the pool, and this particular worker is named 4.
Run this batch file, and you should be good to go.
I try to keep up on here as much as possible, so if this doesnt work, let me know and I’ll try to respond as soon as possible.
I hope this helps!
-
RE: [Dev] Feathercoin 0.13.x - Functional requirement / Development / Testing notes
@wrapper
Where is the option to change to the dark layout…? -
RE: Problems with 0.13 wallet
you dont have to apologize, man… its no big deal to me. i am just trying to give you guys a heads up.
6fb52561cb7022a46c02a30ae53bfcc9e1d1887010f795f75cfeda5b4610156d
-
RE: Problems with 0.13 wallet
I hate to beat a dead horse, since this is something that we’ve already discussed, BUT, I did want to keep everyone in the loop of what I am seeing just in case you all are not seeing the same things.
I had the exact same thing as I described above happen again this morning.
I sent 3 different transactions this morning to my “main desktop wallet”. The first two, which consisted of 40 coins a piece, were sent from 2 separate wallets, went through as expected, with no problems. The third one was sent immediately after these 2, from a third wallet, and has still not confirmed. It has been 60 minutes since the coins were sent!
-
RE: Solo mining batch file no longer works after wallet update...
Thanks for the info!
-
RE: NeoScrypt CUDAminer
I just saw this post. Can’t believe I missed it… Thanks for the release, Ghost!
-
RE: Solo mining batch file no longer works after wallet update...
@Bushstar @Wellenreiter @AcidD
I first added "onlynet=ipv4 to the feathercoin.conf file, closed out the wallet, restarted it, and the problem was still there. Same error when I tried to start the miner.
Next, I updated the rpcallowip command to “rpcallowip=127.0.0.1” as instructed, and I went ahead and made the user and password something more secure. I restarted the wallet again, and am still getting the same error.
Is there anything more that I can do which would help any of you isolate what may be causing the problem? Go slow for me, as I know very little about the tech-side of things, aside from mining, and this little hiccup has shown me that I don’t know as much about mining as I thought I did!
-
RE: Solo mining batch file no longer works after wallet update...
Thanks for the replies, guys!.. I’ll give this a shot this evening and see what happens!
-
RE: Problems with 0.13 wallet
…and just like that, 15 seconds after I made this post, both of my pending transactions came through…
I will leave this post up in case someone else has a miniature heart attack thinking that they have lost some coins, maybe they’ll come across this post and take a deep breath! =o)
-
Problems with 0.13 wallet
As posted earlier, I have had no luck solo mining with this new wallet. I don’t know enough of the technical side to answer most of the questions that I was asked to diagnose the problem, so for the time being, I will not update the wallets on my miners. Easy enough of a solution…
Bigger problem: I got home this evening, and decided to send my mined coins from the miner wallet over to my desktop “main” wallet. As you can see from my 1st picture (this is the sending wallet), I am going on 20 minutes now since I have sent the coins. Every time in the past I have EVER sent coins to myself, I have a “sent” dialogue pop up, and almost immediately, a “received” dialogue pop up on the machine with the other wallet. As you can see from the 2nd picture (this is from my receiving wallet), I have not even received the coins into my receiving wallet with an “unconfirmed” message…
I don’t know what’s going on…but it is troubling me…
I have went over to the Feathercoin FSight block explorer, and this transaction is still showing unconfirmed…25 minutes later!
-
RE: Solo mining batch file no longer works after wallet update...
you guys are talking about things which i dont understand.
i dont know how my wallet would be using the tor network. i dont even know what that means.
all i did was download a copy of the latest wallet from the website.
-
RE: Solo mining batch file no longer works after wallet update...
Bear in mind, this worked flawlessly before the upgrade. I actually have other machines currently using it, which I haven’t upgraded.
I dont know exactly what I’m looking at on the debug file. I copied the last few lines. Maybe this will help…
2018-02-25 19:55:31 Peer 159.100.246.11:9336 unknown, sending version using dual magic
2018-02-25 19:55:31 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:55:31 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:39830, peer=2
2018-02-25 19:55:31 AdvertiseLocal: advertising address 73.7.68.100:9336
2018-02-25 19:55:39 No valid UPnP IGDs found
2018-02-25 19:55:39 upnp thread exit
2018-02-25 19:55:41 Loading addresses from DNS seeds (could take a while)
2018-02-25 19:55:42 27 addresses found from DNS seeds
2018-02-25 19:55:42 dnsseed thread exit
2018-02-25 19:55:43 Peer 94.130.69.120:9336 unknown, sending version using dual magic
2018-02-25 19:55:43 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:55:43 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:44545, peer=3
2018-02-25 19:55:43 AdvertiseLocal: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:55:46 upnp thread start
2018-02-25 19:55:56 No valid UPnP IGDs found
2018-02-25 19:55:56 upnp thread exit
2018-02-25 19:56:00 Peer 173.212.192.212:9336 unknown, sending version using dual magic
2018-02-25 19:56:00 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:56:00 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:36714, peer=4
2018-02-25 19:56:00 AdvertiseLocal: advertising address 73.7.68.100:9336
2018-02-25 19:56:06 Peer 176.9.50.227:9336 unknown, sending version using dual magic
2018-02-25 19:56:06 ProcessMessages(version, 103 bytes) FAILED peer=5
2018-02-25 19:56:07 Peer 24.57.129.35:9336 unknown, sending version using dual magic
2018-02-25 19:56:07 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:56:07 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:48793, peer=6
2018-02-25 19:56:07 AdvertiseLocal: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:56:13 Peer 188.165.254.191:9336 unknown, sending version using dual magic
2018-02-25 19:56:13 ProcessMessages(version, 105 bytes) FAILED peer=7
2018-02-25 19:56:52 Peer 207.134.44.31:9336 unknown, sending version using dual magic
2018-02-25 19:56:52 ProcessMessages(version, 107 bytes) FAILED peer=8
2018-02-25 19:57:09 Peer 104.225.220.19:9336 unknown, sending version using dual magic
2018-02-25 19:57:09 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:57:09 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=73.7.68.100:42940, peer=9
2018-02-25 19:57:09 AdvertiseLocal: advertising address 73.7.68.100:9336
2018-02-25 19:57:32 Peer 192.77.188.104:9336 unknown, sending version using dual magic
2018-02-25 19:57:32 ProcessMessages(version, 107 bytes) FAILED peer=10
2018-02-25 19:57:33 Peer [2a01:4f8:130:11a6::4]:9336 unknown, sending version using dual magic
2018-02-25 19:57:33 ProcessMessages: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 19:57:33 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103945, us=[2601:cd:c100:535c:1d5c:57dd:7466:27ae]:63680, peer=11
2018-02-25 19:57:33 AdvertiseLocal: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 19:57:39 Peer 78.129.241.145:9336 unknown, sending version using dual magic
2018-02-25 19:57:40 ProcessMessages(version, 107 bytes) FAILED peer=12
2018-02-25 19:57:40 Peer 86.5.228.85:9336 unknown, sending version using dual magic
2018-02-25 19:57:47 Peer [2001:41d0:2:c9bf::]:9336 unknown, sending version using dual magic
2018-02-25 19:57:47 ProcessMessages(version, 105 bytes) FAILED peer=14
2018-02-25 19:57:47 Peer 37.187.106.98:9336 unknown, sending version using dual magic
2018-02-25 19:57:47 ProcessMessages(version, 107 bytes) FAILED peer=15
2018-02-25 19:57:58 UpdateTip: new best=149143892ddd5b133184ae5b223c0126f95b7ef8e127bd36d91824168f5202d8 height=2103946 version=0x00000002 log2_work=58.344688 tx=4199690 date=‘2018-02-25 19:57:17’ progress=0.999998 cache=0.0MiB(23tx)
2018-02-25 19:57:58 ProcessMessages(version, 107 bytes) FAILED peer=13
2018-02-25 19:57:59 Peer 84.153.220.102:9336 unknown, sending version using dual magic
2018-02-25 19:58:17 Peer 46.4.0.101:9336 unknown, sending version using dual magic
2018-02-25 19:58:17 ProcessMessages: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:58:17 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103946, us=73.7.68.100:43255, peer=17
2018-02-25 19:58:17 AdvertiseLocal: advertising address [2001:0:5ef5:79fb:20bc:7fd7:b6f8:bb9b]:9336
2018-02-25 19:58:23 Peer [2a02:c207:2008:7125::1]:9336 unknown, sending version using dual magic
2018-02-25 19:58:23 ProcessMessages: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 19:58:23 receive version message: /Feathercoin:0.13.0/: version 70015, blocks=2103946, us=[2601:cd:c100:535c:1d5c:57dd:7466:27ae]:63858, peer=18
2018-02-25 19:58:23 AdvertiseLocal: advertising address [2601:cd:c100:535c:1d5c:57dd:7466:27ae]:9336
2018-02-25 20:01:51 tor: Thread interrupt
2018-02-25 20:01:51 torcontrol thread exit
2018-02-25 20:01:51 msghand thread interrupt
2018-02-25 20:01:51 scheduler thread interrupt
2018-02-25 20:01:51 addcon thread interrupt
2018-02-25 20:01:51 opencon thread interrupt
2018-02-25 20:01:51 net thread interrupt
2018-02-25 20:01:51 Shutdown: In progress…
2018-02-25 20:01:51 StopNode()
2018-02-25 20:01:52 Shutdown: done