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

    [Solved] Safe mode: Warning: The network does not appear to fully agree! False alarm

    Feathercoin Discussion
    6
    13
    4360
    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.
    • AcidD
      AcidD Moderators last edited by wrapper

      Anyone seen this before ?

      https://i.snag.gy/fx3JTL.jpg

      • FTC Block Explorer + API @ https://fsight.chain.tips
      • FTC Beer Money: 6x4LEQV88zRnBvZoH6ZNK6SeRxx4KiTyJs
      • FTC bech32 address: fc1q4tclm3cv4v86ez6el76ewmharexfapxhek5a03
      • BTC bech32 address: bc1qk8umuccapuafspk9e5szahvp0detafuzugv4ay

      1 Reply Last reply Reply Quote 2
      • AcidD
        AcidD Moderators last edited by

        I also have this in my feathercoin debug.log

        
        2016-06-30 11:38:08 CheckForkWarningConditions: Warning: Large valid fork found
          forking the chain at height 1277149 (df7599227e348c49fadb6812af71aa8daf31ad251e3fa41ff87877f9fb7cc4ec)
          lasting to height 1277183 (2956a078a7969ba12cbb0dc5abbf86bfec22fe37cadd68ad416ae892708fbb8e).
        Chain state database corruption likely.
        
        
        
        • FTC Block Explorer + API @ https://fsight.chain.tips
        • FTC Beer Money: 6x4LEQV88zRnBvZoH6ZNK6SeRxx4KiTyJs
        • FTC bech32 address: fc1q4tclm3cv4v86ez6el76ewmharexfapxhek5a03
        • BTC bech32 address: bc1qk8umuccapuafspk9e5szahvp0detafuzugv4ay

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

          Thanks for that investigation work @Aciddude as this seems totally consistent with @Ghostlanders warnings of mixing v2 and v4 database types I have posted in Technical developments to fix this issue.

          0.9.3.2 should not have been released untill some issues have been ironed out.

          So it needs to be made backwardly compatible, for this release. It is being used as a minor release but causing major release issue…

          1 Reply Last reply Reply Quote 2
          • AmDD
            AmDD Regular Member last edited by

            Good catch @aciddude

            P2Pool Node: http://104.236.34.9:19327/ 0.5% fee

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

              When we are ready ,I suggest enforce a hard fork for update to 0.9.3.2 or 0.11.2

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

                http://www.ftc-c.com/pack4/block100.png

                1 Reply Last reply Reply Quote 0
                • ghostlander
                  ghostlander Regular Member @lizhi last edited by

                  @lizhi A hard fork just for v4 is a waste of time.

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

                    @Lizhi We can do the fork when we are ready, and we could be ready soon.

                    We need tidy up 0.9.3.2 and create a final 0.9.3.3 - It will not take long …

                    The we can start to check 0.11 is ready for change over.

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

                      @ghostlander Do you want to implement BIP102 with V4 ? This is not difficult, can be completed.

                      ghostlander 1 Reply Last reply Reply Quote 1
                      • ghostlander
                        ghostlander Regular Member @lizhi last edited by

                        @lizhi What makes you think FTC needs 2MB blocks? The current ones are 95%+ empty. Besides FTC is 10x faster than BTC.

                        wrapper 1 Reply Last reply Reply Quote 4
                        • Wellenreiter
                          Wellenreiter Moderators last edited by

                          I agree with @ghostlander :)

                          There is also a drawback, that the block chain will consume even more disk space and synchronization will take more time

                          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
                          • wrapper
                            wrapper Moderators last edited by wrapper

                            There is the possibility to add 2MB when needed? I understan v4 does a lot of pruning and in future the blocks are likely to be compressed

                            If I recall it correctly, Ufasoft’s multi-currency client stores the blockchain in a format of their own in which it gets compressed, so you might switch to it and see a small decrease in the usage of your hard-drive.

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

                              @ghostlander said:

                              @lizhi What makes you think FTC needs 2MB blocks? The current ones are 95%+ empty. Besides FTC is 10x faster than BTC.

                              What we usually do is proportional, what about setting the FTC Block size to 200K? (as a compromise)

                              I agree with @Ghostlander - 2MB block will take longer to transmit and could cause issues building 1 minute block.

                              I will re-iterate that 30% of blocks have transactions currently, this shows interest and use. The idea is to make FTC usefull and that could be for the smart contract features, with unlimited used, even more than money…

                              So I also I agree with @Lizhi that it as advantageous to change now, while that is still manageable.

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