Today, October 6th around 3:20 PM a strange behavior of some Feathercoin clients where noticed by the community.
Further investigation showed that an attempt of a DOS attack was causing the problem.
The attack tried to use a recently discovered vulnerability of Bitcoin code versions < 0.16.3, causing the attacked block chain to stop working correctly and mint the block chain to the attackers advantage.
The Feathercoin devepoment team released a fix against this attack on September 22nd 2018.
This fix together with Feathercoins advanced checkpointing (ACP) mechanism defended the block against the attack.
Current status is:
FTC Blockchain is operating normally
FTC Clients with version < 16.3 are stuck at block 2366280
Actions to re- activate stuck clients:
upgrade your client to the latest Version
see ttps://feathercoin.com/#wallets for latest releases for your OS
Restart the client with the -rescan comand line paramter
wait until the client is fully synced again and compare the block count with the one shown on https://explorer.feathercoin.com
check here:
https://www.coingecko.com/en/coins/feathercoin/trading_exchanges#panel
and here:
https://coinmarketcap.com/exchanges/volume/24-hour/all/
you need to click on ‘view more’ to find the FTC volumes
I think it is obvious
Just a note re: Implementation of totalitarian brig brother style monitoring of population, and (Cough) Serco Artificial Intelligence Daemon face recognition software.
https://forum.feathercoin.com/topic/6526/exchanges-that-trade-feathercoin-ftc
I also notice the FBI are monitoring the content of chat apps here :
https://www.nbcnewyork.com/investigations/Terror-Plot-New-York-Concert-Landmark-ISIS-Las-Vegas-Arrest-Times-Square-449749293.html
Three men living outside the U.S. planned to attack concerts, Times Square and crowded subways in 2016 in an ISIS-inspired attack that one of the suspects said he hoped would be “the next 9/11,” authorities announced on Friday afternoon.
The FBI said the three men — Abdulrahman El Bahnasawy, a 19-year-old Canadian citizen; Talha Haroon, a 19-year-old U.S. citizen based in Pakistan; and Russell Salic, a 37-year-old orthopedic surgeon in the Philippines — allegedly used chat apps to talk about bringing a car bomb into the Crossroads of the World, gunning down subway riders before detonating vests and opening fire on concert goers in the vein of the Paris terror attacks of 2015.
“NY Needs to fall. This is a must,” Haroon allegedly wrote in a message to an undercover agent posing as an ISIS sympathizer.
FBI and NYPD officials told the I-Team the plot was more aspirational than operational. But according to the indictments, Al Bahnasawy, who has already pleaded guilty to multiple charges, traveled to Cranford, New Jersey, in May of 2016 and had designs on carrying out the attacks before he was cuffed by authorities waiting there for him.
Thanks for the heads up.
This Token isn’t listed on any exchange yet so I don’t think people are getting confused with the names…unless they are really, really stupid…
This seems like very bad business practice, especially because they don’t announce it on their main page. They should ask for donations instead, like Wikipedia does, and if that + ads doesn’t sustain their business model, just let it go.
@kelsey I know Ive mentioned it many times over the years. I used to play some MMORPG games back in the day which had some ingame ‘money’ that you earned and spent on items. I always thought that would be a great entry point for a crypto but soon realized one as slow as Bitcoin probably wouldnt be best. However, Feathercoin might be a good fit… now to find someone who can/will build the game…
@AmDD said in Full Node Status Page:
@Wellenreiter said in Full Node Status Page:
@wrapper said in Full Node Status Page:
Great, can we ban versions above ours as well as bellow? … 75000 = worldcoin
Better to ban based on subversion, banning on version number may cause problems during the roll out of new releases
Is there an easy way to do this? Automatically in the wallet? A script? Manually?
Currently it can be compiled in for the 11.x based code . There is no option do configure it through the command line or the config file and 0.9x doesn’t have that feature… yet
@bsotnikow said in How is it possible?:
Now with a stable BCH out there. FTC can be fine never implementing segwit and stay relevant with Bitcoin upgrades…Anything they do on BTC, they’ll figure out eventually on BCH (and FTC).
My purpose was more, what is the use of scaling FTC in the current state of it’s development ?
And actually I’m not a fan of SegWit, the fact that you separate Signature from the transaction, this kind of “separate chain”, we already have SPV client for light wallet so I don’t see the urge nor the goal. (Some will say Maleability fix)
There is so many other ways to scale. I hope Feathercoin comunity gonna be wiser than Bitcoin one.
So don’t panic, just grab a towel.
@AcidD Awesome thanks. I must be thinking of something else. Following too many coins these days…I want to get some VIVO and TZC too when they hit exchanges that i use. Great to see more neo adoption.
Long live FTC!
Yea, always been that way too on every coin. The top wallets are exchanges, thats why they have thousands and thousands of transactions. No single investor would have a reason to be moving their funds around constantly.
@peeet said in Coinmarketcap and Coingecko:
Lol, I just read in the other thread that 19800 will be closing anyway.
Sorry I forgot to ping here. Yeah some hot news in China. Wait and see.
Anyway you prove than FTC is alive and that is priceless. Thanks a lot for that.
NeoScrypt now used for Scrypt hash generation in the code, CheckProofOfWork set to use hash and nBits instead of height same as Bitcoin and GetPoWHash toggles between Scrypt and NeoScrypt based on time instead of height as suggested by Ghostlander.
https://github.com/FeatherCoin/Feathercoin/commit/cea31da289d1f5ad0487dc080ccf130b8cef43f2
Fork height, fork times and checkpoint keys defined in chainparams.
https://github.com/FeatherCoin/Feathercoin/commit/e9dae3dcd5b7adfc280a1c9f05c625a7730f8923
getwork has been restored in the commit in my post above. Once my client has synced the changes will be pulled into the 0.9.6.2 branch. They are currently on my own 0.9.6.2-bushstar branch.
