Best posts made by TimboSlice

Hey all, just starting a newbie thread so I can post elsewhere

@Wellenreiter said:

@TimboSlice

First of all, welco!e to Feathercoin and the forum.

For your questions:

1. The p2pool nodes are operated by different forum members. They all build one virtual pool that works on the same block and shares the payouts. You can setup one pool node as primary and another one as secondary, and if yoir moner needs to switch, you keep your payouts

2. I think yes

3. yes

4. yes

Thanks for the answers! I figured that’s how it all worked, but getting confirmation is nice.

Thanks for the replies!
I’m running 1x MSI R9 390 and 2x Sapphire R7 370’s on windows 7 with the AMD 15.12 drivers installed, as those were the ones that work best with ETH mining. IIRC, the 390 is hashing at ~580kh or 630kh and the 370’s are hashing at ~250kh or 300kh, depending on if I have them overclocked or not.
The problem might be due to having two different types of cards running on the same miner, since the 390 is so much faster than the 370’s, but they work fine with ETH mining and I haven’t had a chance to only run one type of card at a time yet.
I’ll try out the P2pool this weekend and mess around with only having one type or card running at a time and the other variable options.

Can the intensity be changed/lowered in NSGMiner? I tried to lower and raise it but it never seemed to actually affect the intensity.

Hi all, just started mining FTC part time along with ETH. I may have followed @greenuser over here from the ETH forums :smiley: and figured it would be a good idea to diversify my mining a bit.
I got set up mining just fine at just over 1 MH using nsgminer and The Blocks Factory FTC Pool, however, I have what seems to be a bit high of an invalid hashrate and reject rate. My reject rate according to the miner is around 10%, it seems like it’s sometimes slow to get new work and hashes on an old block, gets rejected, then gets new work.
The invalid hashrate according to the pool bounces anywhere from 10%-20%.

So a few questions;

1. Are the reject rate at the miner and invalid hashrate at the pool connected?
2. Are these percentage high or normal? They seem high to me.
3. Any suggestions on how to fix?

My .bat file for the miner just has the -g 1 -w 128 -I 16 variables, but honestly I don’t know what they do besides the intensity.

I haven’t had time to play around with different pools yet, but I likely will this weekend at some point.

Thanks!