Supported Feathercoin client versions: Current production Version: 0.16.0.

Old Production Version: 0.13.2

Info: If you have problems to post, create one post in the ‘newbies’ category and try again. If you have further problems, find support under Guides or use the shoutbox

[Dev] Feathercoin 0.9.6.2 * Maintenance fix, build & upgrade issues notes.


  • Moderators

    Feathercoin 0.9.6.2 – Notes and discussion

    Task : Re factor all changes from 0.9.6.0 to 0.9.6.1 into version 0.11. UI updates, new icons splash screen, tests, colour scheme etc.

    All commits after : updated commentdialog.ui to improve layout of form, improved help text

    1 parent 29995d5 commit 25b924030f8112c30ac2b8ac6882bb132bf73279 @wrapperband wrapperband committed on 22 Jun 2016

    The 0.9.6.1 changes have been pulled into master and is now released,

    0.9.6.2 is the new maintenance version for 0.9.x series.although there are no fork issues, so it could be used to release an emergency fix version if necessary.

    List of “issues” - FTC contact / contributer - status

    Status key - ToDo, review(ing), work(ing on), complete(d)

    1. Review 0.8.7 - FTC commits to 0.9 version - @Aciddude review / work
    2. OSX - MingW - compilation documentation - @wrapper @Aciddude review / work
    3. bitcoinrpc.cpp / rpcnett.cpp / review - @Wellenreiter, @Aciddude, @wrapper work
    4. Issues with 0.8.7 backward compatibility. @Lizhi +
    5. Bignum.h
    6. OpenSSL
    7. pchMessageStart
    8. getwork
    9. Opennames
    10. Chinese Language files need update.

    Cherry Pick List : Create the where to cherry pick from list

    Neoscrypt.cpp requires update - Ghostlander


  • Moderators

    Not sure where to log this, maybe github.

    Somewhere in the code, it still says the Copyright is 2013-2016

    You can see this in the file properties on windows when you build Feathercoin-QT v0.9.6

    Feathercoin-QT v0.9.6 Properties

    This should be changed to 2017…to reflect the new year 🙂


  • Moderators

    Mhh, I thought I had changed the end year to 2017

    best is to log an issue on github, so we can track and solve it, even if you solve it yourself 😉


  • Moderators


  • Moderators

    @Wellenreiter said in [Dev] Feathercoin 0.9.7-dev * Bug fix & issues notes for 0.11:

    Mhh, I thought I had changed the end year to 2017

    best is to log an issue on github, so we can track and solve it, even if you solve it yourself 😉

    Github issue created. When I get some time I’m gonna go and change it, I can test with my windows build environment.

    will send my PR to 0.9.7-dev



  • QT Copyright is in src\qt\res\feathercoin-qt-res.rc



  • src\clientversion.h


  • Moderators

    @lizhi said in [Dev] Feathercoin 0.9.6.1 * Bug fix & issues notes for 0.11:

    src\clientversion.h

    That definition is used only, if there is no bitcoin-config.h, which in turn is created/updated by the autoconfig scripr, so the definitions in src\clientversion.h are never used.


  • Moderators

    @Wellenreiter said in [Dev] Feathercoin 0.9.6.1 * Bug fix & issues notes for 0.11:

    @lizhi said in [Dev] Feathercoin 0.9.6.1 * Bug fix & issues notes for 0.11:

    src\clientversion.h

    That definition is used only, if there is no bitcoin-config.h, which in turn is created/updated by the autoconfig scripr, so the definitions in src\clientversion.h are never used.

    I think Lizhi might be right. Also we have a slight problem.
    https://github.com/FeatherCoin/Feathercoin/blob/0.9.6/src/feathercoind-res.rc

    #include <windows.h>             // needed for VERSIONINFO
    #include "clientversion.h"       // holds the needed client version information
    

    https://github.com/FeatherCoin/Feathercoin/blob/0.9.6/src/clientversion.h

    // These need to be macros, as version.cpp's and bitcoin-qt.rc's voodoo requires it
    #define CLIENT_VERSION_MAJOR       0
    #define CLIENT_VERSION_MINOR       9
    #define CLIENT_VERSION_REVISION    3
    #define CLIENT_VERSION_BUILD       99
    
    // Set to true for release, false for prerelease or test build
    #define CLIENT_VERSION_IS_RELEASE  false
    
    // Copyright year (2009-this)
    // Todo: update this when changing our copyright comments in the source
    #define COPYRIGHT_YEAR 2016
    
    

    and my release Feathercoin-qt.exe
    Wrong Version

    Look at the version, it’s wrong. and matches what Lizhi was saying.


  • Moderators

    confirmed, changing the details in
    https://github.com/FeatherCoin/Feathercoin/blob/0.9.6/src/clientversion.h

    Now the right version and copyright date appear. Good find @lizhi !!

    alt text


  • Moderators

    @aciddude

    also read lines 1 -5 of that file:

    #ifndef CLIENTVERSION_H
    #define CLIENTVERSION_H
    
    #if defined(HAVE_CONFIG_H)
    //
    
    // These need to be macros, as version.cpp's and bitcoin-qt.rc's voodoo requires it
    #define CLIENT_VERSION_MAJOR       0
    #define CLIENT_VERSION_MINOR       9
    #define CLIENT_VERSION_REVISION    3
    #define CLIENT_VERSION_BUILD       99
    

    There are some lines missing:

    #if defined(HAVE_CONFIG_H)
    #include "bitcoin-config.h" 
    #else
    
    .....
    

    is the right syntax


  • Moderators

    @Wellenreiter said in [Dev] Feathercoin 0.9.6.1 * Bug fix & issues notes for 0.11:

    There are some lines missing:

    #if defined(HAVE_CONFIG_H)
    #include "bitcoin-config.h" 
    #else
    
    .....
    

    is the right syntax

    will it need to be changed in the .rc files as well?

    i think there’s three for feathercoind, cli, qt.exe

    https://github.com/FeatherCoin/Feathercoin/blob/0.9.6/src/feathercoind-res.rc

    #include <windows.h>             // needed for VERSIONINFO
    #include "clientversion.h"       // holds the needed client version information
    
    #define VER_PRODUCTVERSION     CLIENT_VERSION_MAJOR,CLIENT_VERSION_MINOR,CLIENT_VERSION_REVISION,CLIENT_VERSION_BUILD
    #define VER_PRODUCTVERSION_STR STRINGIZE(CLIENT_VERSION_MAJOR) "." STRINGIZE(CLIENT_VERSION_MINOR) "." STRINGIZE(CLIENT_VERSION_REVISION) "." STRINGIZE(CLIENT_VERSION_BUILD)
    #define VER_FILEVERSION        VER_PRODUCTVERSION
    #define VER_FILEVERSION_STR    VER_PRODUCTVERSION_STR
    #define COPYRIGHT_STR          "Feathercoin developers 2013-" STRINGIZE(COPYRIGHT_YEAR) ", The Bitcoin developers 2009-" STRINGIZE(COPYRIGHT_YEAR)   
    

  • Moderators

    according to the piece of code you copied it should be ok.
    If clientversion.h is patched in the qt-directory, it uses the values defined by the confiugure script and we only have one place to change the version numbers


  • Moderators

    @Wellenreiter and I have been working on the sendAlert call which is used to send alerts across the Feathercoin Network.

    I Believe we’ve solved this. Wellenreiter was able to send an alert over the TestNet and he received it on his node.

    There was an issue with one of the blocks on the testnet so that’s just being fixed…one that’s done I should hopefully be able to connect to the TestNet Node Wellenreiter set up and receive his test message.

    Then we can apply the same patch to prod. 🙂


  • Moderators

    Just a note to double check FTC code for this issue LTC #293 - List of FTC custom settings?

    https://github.com/litecoin-project/litecoin/blob/master/src/main.cpp#L4161

    main.cpp nCheckDepth #293

    In the code it says
    nCheckDepth = 1000000000; // suffices until the year 19000

    But Litecoin is 4x faster then Bitcoin.
    The note should say “until the year 4750”

    or should the nCheckDepth be changed into 4000000000 s

    https://github.com/litecoin-project/litecoin/issues/293#issuecomment-285490529


  • Moderators

    Release of New Feathercoin Wallet version 0.9.6.1

    @Wellenreiter has started to lock down the code for the release of version 0.9.6.1.

    Reviewed outstanding document updates and policy.

    The FTC software settings, naming conventions and software development fork procedure showed that a lot of work is need to up keep Feathercoin name interface changes. Some changes such as comments, or where Feathercoin operates the same as Bitcoin core are unnecessary. How to handle files in the future for cherry pick or updates from head were discussed.

     /doc
     /doc/release-notes
    

    ToDo :

    • Include Feathercoin 0.9.6.1 release notes

    • Create Beta test builds / Window / MAC etc

    • Review - update Wallet guide, MultiSig is an important, but complex update, needs better screen shots / help text.
      https://github.com/wrapperband/FeathercoinWalletGuide#multisig-button
      * Review / consider - Include 5, 7 name Multisignature addresses i.e do further update

    * Multisig: A beginner’s guide
    https://99bitcoins.com/multisig-a-beginners-guide/

    • Note : 0.9.6.1 will be a long term version, compatible as a wallet with 0.11. The most usefull cases for Multisig, once you have got over the learning curve, is for more names, and say 3 out of 5, so there is redundancy for fund handling or other open source management / DAO criteria.

    • Review wither to including Feathercoin Wallet Guide in release


  • Moderators

    @wrapper said in [Dev] Feathercoin 0.9.6.1 * Bug fix & issues notes for 0.11:

    Review wither to including Feathercoin Wallet Guide in release

    I’d prefer to just include a link to the online guilde in the wallet-GUI. it gives more flexibility and enables us to update/enhance the guide without releasing new versions of the Wallet


  • Moderators

    ##- Please type your reply above this line -##
    Email to shapeshift

    Jun 28, 2:54 AM MDT

    Feathercoin has spent considerable bounties to include shapeshift, for over one year. We understood FTC was to be reinstated after you had some problems.
    The next release is to be finalised within 5 days and it will then be about 6 months before it can be reinstated.

    Wrapper Admin FTC forum/dev

    Hello from the ShapeShift.io Support Team!

    Urgent Note: https://www.facebook.com/notes/shapeshiftio/note-on-support-requests-for-the-weekend-of-june-16-2017/1321495071261253/

    Your request (64102) has been received and is being reviewed by our team. Please, only send in one ticket per issue - this is important to speed up your resolution time.

    To ensure you get the best support possible please be sure you have included the ShapeShift deposit address and the TXID (or Hash) of your deposit(s).
    ShapeShift Support is available 7 days a week from 11am-7pm EST. Support is available, but limited outside of those hours. Your request will be resolved within 3-4 days.


  • Regular Member

    @wrapper said in [Dev] Feathercoin 0.9.6.1 * Bug fix & issues notes for 0.11:

    ##- Please type your reply above this line -##
    Email to shapeshift

    Jun 28, 2:54 AM MDT

    Feathercoin has spent considerable bounties to include shapeshift, for over one year. We understood FTC was to be reinstated after you had some problems.
    The next release is to be finalised within 5 days and it will then be about 6 months before it can be reinstated.

    Wrapper Admin FTC forum/dev

    Hello from the ShapeShift.io Support Team!

    Urgent Note: https://www.facebook.com/notes/shapeshiftio/note-on-support-requests-for-the-weekend-of-june-16-2017/1321495071261253/

    Your request (64102) has been received and is being reviewed by our team. Please, only send in one ticket per issue - this is important to speed up your resolution time.

    To ensure you get the best support possible please be sure you have included the ShapeShift deposit address and the TXID (or Hash) of your deposit(s).
    ShapeShift Support is available 7 days a week from 11am-7pm EST. Support is available, but limited outside of those hours. Your request will be resolved within 3-4 days.

    I also sent SHapeShift an email a few weeks ago about adding Feathercoin back. I didnt get a direct response yet.


  • Moderators

    Incorrect setting of minimum fee #181
    https://github.com/FeatherCoin/Feathercoin/issues/181

    In at least one place (in main.cpp) - FTC custom settings are required because of block time and reward scaling of Bitcoin parameters.

    Further, whilst reviewing an emergency change, comparison should be made with the Litecoin setting, to ensure the further scaling of coin reward is reflected in the minimum fees.

    This is very important as it is currently mode of failure of Bitcoin and we will be stuck with high fees till the next release.

    v0.8 https://github.com/FeatherCoin/Feathercoin/blob/master-0.8/src/main.cpp
    /** Fees smaller than this (in satoshi) are considered zero fee (for transaction creation) /
    int64 CTransaction::nMinTxFee = 2000000;
    /* Fees smaller than this (in satoshi) are considered zero fee (for relaying) */
    int64 CTransaction::nMinRelayTxFee = 2000000;

    v0.9 https://github.com/FeatherCoin/Feathercoin/blob/0.9.6/src/main.cpp
    /** Fees smaller than this (in satoshi) are considered zero fee (for transaction creation) /
    int64_t CTransaction::nMinTxFee = 1000000; // Override with -mintxfee
    /* Fees smaller than this (in satoshi) are considered zero fee (for relaying and mining) */
    int64_t CTransaction::nMinRelayTxFee = 1000000;

    In 0.8 but not 0.9 main.cpp

    // Feathercoin
    // To limit dust spam, add nBaseFee for each output less than DUST_SOFT_LIMIT
    BOOST_FOREACH(const CTxOut& txout, vout)
    if (txout.nValue < DUST_SOFT_LIMIT)
    nMinFee += nBaseFee;

    // Raise the price as the block approaches full
    

    if (nBlockSize != 1 && nNewBlockSize >= MAX_BLOCK_SIZE_GEN/2)