Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE BLURT!
Sort Order:  
  • Trending
    • [-]
      ·  4 years ago  ·  

    Thank you frog

    62.62 BLURT
    • Past Payouts 62.62 BLURT
    • - Author 31.31 BP
    • - Curators 31.31 BP
    2 votes    $0.18
    [-]
      ·  4 years ago  ·  

    You*re always welcone. My Raspberry P4 will gladly arrive tomorrow. I have to thank you for your think tank.

    0.00 BLURT
      $0.00
      [-]
        ·  4 years ago  ·  

      I only have one piece of bad news on that which is that I hit an additional snag with blurt on Pi.

      The FC library does not seem to be compatible with arm. I may be able to backport from EOS however.

      36.19 BLURT
      • Past Payouts 36.19 BLURT
      • - Author 18.09 BP
      • - Curators 18.09 BP
      1 votes      $0.10
      [-]
        ·  4 years ago  ·  

      I'm pretty sure you will manage to solve the problems step by step. It should be able to setup a blockchain like Blurt pretty new as well. Without all this old fuzzy Graphene stuff it would be a better option for future.

      I installed 64-bit Raspbian OS Beta on my P4-8GB. Is it okay or should I take another OS?

      0.00 BLURT
        $0.00
        [-]
          ·  4 years ago  ·  

        That OS is okay. But in fact I am packaging the chain with the OS so that you don't need to install and configure because that's a pain.

        8.32 BLURT
        • Past Payouts 8.32 BLURT
        • - Author 4.16 BP
        • - Curators 4.16 BP
        1 votes        $0.02
        [-]
          ·  4 years ago  ·   (edited)

        Where do I get this image? I guess it is Megadrive with SOS, ready to be burned on a SD.
        Can't find it, I only find SOS.

        0.00 BLURT
          $0.00
          [-]
            ·  4 years ago  ·  

          You're right.

          Let me see if my work from last night is finished cooking

          41.87 BLURT
          • Past Payouts 41.87 BLURT
          • - Author 20.93 BP
          • - Curators 20.93 BP
          1 votes          $0.12
          [-]
            ·  4 years ago  ·   (edited)

          You remember the tree commands, you wrote to me in an answer before?

          docker run --net=host faddat/blurt-pi /usr/bin/blurt --data-dir /blurtd

          This setup doesn't work on Raspian 64 bit. The container doesn't start. only "dockerd" was running without starting a container. A kind of download with 27 packages where pulled but no start of chain followed.

          After all I tried to start the node by a command line, I saw in one of you movies:

          docker run --net=host faddat/blurt-pi /usr/bin/blurt --data-dir

          It's nearly the same instruction, but without the "/blurtd" at the end. It worked! Now I saw the container's start and then the Blockchain came to download and started to complete itself, block by block, very fast, line by line until hardfork 1. Then it continued but very, very, very slow. The pattern of screen messages changed totally from one line per block to messages like the following pattern:

          {"new_block":{"previous":"000452ff33605382d2caf1c8a67261ccc3af4edd","timestamp":"2020-07-14T02:24:57","witness":"empato365","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"20c60fbb7458f2c6561b2e44ddd9c87a3088b8670a141e9672dbd297f7283f6e344b0f3cd50071b1ecad192ccf1deedd84fa7eea1b1a2bcc187d336951e16bc71b","transactions":[]}}   
database.cpp:759 operator()
3411634ms p2p_plugin.cpp:229            handle_block         ] Error when pushing block:
10 assert_exception: Assert Exception
item->num > std::max<int64_t>( 0, int64_t(_head->num) - (_max_size) ): attempting to push a block that is too old
    {"item->num":284433,"head":284790,"max_size":20}
    fork_database.cpp:57 _push_block

    {}
    database.cpp:871 _push_block

          Six hours later, the downloads are on timestamp September 07 "already", and the pattern of messages changed again. Now the blocks are shown with any transaction inside, and still such slow as after hardfork 1.

          What do you recommend? Should I let it go on? My opinion is to stop it and wait for your Megadrive image. But I have no experience with building nodes. Maybe this described behaviour is quite normal and it takes two or three days to complete the node. What do you recommend?

          0.00 BLURT
            $0.00
            Show 2 more replies