Quote from: pkman999 on May 31, 2019, 08:53:40 AM

Quote from: bible_pay on May 26, 2019, 03:02:26 AM

Quote from: pkman999 on May 26, 2019, 03:00:19 AM

Quote from: bible_pay on May 26, 2019, 02:53:03 AM

Quote from: pkman999 on May 26, 2019, 02:51:14 AM

Quote from: MIP on May 25, 2019, 01:18:12 PM

In case someone wants to test Biblepay Evo RC compiled binaries for ARM32/64 (daemon) devices in Ubuntu 16.04/18.04

ARM32 bit : https://biblepay.org/biblepayd-evo-arm-linux-gnueabihf.tar.gz
ARM64 bit : https://biblepay.org/biblepayd-evo-aarch64-linux-gnu.tar.gz

Any feedback is welcomed.

I used the arm BBP version, i alreay to started the biblepayd that i found the new problem is watchdog tool, it is because the watchdog config still under old file path ~/.biblepaycore.
Any EVO new watchman Version update? Wink

Watchman-on-the-wall is built in the new Evo version and pre-configured to run automatically, so you can delete watchman-classic after block 123,001.

Cheers!

Yes, watchman built in the new evo version but at this moment , i cannot enable the masternode before 123,001 if i used the new evo version?

Please see this post:

https://bitcointalk.org/index.php?topic=2388064.msg51111202#msg51111202

Users are not supposed to upgrade Sancs or controllers to Evo until after block 123,001 passes.

Rob, 122632 blocks now, Can i go to setup the EVO version until 123,001 that to start?
if yes , i will go to upgrade now.

Yes, miners can set up Evo and run it and test it now.

We're just notifying Sancs to not upgrade until after block 123,000 as we really need this superblock to process correctly for our orphan expenses.

I'll be posting info on the wiki guides, the linux compile, the download links, and the timing today.