Hi @jalthage

That service has nothing to do with the main Feathercoin team.

0_1523529660382_e0b9317a-456b-45ad-a03c-d453b59858d8-image.png

it looks like their DNS is configured incorrectly.

Uploaded NeoScrypt CUDAminer v1.0.1. It supports Kepler (GK110) in addition to Maxwells and Pascals. The original Titan, Titan Black, Titan Z, GTX 780 Ti and GTX 780. Keplers were never energy efficient, so the hash rate is about 400KH/s for 200W TDP. Well, it works at least.

Hello. What version of Feathercoin are you running on your pool ?

@ghostlander said in Mining... am I doing it right?:

It doesn’t matter much what driver version is in use. All CUDA miners have kernels built at the compile time by a specific CUDA toolkit.

but it does matter. eg, using alexis with driver newer than 184.xx gives only half of hashrate and does not matter how is intensity set. It has something to do with used CUDA version. I am windows user and I am not able to compile ccminer directly to my system, so I would depend on what is available on the internet.
If I use later driver than 184 and want to use alexis - it gives me max about 450kh/s.
Using tpruvot with the latest driver gives me back about 770kh/s.

@bushstar

Thanks for the info!

@goodthebest said in blocknotify - yiimp:

blocknotify

Read this and see how he’s doing it.

https://bitcointalk.org/index.php?topic=448565.0

you can look at a chart here which shows the avg

https://bitinfocharts.com/comparison/feathercoin-confirmationtime.html

the target is 1 min block time…so every min 1 block should be confirmed

60 mins in every hour so roughly 60 blocks an hour give or take a few…

Answering my own question in case of linux

for detailed debug report, in feathercoin.conf, there should be debug=1

run this command for real time debug,. to exit, Ctrl + C
tail -f ~/.feathercoin/debug.log

@acidd I tried and compiled nsgminer on 5 different machines and result is the same, I’m using ubuntu 16.04.3 lts version. Blocks are found but actually they are never materialized. I’ve reported to developer at Github: ghostlander (John Doering) he’s still looking into it I guess.

Even I’ve discussed same issue with Guncoin’s Peter Bushnell and he told me he ask sent a message to John Doering. Peter Bushnell said “The miner may not like Version Bit blocks. I’ll check with the developer.”, so he did report to nsgminer developer.

Perhaps you can test yourself but use GPU version, it might help to find out what’s going wrong.

@slakov

Well, that is an more or less easy calculation, even there are some variances due to the fact, that the actual block times vary.

The block reward halves ~every 4 years the currently calculated date of the next halving can be found on the
[Feathercoin Homepage[(www.feathercoin.com) we are currently at a reward of 40 FTC / block.

So the halving is 40/20/10/5/3/2/1/0 (the last 4 values are because the reward will be in full coins always.

The halving from 40 to 20 FTC per block is shown at the page mentioned above, that leaves 6 halvings plus the time till the 40/20 FTC halving
So the final Feathercoin will be mined 6x4 years + 1234 days (= 3.38years) from today.

If I’m not wrong this is 2018+24+3.38 what gives some day in 2045 for the last coin mined.

If I made a mistake in the calculation, someone correct me.
I hope to be still alive that day :D

Regarding LTC, it’s not a question about the total number of coins mined and the number of blocks per time frame, but more how frequently the halving is done.

@acidd said in Feathercoin pool:

@Wellenreiter

Chekaz and I set up pool.feathercoin.com :-)

Well done !!! :D

@wellenreiter It’s neat and clear answer. Yep it was about solo mining.

@jimmy24651 said in Solo mining, never got payout...:

I tried shutting down the wallet, and restarting…no luck… Does anyone have any idea at all what may have caused this?

I have no idea, what can cause the problem.
@Tobi97l is right, if you get a notification the wallet has seen the transaction and should show it in the overview page as well as in the transaction page.

I suggest that you go to http://explorer.feathercoin.com or https://fsight.chain.tips and enter you wallet address in the search pages there.
The explorer should come back with a list of transactions and the balance related to the wallet’s address.
If there are no transactions shown, you never received a payout.

see my answer to your other thread:
https://forum.feathercoin.com/topic/9558/solo-mine-with-feathercond-daemon/6

You need to use the RPC port to connect a miner, which is 9337.
In addition you need to configure

server=1
rpcpassword= <a long sequence of characers> ( This is the password to use for the miner)
rpcuser= < a name> (this is the user to use for the miner)
rpcallowip= <ipaddress of the miner> (can be 127.0.0.1 if the miner is on the same host as the wallet