BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[eternalenvoy]

After this incident, I know how to confirm the blockchain status now.

Thanks both. 

[Mart1250]

When it's time to upgrade to the Evo version, do I need to copy my wallet file from classic to the evo folder? (I'm a miner) Or how do I access my funds, it's a fork right, or not?

[togoshigekata]

Dash Core v0.14 Released
https://github.com/dashpay/dash/releases/tag/v0.14.0.0

An Introduction to Dash Platform, DAPI, and Drive
https://blog.dash.org/an-introduction-to-dash-platform-dapi-and-drive-9d080d6e89c9

[togoshigekata]

Happy Bitcoin Pizza Day!
https://bitcointalk.org/index.php?topic=137.0
https://bitcointalk.org/index.php?topic=137.msg1195#msg1195

[bible_pay]

When it's time to upgrade to the Evo version, do I need to copy my wallet file from classic to the evo folder? (I'm a miner) Or how do I access my funds, it's a fork right, or not?

Sorry for the delay, lots of BiblePay things going on.

So just to be *extra* careful during this upgrade, I moved the BiblePay data directory for Evolution to a different location.  You might ask why; with Evo we have HD wallet support and yes Dash does have an upgrade from legacy wallets (but during testing I ran into a couple errors and that made me nervous for one) - in addition, the block format is changing and Evo adds an extra database file (Evo supports both compact and non compact blocks).  Just to be safe I decided its less risky for us to ask the users to just copy their wallet.dat to the new location.  Technically, its a good exercise to always have an extra copy of wallet.dat anyway (and I encourage users to keep an offsite copy of your wallet.dat on a flash drive).  Maybe someday, we will have a nice hardware wallet and a branded flash drive .

For now, let me give you the high level technical solution; and when we are closer to launching Ill make a wiki page for Getting Started that includes more details, and our ability to join POG at the same time.

Migrating To Evolution from Classic:

Old application data directory:  %appdata%\biblepaycore  (or ~/.biblepaycore)
New application data directory:  %appdata%\biblepayevolution (or ~/.biblepayevolution)

Steps to migrate:

Copy wallet.dat from the old place to the new place then boot Evo.


Note:  You can let the blocks sync manually to ensure your governance files get updated correctly.


Once things settle down you can delete your old:
~/.biblepaycore -r
~/biblepay -r

Files to regain the disk space.


=-=-=-=-=-=-=-=-=-=-=-=-=-
Regarding the Hard Fork question at block 123,200:

Yes, after block 123,199 biblepay-classic ceases to work correctly and forks at that point.  So it is recommended to upgrade to the mandatory version by block 123,000 (this is the block height where our May governance superblock is paid).

[Mart1250]

Thanks for your explanation Rob.   I understand what I need to do now, but don't know what you mean with governance files to be honest.


Best regards,

Mart

[bible_pay]

Thanks for your explanation Rob.   I understand what I need to do now, but don't know what you mean with governance files to be honest.


Best regards,

Mart

Basically, the governance system caches sanc payments and gobjects and votes in a few different governance files when the client shuts down.

So, if we asked people to copy the classic blocks files, (IE to sync from where they left off), they could miss some governance objects and files etc (and it would make this kind of complicated), so Ill probably ask them to just sync from zero when we explain the upgrade to them (for the Evo launch).

I'll modify the wiki page asap.

[Mart1250]

Thanks for your explanation Rob.   I understand what I need to do now, but don't know what you mean with governance files to be honest.


Best regards,

Mart

Basically, the governance system caches sanc payments and gobjects and votes in a few different governance files when the client shuts down.

So, if we asked people to copy the classic blocks files, (IE to sync from where they left off), they could miss some governance objects and files etc (and it would make this kind of complicated), so Ill probably ask them to just sync from zero when we explain the upgrade to them (for the Evo launch).

I'll modify the wiki page asap.

Thanks, now I understand. Syncing from zero seems indeed the best option and it's easier for users than messing with those files.

Regards,

Mart

[MIP]

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.

[bible_pay]

So let me know if we still have any outstanding c-cex issues; 6 days left before the shut down.

[pkman999]

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?


https://imgur.com/zCHu0PH

[bible_pay]

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?

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!

[pkman999]

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?

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?

[bible_pay]

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?

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.

[capulo]

So let me know if we still have any outstanding c-cex issues; 6 days left before the shut down.

i'm still locked... nothing changed

[bible_pay]

So let me know if we still have any outstanding c-cex issues; 6 days left before the shut down.

i'm still locked... nothing changed

Capulo was refunded.

[bible_pay]

Slovakia, you are still banned as you continue to spread FUD and fabricate lies without any backing and that is bad character.

[bible_pay]

Just to remind you all:  No one has ever found a scam nor ever will with BiblePay or me... Post here if you think there has *ever* been a prior issue with anything.

We've gone the extra mile in every respect to ensure our integrity is still 100%.  God's children have received the net positive benefit in every transaction.

Any transaction that was short was always rounded up by me, and any small benefit I ever received I gave back to the orphans through donations to the foundation.

[bible_pay]

700 Block Countdown until Evo is launched!

- https://biblepay.org (WebSite) has been updated with :  Evolution downloads and new Sanc lockup req's
- CoinExchange.IO has upgraded to Evo
- Togo has notified CryptoBridge
- C-CEX will be closing on June 1st
- SouthXChange and GIN have been notified to upgrade
- Togo is delegating the Reddit update
- Rob will be posting Evo launch information soon (as we are cognizent about the timing of this, as we don't want sancs to upgrade early)
- BitcoinTalk OP post has been updated
- Rob will update pool.biblepay.org
- Purepool is working on the mining changes for Evo

If anyone has any suggestions for an edit, or currently see any misinformation (for example Sanc lockup requirements) on any of our sites, or feels there is something that we need to communicate to one of our third parties or social channels, please post here so we can take care of that immediately.

[capulo]

what kind(s) of mining will be in evo?
also some guides how to switch to evo (if something else than wallet upgrade) will be great