Topic: Feathercoin [FTC] - page 28. (Read 460641 times)
I still expect this badboy to go up x10 this year. Litecoin is set to do the same so its fork should be able to achieve the same if the development doesn't stall
the cron job for payouts and finding blocks is a bit tricky. Once we find more blocks at a consistent rate the scripts perform better. I have alerts on the pool so usually get to it within a few hours if the cron job fails.
If it does fail it doesnt affect payouts or shares as it's only for the 1 block it failed on.
If you check the pool blocks page now you'll see it's all running as normal now and matches with the block explorer.
thanks for the explanation, so pool needs more hashpower. But blocks 2099990 and 2111177 are still missing in the blocks pool page.If it does fail it doesnt affect payouts or shares as it's only for the 1 block it failed on.
If you check the pool blocks page now you'll see it's all running as normal now and matches with the block explorer.
And I apologize for annoyance, but really want to have fully trustworthy pool for FTC (especially if it is official coin pool), so please make sure that everything is working great.
the official pool that I run pool.feathercoin.com mined a block around an hour ago....i've had no reported errors. We find blocks fine we just have a low hash rate because we only brought the pool up a few weeks ago.
could you tell me why do you apply 125 confirmations for payout? Official pool should have better conditions. Why do we have 6 confirmations for the blocks to be accepted and irreversible and some pools still work with 100+ confirmations?We can lower it at any time. I'll make it a little better than give-me-coins at 25 confirms before payout.
edit1: could you explain how the payout is working here? I can see mined block 2113227, confirmed, but in the statistics there is PPLNS Shares 0, Actual Shares 0, Percentage 0 and there is no payout for it (in the dashboard there is confirmed / unconfirmed - 0 too). How long does it take to your pool to distribute block reward among the miners?
edit2: and is there everything set well? I can see that your pool mined more blocks in the real than it is in the blocks section on its webpage. Currently can see that blocks 2099990, 2111177, 2113284 were mined by your pool but they are not visible and were not payed out to miners. You can see pool blocks from the pool page and compare it with the pool wallet where generated blocks are payed out (in chain explorer).
https://imgur.com/a/XcIGP
compare blocks with this
https://chainz.cryptoid.info/ftc/address.dws?6h6DfhjXWCnioT5kg5xgKkduhDfV3HNbJ8.htm
the cron job for payouts and finding blocks is a bit tricky. Once we find more blocks at a consistent rate the scripts perform better. I have alerts on the pool so usually get to it within a few hours if the cron job fails.
If it does fail it doesnt affect payouts or shares as it's only for the 1 block it failed on.
If you check the pool blocks page now you'll see it's all running as normal now and matches with the block explorer.
Hello everybody! I don't really understand - is the road map going right or will it change now?
the official pool that I run pool.feathercoin.com mined a block around an hour ago....i've had no reported errors. We find blocks fine we just have a low hash rate because we only brought the pool up a few weeks ago.
could you tell me why do you apply 125 confirmations for payout? Official pool should have better conditions. Why do we have 6 confirmations for the blocks to be accepted and irreversible and some pools still work with 100+ confirmations?We can lower it at any time. I'll make it a little better than give-me-coins at 25 confirms before payout.
edit1: could you explain how the payout is working here? I can see mined block 2113227, confirmed, but in the statistics there is PPLNS Shares 0, Actual Shares 0, Percentage 0 and there is no payout for it (in the dashboard there is confirmed / unconfirmed - 0 too). How long does it take to your pool to distribute block reward among the miners?
edit2: and is there everything set well? I can see that your pool mined more blocks in the real than it is in the blocks section on its webpage. Currently can see that blocks 2099990, 2111177, 2113284 were mined by your pool but they are not visible and were not payed out to miners. You can see pool blocks from the pool page and compare it with the pool wallet where generated blocks are payed out (in chain explorer).
https://imgur.com/a/XcIGP
compare blocks with this
https://chainz.cryptoid.info/ftc/address.dws?6h6DfhjXWCnioT5kg5xgKkduhDfV3HNbJ8.htm
the official pool that I run pool.feathercoin.com mined a block around an hour ago....i've had no reported errors. We find blocks fine we just have a low hash rate because we only brought the pool up a few weeks ago.
could you tell me why do you apply 125 confirmations for payout? Official pool should have better conditions. Why do we have 6 confirmations for the blocks to be accepted and irreversible and some pools still work with 100+ confirmations?We can lower it at any time. I'll make it a little better than give-me-coins at 25 confirms before payout.
Hi all,
am I the only one who has the impression that all known pools are currently "out of luck"?
Could it be that some pretty big player has started to hash with his own pool without anybody knowing it? Or why else seem most pools currently not finding any block?
Miningpoolhub is doing well, there is a block every several minutes. Currently round estimate 3,5 min with around 40% of whole FTC network. But this is not very good for FTC. Hashrate should be more distributed to other pools.am I the only one who has the impression that all known pools are currently "out of luck"?
Could it be that some pretty big player has started to hash with his own pool without anybody knowing it? Or why else seem most pools currently not finding any block?
others:
Theblocksfactory has only about 40MH/s with rounds in several hours. You can see that they reduced fee to 0% from the moment when miners gone. They had 2% fee before.
Give-Me-Coins has longer constant rate in the range 100-200MH/s with estimated rounds about 1-2 hour. They apply 1% fee but only 30 confirmations to payout (the best value among other FTC pools). Their luck is weak last days.
And in general, yes there is "somebody" with stronger hashrate who sometimes run in the FTC network. It was visible last days, when network diff was higher than ussual. Maybe it is the load from a multipool or a private bigger pool, who knows...
the official pool that I run pool.feathercoin.com mined a block around an hour ago....i've had no reported errors. We find blocks fine we just have a low hash rate because we only brought the pool up a few weeks ago.
could you tell me why do you apply 125 confirmations for payout? Official pool should have better conditions. Why do we have 6 confirmations for the blocks to be accepted and irreversible and some pools still work with 100+ confirmations? Volume $3.1 million! That is AWESOME 
Coinbase bringing SegWit online - would be amazing if they picked up FTC!!!
Coinbase bringing SegWit online - would be amazing if they picked up FTC!!!
:-) ! 24 hr Volume has gone past $ 6.5 million or 604 BTC.
Upbit seems to be leading the way this time which is interesting because Bittrex for the longest time has usually been the leader with the most volume.
Hi all,
am I the only one who has the impression that all known pools are currently "out of luck"?
Could it be that some pretty big player has started to hash with his own pool without anybody knowing it? Or why else seem most pools currently not finding any block?
am I the only one who has the impression that all known pools are currently "out of luck"?
Could it be that some pretty big player has started to hash with his own pool without anybody knowing it? Or why else seem most pools currently not finding any block?
the official pool that I run pool.feathercoin.com mined a block around an hour ago....i've had no reported errors. We find blocks fine we just have a low hash rate because we only brought the pool up a few weeks ago.
What is the unique value proposition of Feathercoin>
Hi all,
am I the only one who has the impression that all known pools are currently "out of luck"?
Could it be that some pretty big player has started to hash with his own pool without anybody knowing it? Or why else seem most pools currently not finding any block?
am I the only one who has the impression that all known pools are currently "out of luck"?
Could it be that some pretty big player has started to hash with his own pool without anybody knowing it? Or why else seem most pools currently not finding any block?
Heelloooo
just starting.
Whats the better pool for mine??
If you have a decent hashpower the best way is to use official: pool.feathercoin.comjust starting.
Whats the better pool for mine??
if your miner is weak, choose bigger pool where rounds are faster:
give-me-coins.com
feathercoin.miningpoolhub.com
nice, thanks alot.
Testing with very low hash but if it work nice i will change for my rigs. So perfect answer
Heelloooo
just starting.
Whats the better pool for mine??
If you have a decent hashpower the best way is to use official: pool.feathercoin.comjust starting.
Whats the better pool for mine??
if your miner is weak, choose bigger pool where rounds are faster:
give-me-coins.com
feathercoin.miningpoolhub.com
Heelloooo
just starting.
Whats the better pool for mine??
just starting.
Whats the better pool for mine??
Volume $3.1 million! That is AWESOME
Coinbase bringing SegWit online - would be amazing if they picked up FTC!!!
Coinbase bringing SegWit online - would be amazing if they picked up FTC!!!
Code:
Making all in src
make[1]: Entering directory '/home/ftc/source/Feathercoin/src'
cd .. && /bin/bash /home/ftc/source/Feathercoin/build-aux/missing automake-1.15 --foreign src/Makefile
cd .. && /bin/bash ./config.status src/Makefile depfiles
config.status: creating src/Makefile
config.status: executing depfiles commands
make[2]: Entering directory '/home/ftc/source/Feathercoin/src'
make[3]: Entering directory '/home/ftc/source/Feathercoin/src/secp256k1'
make[3]: Leaving directory '/home/ftc/source/Feathercoin/src/secp256k1'
CXXLD feathercoind
/usr/bin/ld: crypto/libbitcoin_crypto.a(crypto_libbitcoin_crypto_a-neoscrypt.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
crypto/libbitcoin_crypto.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:3428: recipe for target 'feathercoind' failed
make[2]: *** [feathercoind] Error 1
make[2]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:8650: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:689: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
make[1]: Entering directory '/home/ftc/source/Feathercoin/src'
cd .. && /bin/bash /home/ftc/source/Feathercoin/build-aux/missing automake-1.15 --foreign src/Makefile
cd .. && /bin/bash ./config.status src/Makefile depfiles
config.status: creating src/Makefile
config.status: executing depfiles commands
make[2]: Entering directory '/home/ftc/source/Feathercoin/src'
make[3]: Entering directory '/home/ftc/source/Feathercoin/src/secp256k1'
make[3]: Leaving directory '/home/ftc/source/Feathercoin/src/secp256k1'
CXXLD feathercoind
/usr/bin/ld: crypto/libbitcoin_crypto.a(crypto_libbitcoin_crypto_a-neoscrypt.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
crypto/libbitcoin_crypto.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:3428: recipe for target 'feathercoind' failed
make[2]: *** [feathercoind] Error 1
make[2]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:8650: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:689: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
try it like this please
./configure CFLAGS=-fPIC CXXFLAGS=-fPIC --enable-shared
Code:
Making all in src
make[1]: Entering directory '/home/ftc/source/Feathercoin/src'
cd .. && /bin/bash /home/ftc/source/Feathercoin/build-aux/missing automake-1.15 --foreign src/Makefile
cd .. && /bin/bash ./config.status src/Makefile depfiles
config.status: creating src/Makefile
config.status: executing depfiles commands
make[2]: Entering directory '/home/ftc/source/Feathercoin/src'
make[3]: Entering directory '/home/ftc/source/Feathercoin/src/secp256k1'
make[3]: Leaving directory '/home/ftc/source/Feathercoin/src/secp256k1'
CXXLD feathercoind
/usr/bin/ld: crypto/libbitcoin_crypto.a(crypto_libbitcoin_crypto_a-neoscrypt.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
crypto/libbitcoin_crypto.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:3428: recipe for target 'feathercoind' failed
make[2]: *** [feathercoind] Error 1
make[2]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:8650: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:689: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
make[1]: Entering directory '/home/ftc/source/Feathercoin/src'
cd .. && /bin/bash /home/ftc/source/Feathercoin/build-aux/missing automake-1.15 --foreign src/Makefile
cd .. && /bin/bash ./config.status src/Makefile depfiles
config.status: creating src/Makefile
config.status: executing depfiles commands
make[2]: Entering directory '/home/ftc/source/Feathercoin/src'
make[3]: Entering directory '/home/ftc/source/Feathercoin/src/secp256k1'
make[3]: Leaving directory '/home/ftc/source/Feathercoin/src/secp256k1'
CXXLD feathercoind
/usr/bin/ld: crypto/libbitcoin_crypto.a(crypto_libbitcoin_crypto_a-neoscrypt.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC
crypto/libbitcoin_crypto.a: error adding symbols: Bad value
collect2: error: ld returned 1 exit status
Makefile:3428: recipe for target 'feathercoind' failed
make[2]: *** [feathercoind] Error 1
make[2]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:8650: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/ftc/source/Feathercoin/src'
Makefile:689: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
Segwit in 9 days, guys =)
This coin is going to explode soon! 
Any reason why you think this?
I'm certainly hopeful as I'm mining it (and have been for sometime) with my balance slowly accumulating.
I found it to be fairly stable throughout the last few months of volatility which was a nice change from most of the alts!
The only reason I think this, is the current valuation doesn't make sense to me. How can an established old coin with an active developer have the same marketcap as total shitcoins that haven't had development in months?
Either the market expects bushstar to go work for another coin again, or I'm missing a piece of the puzzle.
Where will the market go this year?
Quote
....DAPPS.
Dapps? Are there more information available how Feathercoin will utilizes decentralized apps? Will there be a new layer introduced?