Please update to the latest version, 1.14.2. Your wallets from previous clients are fully compatible with the new client and testing has been successful.

Fastcoin has gained some ground in 2021 with a new marketing team, additional developers and a lot of new interest. There were a few changes that needed to be made, this was to help maintain the overall health of the blockchain. This is especially so for protecting the blockchain in the event that, at any point, Fastcoin inherits an influx of miners attempting to stress the network.

Fastcoin now supports merge mining, auxiliary proof of work, or AUX-POW. This method was first used by Namecoin in 2011 and was always planned for a future release someday. Fastcoin was almost too fast. In order to maintain a fully stable blockchain, not only for clients but also for exchanges, the 12 second block target was extended to 60 seconds. This is to ensure both stability and speed which go hand and hand for those hosting servers. Looking forward to seeing where Fastcoin finds it's place in the future.

RELEASE : v1.14.3.2

Fastcoin - Celebrating over eight years of fast & secure transactions.
------------------------------------------------------------------------
- Total coins will be 165,888,000.
- 60 second block target (Modified in 2021)
- Custom unique difficulty algorithm.
- Retargets once every hour or 300 blocks.
- Each block contains 32 coins which will be halved every year (or 2,592,000 blocks).
- (Currently 2 coins per block.)
- 4 confirmations per transaction.
- Ports: connection 9526, RPC 9527.
------------------------------------------------------------------------
Download the bootstrap.dat file a quicker sync time. https://archive.org/details/fastcoin_bootstrap

https://sourceforge.net/projects/fastcoin/

https://github.com/fastcoin-project/fastcoin

Thanks to Theymos, my account has been recovered and all of my old posts have been moved to this current account. I now have access to both m0gliE and m0gliEz. My account no longer contains the 2977 posts that were not made by me, however, the previous posts, 127 that were made by me have remained. This was due to the database breech that Bitcointalk.org had back in 2016 where my account, along with many others were sold off to innocent parties with the desire to gain their post status as well as their account reputation.

I didn't give up, although I did assume I would never regain my account again. I had proof of ownership and it took a bit of time before their fraud recovery team could come to the conclusion that in fact, I am the true original owner of this account.

Thank you all for your patience, this has been a long time waiting and caused me to drop interest in the cryptocurrency scene for years.

I plan on being more active, on here and on reddit. I also plan to gather up a new team of developers to assist in moving forward with Fastcoin.

-m0gliE

As I mentioned before, you'll need to revert to v.8.7.2 until the release of 0.10.4 which will be released later next week.

Please revert to v.8.7.2 until the release of 0.10.3. There were not enough users who upgraded to 10.2 before the block consensus was met. Version 10.3 will either remove this option all together or set a deeper block number into the blockchain to provide more time for users to upgrade to the new client.

Fastcoin Core 10.2.2 is derived from both Bitcoin/Litecoin 10.x. Look at the guides to solo mine bitcoin using the new version later then 10.2.x   
Bitcoin Core doesn't directly allow for stratum miners to connect, you will need a proxy to translate the two mining methods used by Bitcoin Core and CGminer.

For an Antminer S3, it's easy to setup using BFGminer.
Run BFGminer on the same computer as Fastcoin Core with the configuration below, you won't need any further settings altered or configured.

bfgminer --stratum-port=3333

BFGminer will launch, and retrieve the information needed for solo mining.                                                                    

You're now ready to solo mine against Fastcoin Core, you just have to point your miner at the IP address of the computer running BFGminer, and the miner should show up in the top section of BFGminer with its hashrate showing as "PXY" (stratum proxy). Any blocks will be paid out to the coinbase address shown in BFGminer, which is a new one generated from your wallet.

You should use a stratum proxy to solo mine.

The rpcallowip= configuration has changed, it no longer supports using "localhost". You must define the IP address or use a range such as "rpcallowip=192.168.1.1/24"

Fastcoin Core v0.10.2.2
 
Win-x64, Win-x86, OSX-x86, OSX-x64, Linux-x86, Linux-x64



IMPORTANT
v0.10.2.2 is now the official release version of Fastcoin Core. On top of the new features, this update contains very important security fixes and all users MUST upgrade to this version as soon as possible as details on several vulnerabilities will be made public on July 7th (Official Bitcoin warning). Pool operators, P2Pool and solo miners especially, as once BIP 66 is enforced, version 2 blocks will be rejected from the network entirely. P2Pool miners must upgrade to the latest version which can be obtained from forrestv's repo.

