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

On further inspection https://download.qt.io/archive/qt/
Requested: https://download.qt.io/archive/qt/5.9

Version 5.9 no longer exists on the site. can we substitute another version?

Blessings
oncoapop

One more basic question:
For the Windows Desktop BMS server ie unchained.

How does one sign in? I cannot perform any actions without signing in and I am sorry but I cannot figure out how to sign in.

I think I was signed in previously as I could add the NFTs, but I am not signed in at present.

Thank you.

Blessings
oncoapop

One more basic question:
For the Windows Desktop BMS server ie unchained.

How does one sign in? I cannot perform any actions without signing in and I am sorry but I cannot figure out how to sign in.

I think I was signed in previously as I could add the NFTs, but I am not signed in at present.

Thank you.

Blessings
oncoapop

Hi bro Oncoapop,

The way authentication works on Desktop unchained is if you have a New wallet, (and no Unchained keypair yet in your Receiving addresses list) , we create one and then we create an 'unchained.conf' file in the data directory (similar to wallet.dat).
That keypair is then used for authentication and spending within all of unchained.  (Phone calls are billed there and file hosting is billed there too, and you can spend from that key from the unchained wallet page).
If you move your system you would have to copy that unchained.conf and then it would authenticate as you again.
(On a side note I sent you an email a few weeks back using this forum email address you have on file).
You can go to Profile and change your Nickname and click save, and that should save your record and prove when you move machine to machine you are logged in.

One more thing, when you have phone numbers attached to that key they stay with that key, so its very important to keep that file once phone numbers and NFTs are attached to that key.

On further inspection https://download.qt.io/archive/qt/
Requested: https://download.qt.io/archive/qt/5.9

Version 5.9 no longer exists on the site. can we substitute another version?

Blessings
oncoapop

You also asked:
Let's say one sanc chain is fully synced, which directories can I copy to the rest of the other /data/biblepay(n) directories so that their chain will be also synced with each of the other sancs, without having to sync from scratch for each of them, or is it necessary for temple sancs to sync from scratch (ie do template sancs communicate with one another to ensure they are internally synced with each other?) What happens when on sanc is out-of-sync, does it automatically get a consensus from internal temple sancs first or just from the blockchain on the internet?

-> I havent found a way to make multiple sanc instances share a data directory (I think thats impossible).  I just have one data directory per sanc.  So they all sync individually right now.  Mainly because database locking - you cant share the database file with more than one node at a time.  (If you are bootstrapping you can ungzip a copy of the synced folder in first; which we dont publish yet but we should in the future).


Ok, thanks for the detailed compile report.
Ive reproduced this on one of my boxes and it is exactly as you say, a build dependency issue is missing and would have affected any upstream coin as well (AKA Dash, Bitcoin) until the build dependency script was fixed (which it looks like it was fixed in the future because there have been commits made to bitcoin and dash for this).  Yes/No on using a new version; No in the sense you cant just change it as it requires a hash and compatibility, but Yes it can be fixed other ways but is very tedious.

The issue with changing these dependencies is there are a whole slew of patches with different QT versions and we cant simply pull the latest Depends(build) files from DASH, because they are Only compatible with recent builds, and you cant change the QT version without disrupting the patches.
Best bet is to inherit all these Depends changes at once during our next rebase and in the mean time fix the dependency URL to point to a real download of 5.9 from somewhere else on the internet.

Ok, now that I know of the problem Ill see if I can host QT 5.9 on the biblepay server a little later and see if that fixes it with a clean build.

Will you be testing a phone call soon?

On further inspection https://download.qt.io/archive/qt/
Requested: https://download.qt.io/archive/qt/5.9

Version 5.9 no longer exists on the site. can we substitute another version?

Blessings
oncoapop

Ok this is fixed.
To build biblepay:
git pull origin master

cd depends
make -j 8

Then after it builds the dependencies, you can continue (just in case you want to verify the entire build finishes, then we can have self built binaries in the future).

Compile completes and the binaries appear in the directory, so it appears to work!
Great job!
Thanks.
Blessings
oncoapop

Dear Rob,
Sorry for some reason I could not remember which web wallet was open when I connected to unchained and hence I cannot login with the same credentials.
I have a phone number (provisioned with 12065310541 to BAuYpKr22mkULvTKb3YiqG3TszbgdXzWRR) but as I cannot login, I cannot make calls.
Blessings
Damian

