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

    [Dev] Change to dedicated pcmessagestart string

    Technical Development
    3
    4
    2378
    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.
    • lizhi
      lizhi last edited by wrapper

      Currently FTC is sharing the pcmessagestart string with litecoin and other coins. FTC should generate an alternate pcmessagestart.

      Issues 94 https://github.com/FeatherCoin/Feathercoin/issues/94

      Now I set new pchMessageStart, They are :

      0xfe 0x46 0x54 0x43

      Updated for 0.11.2 https://github.com/FeatherCoin/Feathercoin/commit/80e605e62fd5644cfa1e9e82f5a7fd6ab1433896

      pchMessageStart

      Updated for 0.11.2

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

        Thanks for your work on pcmessagestart string Lizhi, +10 kudos …

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

          @lizhi , if this activates, will it require a hardfork ?

          Can any one answer this.

          if the pchMessageStart is changed, does this mean when we are using things like FTCSeeder, we wont see other random coins ?

          • 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 1
          • lizhi
            lizhi last edited by

            I think that don’t caused a hardfork , it compatible old protocol.

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