What's New in version v0.10?
This is a major release of Fastcoin Core, featuring the technical equivalent of Bitcoin v0.10.2 but with Fastcoin specific patches. The block synchronization and various internals are considerably faster and more efficient, and it has several major privacy improvements.  The most significant changes include:

• Watch-only wallet support. This allows the wallet to track transactions to and form wallets for which you know the address of but do not have the private key to.
• Faster blockchain synchronization due to headers-first synchronization and support for downloading blocks in parallel. Downloading the blockchain is now much quicker and can be completed within a few hours instead of taking days for some users.
• A REST interface which allows unauthenticated access to public node data when the -rest flag is specified.
• RPC Server “Warm-Up” Mode which starts earlier than previous versions. This helps users or services relying on it know that the server has already started and will be available soon.
• Improved signing security. This is due to using the libsecp256k1 library for signing instead of OpenSSL. libsecp256k1 is a cryptographic library optimized for elliptic curve uses which Litecoin relies on and was created by Bitcoin Core developer Pieter Wuille. Featuring better security, via hardening against timing leaks and derandomization, this library is believed to be better tested and more thoroughly reviewed than the implementation in OpenSSL.
• New utility applications including litecoin-tx for transaction related functionality and litecoin-cli for RPC command line functionality as litecoind no longer accepts them.
• Strict DER encoding for signatures (BIP 66). This introduces block version 3 and a new consensus rule which prevents non-standard transactions from being included in blocks. This also removes the dependency on OpenSSL’s signature parsing. Eventually, libsecp256k1 will be used for all consensus related tasks, depreciating the need for OpenSSL entirely.
• RPC Access Changes. RPC access now supports binary network addresses. This means that you can specify a single IP address, a CIDR network address or a netmask for accessing the RPC service.
• Please note, wildcard string matching no longer works and will display an error in the debug.log file when you attempt to use use a wildcard string in the rpcallowip= variable, either as a config setting or launch parameter.
  
  Example: Allow RPC access from IP addresses 192.168.1.1-192.168.1.254
  

Note: IPv6 addresses can also be used.

The major user-visible features that were new in Bitcoin v0.9 and v0.10 are not actually new for Fastcoin v0.10 because we backported it to Fastcoin v0.8 (like Coin Control).
For a complete list of Fastcoin Core specific changes, you can view the release notes here.

Fastcoin v0.10.2.2 is a minor release from the previous release candidate, featuring improvements and bug fixes. The changes can be seen below:

• Added option -alerts’ to opt out of the network alert system. Please note that disabling network alerts should only be used by power users as this system is used for network emergencies and important security releases. The default behavior is that network alerts are enabled.
• Detect and reject LibreSSL. This prevents a non-approved SSL library being used for compiling Fastcoin Core, preventing potential consensus compatibility issues.
• Improved getbalance RPC functionality to allow the user to display zero confirmation transactions (this works with watch-only addresses as well).
• PID file bug fix for non-Windows based systems.
• Bug fix for signing and verifying messages.
• New GPG Signing Process

Download Binaries
Binaries for Fastcoin can be located at the following mirrors covering all major operating systems. Fastcoin Core 64bit versions are now also available.

Download from Sourceforge
Download from Bitbucket
Download from Codeplex

Source
https://github.com/fastcoinproject/fastcoin/tree/10.2.2-irc
The master-0.10 branch contains the latest commits to the next stable releases of Fastcoin Core.

Build instructions for Linux can be found here.
Build instructions for OSX can be found here.

Bug Reporting
https://github.com/fastcoinproject/fastcoin/issues

WARNING
While this branch has been extensively tested to be compatible with the existing Fastcoin 0.8 network there is the possibility that we missed something.  BACKUP YOUR FASTCOIN DATADIR and wallet.dat because after you run v0.10 the old v0.8 version is no longer compatible with your on-disk data.

What's New in version v0.10?

This is a major release of Fastcoin Core, featuring the technical equivalent of Bitcoin/Litecoin v0.10.2 but with Fastcoin specific patches.

Major improvements in block synchronization and various internals are considerably faster and more efficient, and it has several major privacy improvements.

---

