Forum Home
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Feathercoin 0.8.5

    Technical Development
    14
    70
    36269
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Bushstar
      Bushstar last edited by

      [quote name=“wrapper0feather” post=“33949” timestamp=“1384349764”]
      Re: QR codes. not on linux source build

      I have tested QR codes with my Linux QT build of v0.6.4.4

      The \ receive coins \ show QR – no QR image is shown.
      [/quote]

      Have you built another client like Litecoin to see if the QR codes are working there?

      I just want to make sure that it is the client and not your computer.

      [quote author=Kevlar link=topic=4155.msg33965#msg33965 date=1384365035]
      [quote author=Bushstar link=topic=4155.msg33934#msg33934 date=1384332238]
      The client can show QR codes but only on Windows! I have not compiled this into the Mac client yet, sorry :(

      Poor Mac users, they pay twice the price for a computer and then get forgotten half the time. The Mac client does not handle the Feathercoin URLs either. I believe an installer is required for that to make the client responsible for handling the Feathercoin URLs. If anyone is familiar with this then please let me know.
      [/quote]

      Yeah, I’ve done it plenty of times in the past. Used to make VPN clients that would launch and get their credentials from a protocol handler on Mac, Linux, and Windows.

      Everything you need to know is here. Pretty straight forward. Don’t need an installer, you just need to run the client once.

      [url=http://hublog.hubmed.org/archives/001154.html]http://hublog.hubmed.org/archives/001154.html[/url]

      I don’t have a mac any more though, so some brave soul who does will have to take the next part on.
      [/quote]

      Thanks Kevlar.

      Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

      1 Reply Last reply Reply Quote 0
      • Wellenreiter
        Wellenreiter Moderators last edited by

        When I go to
        https://github.com/FeatherCoin/Feathercoin-0.8.5

        Github says ‘not found’???

        Feathercoin development donation address: 6p8u3wtct7uxRGmvWr2xvPxqRzbpbcd82A
        Openpgp key: 0x385C34E77F0D74D7 (at keyserver.ubuntu.com)/fingerprint: C7B4 E9EA 17E1 3D12 07AB 1FDB 385C 34E7 7F0D 74D7

        1 Reply Last reply Reply Quote 0
        • Bushstar
          Bushstar last edited by

          [quote name=“Wellenreiter” post=“34150” timestamp=“1384425497”]
          When I go to
          https://github.com/FeatherCoin/Feathercoin-0.8.5

          Github says ‘not found’???
          [/quote]

          You need to login as Wellenreiter for it to appear.

          Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

          1 Reply Last reply Reply Quote 0
          • lizhi
            lizhi last edited by

            Feathercoin 0.8.5 , When released ?

            1 Reply Last reply Reply Quote 0
            • Wellenreiter
              Wellenreiter Moderators last edited by

              [quote name=“Bushstar” post=“34155” timestamp=“1384428509”]
              [quote author=Wellenreiter link=topic=4155.msg34150#msg34150 date=1384425497]
              When I go to
              https://github.com/FeatherCoin/Feathercoin-0.8.5

              Github says ‘not found’???
              [/quote]

              You need to login as Wellenreiter for it to appear.
              [/quote]

              ops!!!

              :-[ my fault!!!

              My login at github is Wellenreiter01, not Wellenreiter, as Wellenreiter was occupied when I signed up.

              Sorry !!! :'(

              Feathercoin development donation address: 6p8u3wtct7uxRGmvWr2xvPxqRzbpbcd82A
              Openpgp key: 0x385C34E77F0D74D7 (at keyserver.ubuntu.com)/fingerprint: C7B4 E9EA 17E1 3D12 07AB 1FDB 385C 34E7 7F0D 74D7

              1 Reply Last reply Reply Quote 0
              • lizhi
                lizhi last edited by

                404 Page not found. :(

                1 Reply Last reply Reply Quote 0
                • wrapper
                  wrapper Moderators last edited by

                  [quote]
                  Bushstar
                  Have you built another client like Litecoin to see if the QR codes are working there?
                  I just want to make sure that it is the client and not your computer. [/quote]

                  Litecoin v0.8.5.1-8-gffd7439-beta

                  Linux (13.10) compiled versions from source -

                  Litecoin -Doesn’t have the option for QR codes, right click in receive coins.

                  whereas Feathercoin 0.6.4.4 QR code menu option is there on right click, but nothing happens.

                  1 Reply Last reply Reply Quote 0
                  • Bushstar
                    Bushstar last edited by

                    Thanks for that Wrapper.

                    Wellenreiter and Lizhi I have added both of you again. Apologies Lizhi, I thought I had added you before.

                    The client compiles but is still broken by the changes to the key so is currently no good. The commit that broke compatibility is linked in below.

                    https://github.com/bitcoin/bitcoin/commit/dfa23b94c24aae6466152fccbe896ba5dc0e97b4

                    Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

                    1 Reply Last reply Reply Quote 0
                    • G
                      groll Regular Member last edited by

                      can you add me to the repository. user: groll

                      I will take a look but as usual my time is limited.

                      1 Reply Last reply Reply Quote 0
                      • wrapper
                        wrapper Moderators last edited by

                        Hi Groll / Bush,

                        Re: Crowd development.

                        If you can think of any way I can help, test compiling, looking into some function / patch you need more info on / stuck on (history) or some such. Shout out.

                        1 Reply Last reply Reply Quote 0
                        • Bushstar
                          Bushstar last edited by

                          groll, I have now added you to the repo. The commit that broke ACP and CAlert is as follows.

                          https://github.com/bitcoin/bitcoin/commit/dfa23b94c24aae6466152fccbe896ba5dc0e97b4

                          This made way for HD Wallets. We could simply reverse the commit but I would say that we make ACP and CAlert compatible with the changes to OpenSSL and include HD Wallets in this release.

                          Before the client downloads the block chain it appears fine.

                          [quote]feathercoind getinfo
                          {
                          “version” : 80500,
                          “protocolversion” : 60002,
                          “walletversion” : 60000,
                          “balance” : 31.61469999,
                          “blocks” : 111537,
                          “timeoffset” : 0,
                          “connections” : 0,
                          “proxy” : “”,
                          “difficulty” : 119.77041035,
                          “testnet” : false,
                          “keypoololdest” : 1381493269,
                          “keypoolsize” : 94,
                          “paytxfee” : 0.00000000,
                          “mininput” : 0.00010000,
                          “unlocked_until” : 0,
                          “errors” : “”
                          }[/quote]

                          makekeypair appears to work.

                          [quote]feathercoind makekeypair
                          {
                          “PublicKey” : “04e4f418ea6c6ac443e98f3c7b5d2bd22ce8816288bf9c50e54e6142d4991
                          aa176329dcec83391f6c3c6feda62b79353ed656af35c56c3182221a0437c1fe8766f”,
                          “PrivateKey” : “5nvuGK5APZXj5jjZXtRpW5bSasPqLn6fYazQLbTxTo8EphB2kr6”
                          }[/quote]

                          However when the blockchain starts downloading we get this assert error.

                          [quote]Assertion failed: mapBlockIndex.count(hashSyncCheckpoint), file checkpointsync.c
                          pp, line 223[/quote]

                          [quote name=“wrapper0feather” post=“34932” timestamp=“1384852938”]
                          Hi Groll / Bush,

                          Re: Crowd development.

                          If you can think of any way I can help, test compiling, looking into some function / patch you need more info on / stuck on (history) or some such. Shout out.
                          [/quote]

                          Thanks Wrapper. There should be a whole lot of testing soon. Right now the client compiles but crashes when the blockchain starts downloading with the following assert error. Be careful with this release as the wallets are not backwards compatible afterwards. Make sure you have a backup first.

                          Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

                          1 Reply Last reply Reply Quote 0
                          • wrapper
                            wrapper Moderators last edited by

                            Hierarchical Deterministic Wallets (11-2-2012)

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

                            The Bitcoin reference client uses randomly generated keys. In order to avoid the necessity for a backup after every transaction, (by default) 100 keys are cached in a pool of reserve keys.

                            Deterministic wallets do not require such frequent backups, and elliptic curve mathematics permit schemes where one can calculate the public keys without revealing the private keys. This permits for example a webshop business to let its webserver generate fresh addresses (public key hashes) for each order or for each customer.

                            1 Reply Last reply Reply Quote 0
                            • wrapper
                              wrapper Moderators last edited by

                              More background, Litecoin Devs talk of support for BIP32 and HD wallets. Oct 2013

                              https://forum.litecoin.net/index.php/topic,6466.msg50141.html#msg50141

                              1 Reply Last reply Reply Quote 0
                              • K
                                Kevlar Spammer last edited by

                                [quote name=“Bushstar” post=“34947” timestamp=“1384863075”]
                                groll, I have now added you to the repo. The commit that broke ACP and CAlert is as follows.

                                https://github.com/bitcoin/bitcoin/commit/dfa23b94c24aae6466152fccbe896ba5dc0e97b4

                                This made way for HD Wallets. We could simply reverse the commit but I would say that we make ACP and CAlert compatible with the changes to OpenSSL and include HD Wallets in this release.

                                Before the client downloads the block chain it appears fine.

                                [quote]feathercoind getinfo
                                {
                                “version” : 80500,
                                “protocolversion” : 60002,
                                “walletversion” : 60000,
                                “balance” : 31.61469999,
                                “blocks” : 111537,
                                “timeoffset” : 0,
                                “connections” : 0,
                                “proxy” : “”,
                                “difficulty” : 119.77041035,
                                “testnet” : false,
                                “keypoololdest” : 1381493269,
                                “keypoolsize” : 94,
                                “paytxfee” : 0.00000000,
                                “mininput” : 0.00010000,
                                “unlocked_until” : 0,
                                “errors” : “”
                                }[/quote]

                                makekeypair appears to work.

                                [quote]feathercoind makekeypair
                                {
                                “PublicKey” : “04e4f418ea6c6ac443e98f3c7b5d2bd22ce8816288bf9c50e54e6142d4991
                                aa176329dcec83391f6c3c6feda62b79353ed656af35c56c3182221a0437c1fe8766f”,
                                “PrivateKey” : “5nvuGK5APZXj5jjZXtRpW5bSasPqLn6fYazQLbTxTo8EphB2kr6”
                                }[/quote]

                                However when the blockchain starts downloading we get this assert error.

                                [quote]Assertion failed: mapBlockIndex.count(hashSyncCheckpoint), file checkpointsync.c
                                pp, line 223[/quote]

                                [quote author=wrapper0feather link=topic=4155.msg34932#msg34932 date=1384852938]
                                Hi Groll / Bush,

                                Re: Crowd development.

                                If you can think of any way I can help, test compiling, looking into some function / patch you need more info on / stuck on (history) or some such. Shout out.
                                [/quote]

                                Thanks Wrapper. There should be a whole lot of testing soon. Right now the client compiles but crashes when the blockchain starts downloading with the following assert error. Be careful with this release as the wallets are not backwards compatible afterwards. Make sure you have a backup first.
                                [/quote]

                                This seems like an easy one to fix.

                                The line of code in question is:
                                [quote]
                                assert(mapBlockIndex.count(hashSyncCheckpoint));
                                [/quote]

                                So stick a breakpoint on that line and examine your call stack. What’s calling it? What’s hashSyncCheckpoint value and where is it coming from? Put another breakpoint in mapBlockIndex.count (where is that defined?). What is the expected value? More details please!

                                Also, your header exclusion compiler macro name is funny: #ifndef PRIMECOIN_CHECKPOINTSYNC_H #define PRIMECOIN_CHECKPOINTSYNC_H

                                1 Reply Last reply Reply Quote 0
                                • T
                                  Tuck Fheman last edited by

                                  [quote name=“Kevlar” post=“35009” timestamp=“1384887430”]
                                  This seems like an easy one to fix.

                                  The line of code in question is:
                                  [quote]
                                  assert(mapBlockIndex.count(hashSyncCheckpoint));
                                  [/quote]

                                  So stick a breakpoint on that line and examine your call stack. What’s calling it? What’s hashSyncCheckpoint value and where is it coming from? Put another breakpoint in mapBlockIndex.count (where is that defined?). What is the expected value? More details please!

                                  Also, your header exclusion compiler macro name is funny: #ifndef PRIMECOIN_CHECKPOINTSYNC_H #define PRIMECOIN_CHECKPOINTSYNC_H
                                  [/quote]

                                  [url=http://youtu.be/tlPQD04tn88]http://youtu.be/tlPQD04tn88[/url]

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mnstrcck last edited by

                                    Tuck, that is so against the rules for the forum, but I think we need to keep it. It’s hilariously appropriate.

                                    Kevlar - I am giving you a high-five across the huge land-mass between us.

                                    1 Reply Last reply Reply Quote 0
                                    • Bushstar
                                      Bushstar last edited by

                                      I left PRIMECOIN_CHECKPOINTSYNC_H in there as the code for this is from Primecoin. I do not mind leaving references to Primecoin as a nod to Sunny lest we forget his contributions.

                                      However you can have the honour of renaming it if you like?

                                      Let’s debug.

                                      The function CheckSyncCheckpoint that the assert is in is called from here…
                                      [quote](gdb) info stack
                                      #0 CheckSyncCheckpoint (hashBlock=@0x28f07c, pindexPrev=0x969f168)
                                      at checkpointsync.cpp:223
                                      #1 0x004442f4 in SetBestChain (state=@0x28fa50, pindexNew=0x969f088)
                                      at main.cpp:1980
                                      #2 0x004454fe in ConnectBestBlock (state=@0x28fa50) at main.cpp:1343
                                      #3 0x0042335e in AppInit2 (threadGroup=@0x28fe18) at init.cpp:1068
                                      #4 0x00425627 in AppInit (argc=1, argv=0x4862a40) at init.cpp:228
                                      #5 0x004261a5 in main (argc=1, argv=0x4862a40) at init.cpp:260[/quote]

                                      mapBlockIndex is defined in main.cpp as follows.
                                      [quote]map

                                      Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

                                      1 Reply Last reply Reply Quote 0
                                      • Bushstar
                                        Bushstar last edited by

                                        On Wrapper0feathers suggestion I have created a branch pre-ACP commit which will run. This can be used for testing the client whilst we look at the compatibility between Sunny’s code and 0.8.5.

                                        https://github.com/FeatherCoin/Feathercoin-0.8.5/tree/master-0.8-pre-ACP

                                        Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

                                        1 Reply Last reply Reply Quote 0
                                        • lizhi
                                          lizhi last edited by

                                          Complite 0.8.5 success. Run it ,Need to resynchronization transaction records. ;)

                                          [attachment deleted by admin]

                                          1 Reply Last reply Reply Quote 0
                                          • Bushstar
                                            Bushstar last edited by

                                            I have updated the checkpoint data on both 0.8.5 branches. The non-ACP branch will be deleted eventually but for now it allows us to test.

                                            The data comes from the debug.log as shown below and allows us to enter the correct number of transactions since the last hard coded checkpoint. The number of transactions a day is just an estimated amount taken from our totals transactions and the number of days since launch.

                                            [quote]received block 8c4e02f6c0d20e856fd7e952a147fee30ce145ca6932a284f354924362d2b408
                                            SetBestChain: new best=8c4e02f6c0d20e856fd7e952a147fee30ce145ca6932a284f354924362d2b408 height=41300 log2_work=52.63077 tx=257285 date=2013-06-25 13:26:47 progress=0.036524
                                            ProcessBlock: ACCEPTED[/quote]

                                            Commit is here.

                                            https://github.com/FeatherCoin/Feathercoin-0.8.5/commit/1414528e1bf46d938cc4a7bf05f41c22ee43a797

                                            Donate: 6hf9DF8H67ZEoW9KmPJez6BHh4XPNQSCZz

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post