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

[polipoli]

How do I move the old Sanctuary Wallet and Windows Controller Wallet to the new EVO?

[MIP]

How do I move the old Sanctuary Wallet and Windows Controller Wallet to the new EVO?

Just copy wallet.dat from %appdata%/BiblepayCore to %appdata%/BiblepayEvolution

[MIP]

i think that machines with negative hps does not appear in pool... maybe new version fixing this, but i dont have new binaries yet

BiblePay
1.4.3.2-Leisure Upgrade

Linux binaries available at www.biblepay.org

sha256sum *.tar.gz
a513d937ca5710c190af63e59f6ad0cb44d39c88a60881b00ad74442e5e51f7d  biblepayd-evo-aarch64-linux-gnu.tar.gz
e36ba0605f5378b0dd598d12bf990ae96c34a557b52f012c91720863c91a2153  biblepayd-evo-arm-linux-gnueabihf.tar.gz
d9346aaf571be1961607795a2ab667b2394970043f11442202aa77281de69d39  biblepayd-evo-i686-pc-linux-gnu.tar.gz
792c674c230d82f3562210f6f0a212e31470fc8231570774766d9518a76b6b5a  biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
5c08bb2c1d1ae5ea8451c7f7d2dbddaaa1348191395ec8d7598c9766ea2aa250  biblepay-qt-evo-i686-pc-linux-gnu.tar.gz
42c175551a60bef0faf59470000d07e0f806834f549fdf185dc2c89ab90e339c  biblepay-qt-evo-x86_64-pc-linux-gnu.tar.gz

[eternalenvoy]

i think that machines with negative hps does not appear in pool... maybe new version fixing this, but i dont have new binaries yet

BiblePay
1.4.3.2-Leisure Upgrade

Linux binaries available at www.biblepay.org

sha256sum *.tar.gz
a513d937ca5710c190af63e59f6ad0cb44d39c88a60881b00ad74442e5e51f7d  biblepayd-evo-aarch64-linux-gnu.tar.gz
e36ba0605f5378b0dd598d12bf990ae96c34a557b52f012c91720863c91a2153  biblepayd-evo-arm-linux-gnueabihf.tar.gz
d9346aaf571be1961607795a2ab667b2394970043f11442202aa77281de69d39  biblepayd-evo-i686-pc-linux-gnu.tar.gz
792c674c230d82f3562210f6f0a212e31470fc8231570774766d9518a76b6b5a  biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
5c08bb2c1d1ae5ea8451c7f7d2dbddaaa1348191395ec8d7598c9766ea2aa250  biblepay-qt-evo-i686-pc-linux-gnu.tar.gz
42c175551a60bef0faf59470000d07e0f806834f549fdf185dc2c89ab90e339c  biblepay-qt-evo-x86_64-pc-linux-gnu.tar.gz

After updating the hashps value is amazing...

outputs:
"hashps": 89835431.0839393,

[bible_pay]

i think that machines with negative hps does not appear in pool... maybe new version fixing this, but i dont have new binaries yet

BiblePay
1.4.3.2-Leisure Upgrade

Linux binaries available at www.biblepay.org

sha256sum *.tar.gz
a513d937ca5710c190af63e59f6ad0cb44d39c88a60881b00ad74442e5e51f7d  biblepayd-evo-aarch64-linux-gnu.tar.gz
e36ba0605f5378b0dd598d12bf990ae96c34a557b52f012c91720863c91a2153  biblepayd-evo-arm-linux-gnueabihf.tar.gz
d9346aaf571be1961607795a2ab667b2394970043f11442202aa77281de69d39  biblepayd-evo-i686-pc-linux-gnu.tar.gz
792c674c230d82f3562210f6f0a212e31470fc8231570774766d9518a76b6b5a  biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
5c08bb2c1d1ae5ea8451c7f7d2dbddaaa1348191395ec8d7598c9766ea2aa250  biblepay-qt-evo-i686-pc-linux-gnu.tar.gz
42c175551a60bef0faf59470000d07e0f806834f549fdf185dc2c89ab90e339c  biblepay-qt-evo-x86_64-pc-linux-gnu.tar.gz

After updating the hashps value is amazing...

outputs:
"hashps": 89835431.0839393,

Yeah - I see you and Capulo have very high HPS.
We will probably need to move to MH/S, but lets take a look at everything in the pool and make sure its sane.

[bible_pay]

***** Chainz has updated the Block Explorer to Evo *****


What great service they provide; they appear to be a very good company.

https://chainz.cryptoid.info/bbp/

[bible_pay]

How do I move the old Sanctuary Wallet and Windows Controller Wallet to the new EVO?

