Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - oncoapop

Pages: 1 [2] 3 4 5 6 7 8 9 ... 12
16
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

17
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).

18
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.

19
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.

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

21
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

22
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

23
1. The error that I can see on the compile script is this:

Fetching qtbase-opensource-src-5.9.6.tar.xz from https://download.qt.io/archive/qt/5.9/5.9.6/submodules
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
Fetching qtbase-opensource-src-5.9.6.tar.xz from https://download.qt.io/archive/qt/5.9/5.9.6/submodules
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
Fetching qtbase-opensource-src-5.9.6.tar.xz from https://download.qt.io/archive/qt/5.9/5.9.6/submodules
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
Fetching qtbase-opensource-src-5.9.6.tar.xz from https://bitcoincore.org/depends-sources
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
make: *** [funcs.mk:247: /root/biblepay/depends/sources/download-stamps/.stamp_fetched-qt-qtbase-opensource-src-5.9.6.tar.xz.hash] Error 22

2. The script then fails to compile at the end..
configure: error: libdb_cxx headers missing, Biblepay Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)
make: *** No targets specified and no makefile found.  Stop.

Any suggestions?


Blessings
oncoapop


24
Thank you, Rob, the guide was useful.

I used the precomplied binaries which were downloaded instead of compiling it on the server as compilation did not work on the first try.

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?

edit: all my 10 sancs are synced

Also, I instead of putting the conf files in a directory called /config, each of them are in the respective directories to aid trouble-shooting eg /data/biblepay1/biblepay1.conf

Would you like to commission my son who is on summer break to design some NFTs? We need to have a bit of back and forth as to what the designs are as they have to look professional and desirable!

Thank you.

Blessings
oncoapop

25
Thank you, Rob, the guide was useful.

I used the precomplied binaries which were downloaded instead of compiling it on the server as compilation did not work on the first try.

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?

Also, I instead of putting the conf files in a directory called /config, each of them are in the respective directories to aid trouble-shooting eg /data/biblepay1/biblepay1.conf

Would you like to commission my son who is on summer break to design some NFTs? We need to have a bit of back and forth as to what the designs are as they have to look professional and desirable!

Thank you.

Blessings
oncoapop


26
Dear Rob,
I have finally managed to set up a Cantabo VPS with the specs. 8 vCPU, 30 Gb RAM, 800 Gb SSD. What is the recommended method to set up each of the sanctuaries such that I can also set up cockroachdb on the same server to optimize usage of the machine? If there is a Wiki somewhere for this process, could you please point me to it, so that I can set it up properly from the first go without having to reprovision it if I screw up.
Thank you.
Blessings
oncoapop

27
BIBLEPAY RED SEA

Mandatory Upgrade @ 428,000 for Entire Network - June 19th, 2023
Github Commit:  https://github.com/biblepay/biblepay/releases/tag/0.17.3.7




The time is here for BiblePay to release its most powerful software ever:

  • The BiblePay Phone System with your own authentic US Phone Number
  • The ability to call anywhere globally to real PSTN destination phone numbers with low rates
  • Investor Sanctuaries
  • Active Sanctuaries
  • Unchained Desktop

Some notes about the release:
https://wiki.biblepay.org/Red_Sea_Release

User Guide:
https://wiki.biblepay.org/Red_Sea_User_Guide

Phone Rates:
https://unchained.biblepay.org/phone/rates

Congratulations on the latest upgrades and new features. The dark theme of the desktop version of Unchained appears to "hide" the announcements on the top of the page.

28
Dear Rob,

The Hash of biblepay-lin64.zip (linux wallet) does not appear to match the published hash on the website

Published hash                        = 70e0c55f4af8c93f2387e8e91aa56f27972d969b2c633472e1f46bedb53a4214
Newly Downloaded file hash = ac764d5e04e05d7ae1c13a555f01b98bdf35786eb6137261281ff518d32ee03d
Hashes do not match...

Thanks,
oncoapop

Thanks.

To set up a POVS sanc first create a regular sanc in prod and ensure its Enabled:
https://wiki.biblepay.org/Create_Sanctuary

Then install BMS:
https://wiki.biblepay.org/Install_BMS

At that point you can check the status of the sanc by looking at its status page:
https://your_sanc_IP/BMS/Status


** Important **
The new node must have at least a 400gb hard drive (free space) and 6 core cpu (otherwise it does not meet the minimum spec and will not be paid).

29
TestNet Discussion Archive / Re: February 2021 Testnet Thread (Tribulation)
« on: February 09, 2021, 01:08:33 AM »

Anyway, on a separate note, we still have BiblePay-TV to test also (although, Im removing 'mining' from it because it doesnt really fit properly in our infrastructure, so ignore that menu option).   EDIT: I just removed 'mining' from BiblePay TV.

Does anyone have Roku here?  If so you can also test BiblePay TV.

I do have a Roku3 - I just searched for Biblepay but could not find any channel of that name....

I might not have time to test during the week but I will try this weekend.


30
Note that any time we have a mandatory upgrade, all sancs that are part of the current quorum will end up getting POSE banned.  This also happens if all of us have our miners shut off.  Yesterday for example I had a power outage here and no one was mining for about 4 hours, so we had a lot of members of the quorum get pose banned. 

Today, I have a single thread miner running on one of the sancs - so theroetically none of us that are at the 0 ban level should increase.  Im going to be watching that.

I see your sancs:  104.167.116.179, and 108.63 are both POOS banned.  The way you can tell if you are POOS, or POSE, or both is:  700=POOS, 100=POSE, 800 = BOTH.
I see your two POOS banned sancs are both POOS+POSE banned (thats good) because they didnt pay their theoretical orphanage bill.

Ill set 104.167.108.63 as PAID now: OK 63 is paid.  Please revive it now.

Thats good you got the code -25 earlier, when trying to revive the POOS banned sancs.  Thats correct, people cant revive them unless the bill is paid first (this keeps people from slipping in and out and getting half paid by sending 15 revivals per month and tricking us).

Yes, I see you revived 45.62.240.90 earlier.  Good.  The "protx-dup' just means you sent a duplicate revival tx before the network fully processed the other one.  That doesnt hurt anything.  I think it takes about 2-3 confirms for us to all see the revival occur.

So far this test case (for cameroon one orphan-banning vs revival) has passed for me and for you.

Let me know if you have problems testing the test cases I posted in the OP post.

I dont know if you run the QT wallet or not.

On a side note, do you like the idea of POOS?  Didnt see any comments about it in the POOS thread.  How do you feel about sanc owners paying for an orphan?

1. Thank you.  104.167.108.63 has been revived.

2. 104.167.116.179
still  error code: -25

3. Just a quick reflection on the POOS.
a. It does place an extra burden on the sanc owners. They need to keep their servers running 24/7 or else get PoSE banned and also keep up Orphan payment or else get POOS banned.
b. Secondly, I presume that that orphan payments will be fixed in USD? Unless there are specific channels set up, frequently small payments in other than USD usually incur transaction fees which can add up. I personally support charities abroad and that is often a real problem.
 


Pages: 1 [2] 3 4 5 6 7 8 9 ... 12