Hi bro Oncoapop,

The way authentication works on Desktop unchained is if you have a New wallet, (and no Unchained keypair yet in your Receiving addresses list) , we create one and then we create an 'unchained.conf' file in the data directory (similar to wallet.dat).
That keypair is then used for authentication and spending within all of unchained.  (Phone calls are billed there and file hosting is billed there too, and you can spend from that key from the unchained wallet page).
If you move your system you would have to copy that unchained.conf and then it would authenticate as you again.
(On a side note I sent you an email a few weeks back using this forum email address you have on file).
You can go to Profile and change your Nickname and click save, and that should save your record and prove when you move machine to machine you are logged in.

One more thing, when you have phone numbers attached to that key they stay with that key, so its very important to keep that file once phone numbers and NFTs are attached to that key.

Dear Rob,
Sorry for some reason I could not remember which web wallet was open when I connected to unchained and hence I cannot login with the same credentials.
I have a phone number (provisioned with 12065310541 to BAuYpKr22mkULvTKb3YiqG3TszbgdXzWRR) but as I cannot login, I cannot make calls.
Blessings
Damian

I just remembered I had fixed a few problems in unchained during the last round of phone testing and maybe I broke login; let me release the new version of unchained with voice mail and we can test login again.

Hang on...

Dear Rob,
Sorry for some reason I could not remember which web wallet was open when I connected to unchained and hence I cannot login with the same credentials.
I have a phone number (provisioned with 12065310541 to BAuYpKr22mkULvTKb3YiqG3TszbgdXzWRR) but as I cannot login, I cannot make calls.
Blessings
Damian

Ok, I released the latest version (6.52) which includes voice mail.
Go ahead and click Unchained from the left menu from your node and it should upgrade (it could take a good 3-4 mins).  Ive got a future feature coming where it will display the upgrade progress but that is hard to release (right now there is a 50% chance you will get a popup telling you that its upgrading); either way just wait til the web page loads.

Then verify its v6.52 on the web UI; then you should be logged in.

Try saving your NickName just to be sure things work then you should be able to test the phone.

I tested this upgrade on my remote test node and it worked.

Still did not work for me. Am I supposed to sign in using another wallet (ie metamask) or is that automatic given the .conf file? My unchained BBP address is automatically recognized.

This is output of the BMS window:

info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://0.0.0.0:8080
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: C:\Users\damia\AppData\Roaming\Biblepay\BMS
warn: Microsoft.AspNetCore.Session.SessionMiddleware[7]
      Error unprotecting the session cookie.
System.Security.Cryptography.CryptographicException: The payload was invalid.
   at Microsoft.AspNetCore.DataProtection.Cng.CbcAuthenticatedEncryptor.DecryptImpl(Byte* pbCiphertext, UInt32 cbCiphertext, Byte* pbAdditionalAuthenticatedData, UInt32 cbAdditionalAuthenticatedData)
   at Microsoft.AspNetCore.DataProtection.Cng.Internal.CngAuthenticatedEncryptorBase.Decrypt(ArraySegment`1 ciphertext, ArraySegment`1 additionalAuthenticatedData)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.DangerousUnprotect(Byte[] protectedData, Boolean ignoreRevocationErrors, Boolean& requiresMigration, Boolean& wasRevoked)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData)
   at Microsoft.AspNetCore.Session.CookieProtection.Unprotect(IDataProtector protector, String protectedText, ILogger logger)

Ok, I released the latest version (6.52) which includes voice mail.
Go ahead and click Unchained from the left menu from your node and it should upgrade (it could take a good 3-4 mins).  Ive got a future feature coming where it will display the upgrade progress but that is hard to release (right now there is a 50% chance you will get a popup telling you that its upgrading); either way just wait til the web page loads.

Then verify its v6.52 on the web UI; then you should be logged in.

Try saving your NickName just to be sure things work then you should be able to test the phone.

I tested this upgrade on my remote test node and it worked.

Still did not work for me. Am I supposed to sign in using another wallet (ie metamask) or is that automatic given the .conf file? My unchained BBP address is automatically recognized.

This is output of the BMS window:

info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://0.0.0.0:8080
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: C:\Users\damia\AppData\Roaming\Biblepay\BMS
warn: Microsoft.AspNetCore.Session.SessionMiddleware[7]
      Error unprotecting the session cookie.
System.Security.Cryptography.CryptographicException: The payload was invalid.
   at Microsoft.AspNetCore.DataProtection.Cng.CbcAuthenticatedEncryptor.DecryptImpl(Byte* pbCiphertext, UInt32 cbCiphertext, Byte* pbAdditionalAuthenticatedData, UInt32 cbAdditionalAuthenticatedData)
   at Microsoft.AspNetCore.DataProtection.Cng.Internal.CngAuthenticatedEncryptorBase.Decrypt(ArraySegment`1 ciphertext, ArraySegment`1 additionalAuthenticatedData)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.UnprotectCore(Byte[] protectedData, Boolean allowOperationsOnRevokedKeys, UnprotectStatus& status)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.DangerousUnprotect(Byte[] protectedData, Boolean ignoreRevocationErrors, Boolean& requiresMigration, Boolean& wasRevoked)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector.Unprotect(Byte[] protectedData)
   at Microsoft.AspNetCore.Session.CookieProtection.Unprotect(IDataProtector protector, String protectedText, ILogger logger)

Yeah, the key would be to upgrade to 6.5.2 (you can see the version from the Home page).

I dont know what this error means.

Please try to kill BiblePay BMS from task manager and try one more time?

Then paste stack again?

In the mean time, Ill do a little research and see if we have a separate log for upgrading.

Good luck.

Once you are on 6.5.2 I think your login will work fine (even though its just a local login to localhost).

Thank you, Rob for your efforts.

The new Biblepay version does not extract the BMS directory at least at the same location. I erased the old BMS directory and reinstalled but the new installation did not contain a BMS directory at ....\AppData\Roaming\Biblepay

Are you kindly able to advise?

Thank you.

Blessings
oncoapop

Yeah, the key would be to upgrade to 6.5.2 (you can see the version from the Home page).

I dont know what this error means.

Please try to kill BiblePay BMS from task manager and try one more time?

Then paste stack again?

In the mean time, Ill do a little research and see if we have a separate log for upgrading.

Good luck.

Once you are on 6.5.2 I think your login will work fine (even though its just a local login to localhost).

Prior to deletion of the BMS directory, navigating to localhost:8080 actually gave me the option of connecting to a wallet (see screenshot).

Blessings
oncoapop

Thank you, Rob for your efforts.

The new Biblepay version does not extract the BMS directory at least at the same location. I erased the old BMS directory and reinstalled but the new installation did not contain a BMS directory at ....\AppData\Roaming\Biblepay

Are you kindly able to advise?

Thank you.

Blessings
oncoapop

Oncoapop,
I forgot to mention, on the localhost version of Unchained, we no longer use metamask.
It strictly connects to the unchained.conf file, gets your keypair, and considers you logged in if it has a valid keypair.
This keypair links your wallet to the cockroachdb user record instance which gets your Nickname (and allows you to use social media features etc as a community user).


We should not have changed the location of the unzip; I will look at the installer process and for a log and get back to you.

What version are you currently showing on the home page?

Dear Rob,

As I have deleted my BMS directory, BMS no longer launches but a parallel version on my other desktop shows BiblePay v4.3.2 on the Chrometab and BiblePay Unchained v6.07 on the home page. The wallet shows the correct address BUT a balance of -1.00 BBP.

Interestingly, using the Phone service tab (Phone v.12), it correctly reports my Unchained BBP address (BAu...WRR) AND CORRECT balance (1,335,601... BBP), but fails to make a call as I am not logged in.

Also, when I purchase (Buy it now) NFT Lamb (2,514 BBP), my wallet is charged 2,514 BBP and 4.73 BBP but fails to appear under my NFTs as I am not logged in.

Blessings,
oncoapop

Oncoapop,
I forgot to mention, on the localhost version of Unchained, we no longer use metamask.
It strictly connects to the unchained.conf file, gets your keypair, and considers you logged in if it has a valid keypair.
This keypair links your wallet to the cockroachdb user record instance which gets your Nickname (and allows you to use social media features etc as a community user).


We should not have changed the location of the unzip; I will look at the installer process and for a log and get back to you.

What version are you currently showing on the home page?