Messages

91

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: August 16, 2023, 08:45:14 PM »

BIBLEPAY EXCHANGE ALERT


TXBIT.IO (Coin Exchange) is going out of business.


PLEASE WITHDRAW ALL COINS WITHIN 30 DAYS.

92

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: August 15, 2023, 07:05:35 PM »

Thank you for releasing the new BBP wallet version 0.17.3.8!

It reinstalls over the old and the previous issues were addressed!

1. Selecting Unchained from the wallet after install of the new version shows BMS upgrading and reinstalls BMS directory (which I previously deleted).
2. Unchained then loads in the (default, in my case Edge) browser and is automatically logged in with the correct BBP value in the address and Unchained version. All my NFTs are correctly displayed!
3. The phone works well and very clear from my BBP number to my Canadian cell phone! I can call the BBP number from my cell phone but I did not know it was ringing unless I had my browser window open and could see the pop up.
4. I also tried SMS which works both ways! This is great!

Congratulations on the success! Excellent work! Thank you! 

Blessings
oncoapop

Hi Bro. Damian,

Hey thanks for testing this.  I'm so glad the bootloader works more professionally now (doesn't let the user hang if it needs to sync the initial files for the first time, or if it needs to upgrade.  It also kills straggling copies when it upgrades).

So I'm really happy you tested the phone, thank you sir.

SMS is still a work in progress; there are some issues with certain countries SMS to each other; I actually released that by accident, sorry.  I need to explain some of these goals; because they are rather complex now.  (For example, competing with Zoho and making an SSO for BBP users with an Outlook type inbox, etc).

I got your DM about the NFT... I'm going to debug that, it brings up some very good points.  I have a hunch that the 'common sense' used when we had ERC712 possibly some of those rules got lost when I moved back to native BBP; sigh, its a stressful situation.  On one hand I like the rigid interface of ERC20 NFTs but otoh I like it when BBP owns the NFT natively... Let me elaborate after I debug the specific issue.

I also owe a broad discussion on the roadmap.  You have some great ideas but we have limited resources.  I think what we need is to get this roadmap into a gantt chart and a project mgmt system with stories and epics so we can understand whats currently slated as compared to the potential wishlist, and we can also let the community (or possibly the Sancs) vote on what we do each quarter!

Thanks!

93

Active Discussions / Re: March 2023 - Red Sea Release

« on: August 15, 2023, 06:55:35 PM »

rob again I can't dial other countries numbers

Please post everything leading up to the problem; IE if you have a phone number and can call US numbers - and then the flow and then the problem.

94

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: August 12, 2023, 01:16:53 PM »

Just a friendly note, Oncoapop, in the inner text of the instructions, its supposed to be 4,500,001 for the collateral.

95

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 30, 2023, 09:01:41 AM »

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

Theres got to be a reason its not upgrading from 4.3.2 to 6.5.2 - I sent you a DM about it and we can try a reinstall with reupgrade to see where it falters in the ugprade process.

So on the lamb, I added a piece of BL lately that stops a user from buying an NFT if they are not logged in but you have to be upgraded to see that.
Once you upgrade we can see if you can view the lamb in My NFTs.

In the near future we will be able to show the user more clearly that the node is upgrading (IE a message) and we can also enforce the new version when it has broken compatibility (IE when a major release is released, the node should stop working and show a clear message that it has to upgrade, otherwise it dies off).  I'm working on that.

96

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 30, 2023, 07:33:05 AM »

Thanks for the update Oncoapop.

I got called to be best man at a wedding so things have been a little behind here, but I'm checking on this today.

97

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 25, 2023, 08:11:36 PM »

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?

98

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 22, 2023, 08:01:49 AM »

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

99

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 15, 2023, 09:09:27 PM »

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.

100

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 15, 2023, 08:51:46 PM »

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

101

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 15, 2023, 01:02:58 PM »

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

102

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 15, 2023, 06:35:25 AM »

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?

103

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 15, 2023, 06:26:56 AM »

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.

104

Active Discussions / Re: March 2023 - Red Sea Release

« on: July 13, 2023, 08:38:04 PM »

God morning

 If i make a easy sanc,that will be a cold sanc,right? And if i like a active sanc i can chang it to do so?Will my KEMO(vpn) be a trouble fore it to work?

Just to make a distinction between cold & hot sancs, that term used to be at the beginning but hot sancs are no longer supported.  All that means is at one time, we used to be able to put collateral in a sanc and run it on a VMS and that sanc would have 4,500,001 in its wallet and therefore it was a hot sanc.  Those are no longer supported - all sancs are cold now.  (Cold just means the collateral stays in your home wallet, but gets allocated/locked which points the collateral to a running sanc, allowing that running sanc to have a cold wallet).  Which is good for security.

If you run a sanc at home vs VPS, that would just be Dynamic IP sanc vs Static IP sanc.  Both work fine as real sancs (IE you will get the full reward).

The only downside to dynamic IP sancs is if your IP changes you get pose banned (which moves your sanc into Investor mode), and then you have to change your IP in your 'deterministic.conf' file and run the revivesanc sancname command to recover.  While its being POSE banned, all that happens is you move temporarily into 50% pay mode until you revive the sanc.  Btw, we caption the sanc as 'INVESTOR' when that happens.

105

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: July 13, 2023, 06:26:19 AM »

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

Ok, it might be OK that you've moved the configs to other places in this case (hopefully).

Do you know what error you received in the compile and what led up to it?  Im not against using the precompiled binaries, but it doesnt make me feel too good if we go end to end building the temple and we have a basic compile problem (will probably become an issue when we get to the advanced troubleshooting with cockroachdb, possibly).

I dont want to set expectations too high on the NFT side; Im not going to have the bandwidth to talk about NFTs for quite a while; I would prefer if you work directly with the community on that so that Im not a blocker.

Any progress on testing the phone system?