Thank you very much for your kind words. I’m happy it’s all sorted.
Please do post back if you need any further assistance, we are here to help. :)
Thank you very much for your kind words. I’m happy it’s all sorted.
Please do post back if you need any further assistance, we are here to help. :)
For me personally.
Feathercoin has long been due a correction upwards. The fact that it was one of the first altcoins with a fucking fast blockchain should speak volumes!
Feathercoin works perfectly as a payment network and in my humble opinion - the tech shits all over BTC. Most if not ALL the issues Bitcoin has, have already been solved with Feathercoin in some way.
DEC 2018:
10+ USD (We can hope and pray :-) )
Hi All, test
I’m running a Feathercoin full node and wanted to get more out of it so I decided to set up a Feathercoin Block Explorer + API alongside my node.
If you would like to get your own Feathercoin Core full node up and running, see this guide:
http://forum.feathercoin.com/topic/8392/guide-build-feathercoind-v0-9-3-1-and-create-a-full-node-on-centos-7-minimal
I’ve set up a block explorer that I’m calling fsight, it’s based off the BitPay-Insight API, but uses Feathercoin.
Home Page: https://fsight.chain.tips
API Page: https://fsight.chain.tips/api
FSight is protected with SSL from LetsEncrypt.org
https://www.ssllabs.com/ssltest/analyze.html?d=fsight.chain.tips
Project Update Log:
. July 2017
– Added difficulty to homepage
– Updated backend node to v0.9.6.1
. June 2017
– Fsight added to 19800.com
. February 2017
– Updated backend node to v0.9.6
. December 2016
– Uptime and HTTPS monitoring added
– Fixed USD conversion - Now shows correct amounts when USD is selected, Thanks @AmDD !!
– Added to CoinMarketCap.com under “Explorer 2”
– Refreshed colour scheme
– Update to Decode OP_RETURN (coments in Blockchain)
– Added SSL/HTTPS
– Redirect from HTTP to HTTPS
. November 2016
– Webserver proxy configuration
. May 2016
– Stability Issues identified - webserver config changes fixed them
. April 2016
– Insight API online
. March 2016
– Originally started with iquidus explorer, and then moved to BitPays Insight-api
To Do/Coming Soon
Original Post:
Since I’m running my own full node, I figure I may as well put it to good use
It’s currently syncing, and I had to re-index my FTC block chain.
So far I think it looks pretty sweet. :-)
This is running on Centos 7 Minimal and I used the iquidus explorer with a few modifications.
Hello Everyone,
Feathercoin v0.9.6 has officially been released!
Feathercoin 0.9.6 has been officially released for the following platforms:
The official download links for 0.9.6 are below:
https://github.com/FeatherCoin/Feathercoin/releases/tag/v0.9.6
http://software.opensuse.org/package/feathercoin
You can see some fun screenshots below of the new client in action, these screen shots were taken on Windows 10.
The new loading screen…
The main wallet screen
The multi-sig screen
I’d like to personally thank @Wellenreiter @wrapper @AFB @ghostlander @lizhi @ChekaZ and all the others that worked on the code, website, marketing and anything to help get Feathercoin to where it is…I apologise if I’ve missed anyone from this list.
As always, if you have any questions, please feel free to post on the forums or if you’re a developer or techy who’s spotted an issue, you can raise an issue on the official Feathercoin GitHub here: https://github.com/FeatherCoin/Feathercoin/issues
Thank you for reading, we hope you enjoy the new client.
Hi All,
If you’d like to help the network, get yourself a little Centos7 VPS and create a full node! :-)
The following assumes a new Centos 7 Minimal Installation, and you’ve just logged in as root for the first time.
yum upgrade -y
yum install -y epel-release
yum -y install gcc-c++ libtool make autoconf automake openssl-devel libevent-devel boost-devel libdb4-devel libdb4-cxx-devel which git bzip2 wget
Since Centos 7 comes with a version of OpenSSL that has ECC disabled, we need to build a new version of OpenSSL with ECC enabled. Otherwise FTC wont run and will give you an ssl error on compile
cd /usr/src
wget https://www.openssl.org/source/openssl-1.0.2k.tar.gz
tar zxvf openssl-1.0.2k.tar.gz
cd openssl-1.0.2k
export CFLAGS="-fPIC"
./config --prefix=/opt/openssl shared enable-ec enable-ecdh enable-ecdsa
make all -j2
sudo make install -j2
cd /usr/src
git clone https://github.com/FeatherCoin/Feathercoin.git FTC
cd FTC
./autogen.sh
./configure --disable-shared --without-gui --prefix=/opt/feathercoin PKG_CONFIG_PATH=/opt/openssl/lib/pkgconfig LIBS=-Wl,-rpath,/opt/openssl/lib
make
sudo make install
If you try to run feathercoind now, it will complain about not having a conf file, so we need to create one.
.
.
.
Create blank feathercoin.conf
touch /root/.feathercoin/feathercoin.conf
Edit the conf file
vi /root/.feathercoin/feathercoin.conf
Add an rpc user and a complex password like in the example below.
rpcuser=feathercoinrpc
rpcpassword=HyeZz7WZJwCvYrThisISaComplexPassword7dX7ej1zbTV6s3
.
.
in Centos 7, we now have the awesome firewall-cmd client. which interacts with firewalld
Add port 9336
sudo firewall-cmd --zone=public --add-port=9336/tcp --permanent
Reload load the firewall rules after adding the feathercoin port.
sudo firewall-cmd --reload
You can check your open port with this command.
sudo firewall-cmd --list-all
You should see something like this.
public (default, active)
interfaces: eth0
sources:
services: dhcpv6-client ssh
ports: 9336/tcp
masquerade: no
forward-ports:
icmp-blocks:
rich rules:
.
.
cd /opt/feathercoin/bin
./feathercoind --server &
You can check on the status of your node with this command
./feathercoin-cli getnetworkinfo
And you should see something like this:
{
"version": 160000,
"subversion": "/Feathercoin:0.16.0/",
"protocolversion": 70015,
"localservices": "0000000000000409",
"localrelay": true,
"timeoffset": 3,
"networkactive": true,
"connections": 8,
"networks": [
{
"name": "ipv4",
"limited": false,
"reachable": true,
"proxy": "",
"proxy_randomize_credentials": false
},
{
"name": "ipv6",
"limited": false,
"reachable": true,
"proxy": "",
"proxy_randomize_credentials": false
},
{
"name": "onion",
"limited": true,
"reachable": false,
"proxy": "",
"proxy_randomize_credentials": false
}
],
"relayfee": 0.00100000,
"incrementalfee": 0.00001000,
"localaddresses": [
{
"address": "90.252.127.106",
"port": 9336,
"score": 3
}
],
"warnings": ""
}
.
.
Create the feathercoin service file
touch /etc/systemd/system/feathercoind.service
Edit the file
vi /etc/systemd/system/feathercoind.service
Add this to the file
[Unit]
Description=Feathercoinss distributed currency daemon
After=network.target
[Service]
User=root
Group=root
Type=forking
PIDFile=/root/.feathercoin/feathercoind.pid
ExecStart=/opt/feathercoin/bin/feathercoind -daemon -pid=/root/.feathercoin/feathercoind.pid \
-conf=/root/.feathercoin/feathercoin.conf -datadir=/root/.feathercoin
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=2s
StartLimitInterval=120s
StartLimitBurst=5
[Install]
WantedBy=multi-user.target
You can now start feathercoind with:
sudo systemctl start feathercoind
Youc an stop feathercoind with this:
sudo systemctl stop feathercoind
And you can check the status with this:
sudo systemctl status feathercoind
Finally, to configure the service to start at boot
sudo systemctl enable feathercoind
Edit 09/05/2018: Updated for version 0.16
Edit: Updated for version v0.9.6
I hope this helps someone. :-)
Exciting Times ahead!
Feathercoins mining reward has been scheduled to halve at block 1,793,041
At time of writing we are at block 1,790,926 which gives us 2115 blocks left or around ~35 Hours.
Time to party!!! :trumpet: :man_dancing_tone3: :man_dancing_tone3: :man_dancing_tone3: :trumpet:
This kind of movement looks like a pump, nothing more. FTC has many whales that pump the coin whenever the hell they like.
having said this, most of the big markets are reporting green atm.
1 - This was a Feathercoin Transaction with only Feathercoin Core installed
2, 3 - These were incoming and outgoing transactions with both Feathercoin and Bitcoin core installed
4, - This was me fucking up my build
5 - This is a transaction with both Bitcoin and Feathercoin Core installed…as you can see, the Feathercoin-QT icon loads
Updates:
Homepage has been updated. I’ve removed the 0.9.6 release announcement and I’ve added “Current Mining Difficulty” to the front page
Hey @addamnorth
This is really your call. you can do a few things but i guess the below is the simplest if you wanted to “own” everything
The FTC client (feathercoin-qt) generates addresses for you. You could do it yourself with an offline secure computer and a local client…you can print out the private and public keys yourself locally and use those. Test with small amounts first and make sure you test recovering your coins :-)
Hello, I’ll ask them to add it
@Wellenreiter @Bushstar - what do you guys think of the above idea ?
Keeping on topic.
Feathercoin needs to get used… in order for it to get used it needs to be accepted where people will use/spend it.
before we can do any of that I think the team wants to use the cryptowinter to iron issues with the difficulty adjustment algo. EHRC is not really the way forward I dont think…there are better algos out there right now and currently the team are testing some of them.
once our blocktime is at a stable 1 min regardless of wild hashrate fluctuations, I think we’ll have a better chance of getting accepted as a form of payment.
@wellenreiter said in Question or two for the more informed:
@AcidD Is a special BTCPay version for Feathercoin required, or will the ‘standard’ BTCPay sufficient?
So BTCpay works in the way where you clone the official repo and then specify the coin that you want to use. In our case FTC
@kelsey its great to see you around here again.
@j_scheibel BTCPay which now supports FTC should solve all of this for you.
It can also run in a docker container for easy portability
@Wellenreiter thanks for starting this thread, it’s an important discussion.
the trigger rule sounds interesting.
Question: Say the xxx minutes = 3. Am I right in understanding that every 3 mins if a block is not found the difficulty will half.
Say the diff is 100. After 3 mins the diff would be 50, if no block is found…after another 3 mins the diff will be 25…if no block is found the diff will be 12.5…and so on ?
Is that correct ?
Holy hell! Feathercoind running on android! Amazing
Well done @Reimelt