Just copy wallet.dat from %appdata%/BiblepayCore to %appdata%/BiblepayEvolution

I wonder if he meant 'migrate BBP' or copy his wallet.

Either way, here is the page:

https://wiki.biblepay.org/Evolution_Upgrade

[bible_pay]

Where do you see sourcelink that is wrong (we now have millions of lines of code and multiple sites and systems)?

www.biblepay.org -> WALLET -> Source

Fixed.  Thanks.

I also have a request :
To add sha256sum of Binaries release (tar files of executables) in github, so I could make sure the released version is untempered by hackers.

I guess it is high time we start releasing the sha256 hash of our binaries on our web site.

We will implement this in our build scripts over the next 14 days.

Ill get back to the forum here with a post when it is working.

[bible_pay]

** Two Ways to get Sha256 Hash of a BiblePay binary **

Method 1:  
Download the binary, and once you know its name you can type it in the browser to get the sha256hash:
For example:  You use the windows 64 bit release, the downloaded filename is : biblepayevo64.exe
URL:  https://biblepay.org/biblepayevo64.hash.htm
(You can bookmark the URL for your platform).

Method 2:
Navigate to the https://biblepay.org website and click on the Top level menu | Wallet | Expand the subsection for your OS | Click on Release Name - Hash

** Two ways to verify the Sha hash per OS **

Method 1 (Linux):
Type sha256sum downloaded_file_name

Method 2 (Windows):
certutil -hashfile downloaded_file_name

NOTE:  We are still deploying this solution, so at this time only the Windows hashes are available.  MIP will update us when the Linux hashes are available.
(These will all automatically update each time we release).

[inblue]

** Two Ways to get Sha256 Hash of a BiblePay binary **

Method 1: 
Download the binary, and once you know its name you can type it in the browser to get the sha256hash:
For example:  You use the windows 64 bit release, the downloaded filename is : biblepayevo64.exe
URL:  https://biblepay.org/biblepayevo64.hash.htm
(You can bookmark the URL for your platform).

Method 2:
Navigate to the https://biblepay.org website and click on the Top level menu | Wallet | Expand the subsection for your OS | Click on Release Name - Hash

** Two ways to verify the Sha hash per OS **

Method 1 (Linux):
Type sha256sum downloaded_file_name

Method 2 (Windows):
certutil -hashfile downloaded_file_name

NOTE:  We are still deploying this solution, so at this time only the Windows hashes are available.  MIP will update us when the Linux hashes are available.
(These will all automatically update each time we release).

Just downloaded from the website and cross checked the sha256 hash, looks good! Also, a tip for users who use 7Zip, you can go to settings and enable "CRC SHA" as a context menu item, so you can check all files easily on right click.

While you're at it, could you perhaps look into signing the exe so that Windows treats it with more confidence and new users don't doubt the validity of the files?

[bible_pay]

Where do you see sourcelink that is wrong (we now have millions of lines of code and multiple sites and systems)?

www.biblepay.org -> WALLET -> Source

Fixed.  Thanks.

I also have a request :
To add sha256sum of Binaries release (tar files of executables) in github, so I could make sure the released version is untempered by hackers.

I guess it is high time we start releasing the sha256 hash of our binaries on our web site.

We will implement this in our build scripts over the next 14 days.

Ill get back to the forum here with a post when it is working.

Just downloaded from the website and cross checked the sha256 hash, looks good!

While you're at it, could you perhaps look into signing the exe so that Windows treats it with more confidence and new users don't doubt the validity of the files?

Yes, MIP and I will discuss a bullet point during our next dev conf call.

[bible_pay]

I see our Average difficulty is about Twice what it was before!  Congratulations.

See pool.biblepay.org | Reports | Difficulty History

[bible_pay]

People who are entering diary entries, could you please be more specific as to who you prayed for and what happened?

For example someone put:  Prayed for Leukemia to leave body

Lets say: Prayed for Joe's Leukemia to leave the body... and he said he felt better
(Or leave the end off if nothing happened)... (Or put and he was healed immediately) if he was healed.

And optionally- add where you did this (at the mall, on the street corner, at WalMart) etc.
And optionally the date.

I just want it to be specific so we can eventually showcase good ones on our overview page.

If you took a video of this please paste the URL at the end.

[Mart1250]

How is it possible that with the same evo version (both 64bit) I have 2 different layouts on 2 different machines?, one at the old layout and one at a new layout. The loading screen is different too, old and new. One machine runs windows 10 and the other runs Windows server 2012 R2 Datacenter Edition. Same installer.