Sourceforge is still implementing server upgrades and currently is not accepting any new uploads to their servers.

The current release of updated clients (fastcoin-0.10.2.2) have been uploaded to the following mirrors.

https://fastcoin.codeplex.com/releases/view/616540

https://bitbucket.org/m0gliE/fastcoin/downloads

`

That listing just reflects the original upload date. Look at the details and directory listing here.

https://archive.org/details/Fastcoin_Blockchain

https://archive.org/download/Fastcoin_Blockchain

Yes, I'll be updating all the files hosted on archive.org this evening, including the individual blockchain files and the self-extracting bootstrap.dat.

Updated bootstrap.dat

Block 4651287 - 2015-04-22

https://sourceforge.net/projects/fastcoin/files/bootstrap/2015-04-22/

win32
https://drive.google.com/open?id=0Bz3NalaCIrQrWGh4N2F4NzlXZEE

source
https://drive.google.com/open?id=0Bz3NalaCIrQrSDJ4NElJOE1kZ28

compressed bootstrap.dat.xz

https://drive.google.com/open?id=0Bz3NalaCIrQrb3JSLTZVZkhadTQ

directory folder

https://drive.google.com/open?id=0Bz3NalaCIrQrdWp2Unp0bHZScmM

Look here on resolving orphan transactions.

0.1 FST for 15,000 FST doesn't seem very good.

http://www.fastcointalk.org/index.php/topic,1078.msg6504.html#new

That's a P2Pool node, all the coins are paid out directly to miners wallets, there is no way the "pool" can take any coins. If you're looking at the solved blocks list, you'll see there are a lot, however, because of the way P2Pool works on it's own sharechain, many of these blocks are orphaned or stale.

Perhaps you should read up on how P2Pool functions and I can also point out that it is decentralized.

https://en.bitcoin.it/wiki/P2Pool

That makes no sense, why would you be interested in a coin that is not only centralized, but operated by a single company. Sounds like a sham. Fastcoin has always promoted decentralization, not controlled or operated by a single entity. Gaw miners are using their coin as a way to increase their own mining profits, you don't see that?

https://www.cryptocoinsnews.com/josh-garza-address-growing-paycoin-paybase-scam-concerns-tnabc-miami/
https://bitcointalk.org/index.php?topic=900970.0
http://www.btcfeed.net/fraud/paycoin-next-big-scam-crypto/

"PayCoin (XPY) an altcoin backed by GAW miners, which is believed to be a scam, recently joined the Top 5 club of cryptocurrencies according to its market valuation on CoinMarketCap. At the time of valuation, PayCoin was also informally launched on 16th December with an initial investment of $54.5 million brought into the market. It is also believed that PayCoin is part of a ponzi scheme with GAW Miners playing a major role."

Much faster...

Fastcoin has a 12 second block time compared to their 60 seconds block time.
Fastcoin transactions confirm after 4 blocks, making a transaction complete in 48 seconds!
Compare this to their 5 confirmations x 60 seconds = 5 minutes to confirm a transaction.

They also require no transaction fee, which does not give their miners any incentive to mine.

Fastcoin has been sustained by providing miners a decent amount of fees for relaying transactions.

Fastcoin is not only fast, but it is also sustainable for it's community of loyal miners and their operations.

You should try to run the -reindex command line perimeter, what happens is that after downloading the bootstrap/blockchian, the blocks will sometimes be out of sync from what the other nodes tries to send or request blocks you already have which causes the client to have to sort out the differences. Running the -reindex line helps organize the database and makes the rest of the sync process run more smoothly. Also, while importing the blockchain, it's a good idea to only connect to one node so this doesn't happen. Set maxconnections=1 in your .conf so you don't get several nodes sending you chunks of 500 blocks that you may already have. After you import, you can change to something like maxconnections=30 and then run -reindex if needed.

How much ram do you have on your host allocated to fastcoind? Did you also provide a large enough swapfile?

What's happening is that the P2Pool network has so much hashrate that it's solving multiple's of the same blocks, causing some to orphan which in turn causes the daemon to improperly calculate the hashrate. So essentially the pool is assuming it has more hashrate because of the multiple blocks being submitting at the same time.

Just went up - bouncing around 251 MH/s while P2Pool is 330MH/s

P2Pool node - http://inetrader.com:5150/static/