Edit: I even tried copying the exact same installer that I downloaded on my win10 machine to my windows server 2012 machine and it still shows the old layout?

Edit 2: Fixed... I think there are some register entries that are read from the old version. I changed it in the interface menu.

Regards,

Mart

[harrisvan87]

Code:

  {
    "account": "",
    "address": "BHmM5aRfQ1GVbri4t9uyAc2A4bZ6orjnU7",
    "category": "send",
    "amount": -44119.99959200,
    "vout": 1,
    "fee": -0.00040800,
    "confirmations": 0,
    "bcconfirmations": 0,
    "trusted": true,
    "txid": "56c390c58c976285989d89dca1c512ccd0abf2d84843e56b76ee10a8472043d9",
    "walletconflicts": [
    ],
    "time": 1559668021,
    "timereceived": 1559668021,
    "bip125-replaceable": "no",
    "abandoned": false
  }

How can i recover the transactions > i see     "confirmations": 0, "bcconfirmations": 0,

[bible_pay]

How is it possible that with the same evo version (both 64bit) I have 2 different layouts on 2 different machines?, one at the old layout and one at a new layout. The loading screen is different too, old and new. One machine runs windows 10 and the other runs Windows server 2012 R2 Datacenter Edition. Same installer.

Edit: I even tried copying the exact same installer that I downloaded on my win10 machine to my windows server 2012 machine and it still shows the old layout?

Edit 2: Fixed... I think there are some register entries that are read from the old version. I changed it in the interface menu.

Regards,

Mart

Yeah, on Windows this is possible because we still use the same key-hive (biblepay) in both Classic and Evo.  In Classic, it had a setting name for the theme and we respect it, but on new installs we set it to be "Bezaleel" (the nice one).    You can get the key hive name by looking in the log under "QT-Settings", I believe we write it now (we also write it in linux, and a linux user can edit that file).

Or, you can just edit the settings in the UI and re-save once you upgrade .

[bible_pay]

Code:

  {
    "account": "",
    "address": "BHmM5aRfQ1GVbri4t9uyAc2A4bZ6orjnU7",
    "category": "send",
    "amount": -44119.99959200,
    "vout": 1,
    "fee": -0.00040800,
    "confirmations": 0,
    "bcconfirmations": 0,
    "trusted": true,
    "txid": "56c390c58c976285989d89dca1c512ccd0abf2d84843e56b76ee10a8472043d9",
    "walletconflicts": [
    ],
    "time": 1559668021,
    "timereceived": 1559668021,
    "bip125-replaceable": "no",
    "abandoned": false
  }

How can i recover the transactions > i see     "confirmations": 0, "bcconfirmations": 0,

This tx is not on the main chain. 
If you -zapwallettxes=1  it will erase the orphan from your wallet, then just re-send it.

[bible_pay]

Wow, with 115K diff and QT starting in a couple days it appears to be a nicer environment for investors.

[bible_pay]

****  BUG BOUNTY PROGRAM UPDATE ****

I added new bug bounty program bounties:
https://forum.biblepay.org/index.php?topic=408.msg6046#msg6046

The first rewards a white-hat-hacker for porting POBH to GPU.

The second rewards a white-hat-hacker for exploiting a GSC contract.

The third is the normal request for an upstream security bug.

[orbis]

Although we dont have the override yet for the client side transmission frequency, you can do this:
pog_foundationdonation=0
pog_coinagepercentage=0
healing_foundationdonation=0
healing_coinagepercentage=0

From your VMS and that will prevent it from sending a transmission.

I just added :
disablegsctransmission=1

To the next version.  This will stop the wallet from sending any.

So, my assumption was the same with those "0" so I add it to my VPSs (with disablegsctransmission=1). It was looking that it's OK, but then I realized the maybe it's needed to copy newest version of wallet (with registered CPK). So I copied newest wallet to my VPSs, restart wallet, unlocked it and ... went to bed, because it was too late.
Today after I came back from work I was badly surprised.
all of my VPSs sent default 2,5BBP GSCC and 2 times because it was more than 12h.
So, now I'm totally without coinage
There were light in the dark with 1432, I add disableclientsidetransmission=1 to all my configs, but 2 of my VPS sent GSCC again despite of that. I don't know why. Maybe that config wast just badly saved. I edit it again and now it looks that it's working properly, but with my 0 coinage I'm out of play
But thanks for the update
I have few questions:
Is it needed to have newest version with registered CPK on VPS?
Is it needed to have it unlocked? (I'm using -headlesspassword)
I was looking with "exec testgscvote" on contracts and there is stated that last superblock was 123430, but I haven't any payment. Or am I looking at it badly?
Thanks