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 - Rob Andrews

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 263
271
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 22, 2022, 02:41:17 PM »
Evenin.

Not at all. My problem was the biblepay-cli, i received some error "cannot connect to 127.0.0.1 make sure biblepayd is running" something like that so i added the RPC arguments in the config file.
Code: [Select]
#----
rpcuser=XXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
#----
#masternodeblsprivkey=
externalip=XXX.XXX.XXX.XXX
#----

I dont know if the masternodeblsprivkey=xxxxx + testnet=1 should be enough but for some reason i dont get the cli to respond without the rpc commands.

For sure looking forward for some test cases  :D ;D

Whew good, Im glad our wiki is OK for now praise God.  I think I know the problem with biblepay-cli.  When you run it simply as ./biblepay-cli command,  It tries to look to your "biblepay.conf" file for credentials to connect to biblepayd.
All you have to do is specify where your config is.  If for example your testnet conf is called "biblepaytest.conf" then do like this:

./biblepay-cli -conf=biblepaytest.conf getmininginfo
(This assumes of course that biblepaytest is in the ~/.biblepay directory, thats where I usually have it on non prod sancs. )

Yeah, let me look at these test cases next.

I'm going to start sharing some commands to query videos too.

PS
Your conf file is fine, but note that a lot of that is no longer necessary (I think each of those things had value in the past).
You can try putting a pound sign in front of everything except:
masternodeblsprivkey=
and
testnet=1


Using externalip is usually overkill.  I used to put that in because 'masternode status' showed some crazy result, but I found out later it always resolved itself after 20 hours lol.


272
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 22, 2022, 07:40:03 AM »
Hello Brother Rob.

Finally i have got the testnet Sanctuary and BMS up and running on the 20.04 node.
It was easy enough following the guides https://wiki.biblepay.org/Create_Sanctuary and https://wiki.biblepay.org/Install_BMS
I also threw an eye at the  https://docs.dash.org/en/stable/masternodes/setup.html

As for compiling the core wallet https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt it was just copy paste on this VPS no issues there.

I ran the
Code: [Select]
masternode status and
Code: [Select]
mnsync status  and i got
Code: [Select]
"state": "READY",
  "status": "Ready"
and
"IsBlockchainSynced": true,
  "IsSynced": true
 
so i ran the getblockhash comand

Code: [Select]
getblockhash 142700
539f1b8c495a568e4dcb69ae817679e4b5f53e4ef2ccba78f030543fe5ae6316

That looks fine.

After that i installed the BMS , went fine and after posting bms adress in the browser i got :

Code: [Select]
1029|0|v1.2|Status: OK
|https://185.182.186.162:8443|Synced_Count: 101, File_Count: 131838, Synced: 0.0007660916605158102
<EOF>

The only thing that i had abit trouble with was the biblepay-cli but that seems fixed aswell.

Hi Bro. Earlz, I hope you are blessed.
This looks really good, now we can make some real progress.

On the dash guide @ https://docs.dash.org/en/stable/masternodes/setup.htm, is there anything that we need to add to Create Sanctuary wiki page because its muddy?  Cause on one hand, getting the doc destroyed forced me to create a more succinct doc (which is good I think) but otoh its more for power users.  Ill be glad to add something if there was uncertainty somewhere.

Im very excited that you have both the sanc running and BMS is syncing now.  It should be synced within an hour or so.

In the mean time, I want to make you aware that we have a wilcard CDN SSL cert that we bought and deployed with BMS (its integrated with the program) and what this does is allows us to issue any hostname while the CDN is running and respond to the user without ssl errors.  So for example, your sanc is internally known as this DNS address to the other sancs:

https://sanc185182186162.cdn.biblepay.org:8443/BMS/Status

See if you open that in a browser, you won't get any SSL error because of the wildcard.  Anyway, the reason I mention this is I'm going to give you some pages you can hit from your browser that let you see Sanc videos directly from your sanc (proving that its working).  Its also possible to upload an s3 file directly into your sanc and get it onto the biblepay network by using the biblepay API.  https://wiki.biblepay.org/API

So let me get some of this info together for you once this sanc is almost synced, lll be back asap.





273
Amen!

My question is that I have about 630,000 BBP and would like to send some to an exchange.  It seems like I keep redpositing my stakes, so now my balance isn't that high in stakes I can send.  They all seem locked.  Is there any way to unlock some?
Hi brother in Christ,

I assume these are locked in the biblepaycore-wallet, right?  In coin control?  First ensure you are running the latest version because we had an upgrade  (Tools | Info) Version shold be 0.17.1.5 now.
Ensure you are synced with https://chainz.cryptoid.info/bbp/
Then go to Settings | Options | Wallet | Show Coin Control Tab=checked

Then go to coin control by going to SEND, then click Coin control.
Then right click and uncheck the locked coin, and then you can send it.

I usually send it to myself (my own address from the address book, just to get it unlocked) then you can send it later  etc..


274
Problem Statement:
The problem is not in the biblepay-qt wallet itself, it is merely that the OS in some circumstances launches our QT application with a high DPI scale setting (usually 2.0) which effectively means the app launches on the screen double its intended size.  Additionally, the core window is coded to work with monitors greater than 1150 x 800, so if your resolution is greater than this, you should be able to make biblepay-qt work properly.


Solution 1:

Try this one first; this is the easiest change:
Click Settings | Options | Appearance:
Change the font scale slider to the left.
Change the Font Family to System Default.  Click OK.
On my machine, the entire window size scales down to be smaller and the font size scales down, then I can see everything.
Note, that the wallet should not take up more than 75% of your screen.  If its hanging off the end of your monitor (too big for your screen, proceed to Solution 2).

Solution 2:
(Primarily for Windows):
Check your resolution in display settings.  Our wallet works down to 1150x800.  If your resolution is bigger than this, and biblepay is larger than the screen then you are experiencing the Windows HDPI mismatch between the hi-definition dpi scale and the application.
Try this:
https://www.windowscentral.com/how-change-high-dpi-settings-classic-apps-windows-10-april-2018-update
The goal is to change the scale of the app back to 1.0.

Solution 3:
(Primary for Linux):
In QT, I have observed a double sized (high dpi) launch of biblepay-qt a few times and I think this is primarily due to having lost specific QT export settings for the current user.  And I've seen screen shots of Dash having this issue.
I successfully launched biblepay-qt with a 1.0 scale by doing this:
export QT_AUTO_SCREEN_SCALE_FACTOR=0
./biblepay-qt

Let us know if all 3 of these things fail or if you have some more suggestions or enhancements!




275
This thread discusses solutions if your biblepay-qt wallet appears too large on your display, so large that the borders are cut off the screen Or if you cant see the "SEND" button when you navigate to the "SEND" menu (to send coins).  Send button is supposed to be at the bottom left of the screen (below the transaction fee). 


276
Interesting. Just started reading this, and I like this topic. I don't have much time to research, but it's interesting to read.
I see there was a broken link in the OP post: FIXED.


277
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 18, 2022, 06:48:40 PM »
Evenin.

I have also done some testing on this  BBP drive.

https://wiki.biblepay.org/BBP_Drive

The installation process went smooth overall. There was that thing about the .conf file but Rob fixed that.   

Navigate to BBP Drive github from op post.
Install Dokan driver on windows box: pass
Install BBP drive using the MSI:  pass
Launch "BBP Drive" from Start | Applications | BBPDrive
When BBP Drive boots it asks for API key.
Enter the API key you obtain from the wiki instructions:  pass
Once BBP drive is running, verify we have an N: drive in windows : pass
Rename a file, verify it renames : pass
renamed a picture, np there.
Edit a file and re-save it , verify the contents have changed : pass
changed a text document,  it checked out.
Delete a file, verify it deletes : Does not seemed that it deleted yet.

I deleted the picture from the N drive but still i can see it in the web browser.

Try loading one of your files from the external URL:
It works, for example some of my pictures:  https://bbpipfs.s3.filebase.com/video/45/timber12.gif , https://bbpipfs.s3.filebase.com/video/45/APPstyleLcabin.png

Overall i think nice feature.

When minimizing the BBPdrive.exe i would have liked if it could go to the hidden icons section on windows 10  where  your speakers , windows security , network etc are.  Also like a harddrive bbp icon would be sweet.

Great testing man.  I really like the APPstyleLcabin, that things is beautiful.

So on the deleted file, this actually might be OK if it still on the internet.  This is because our CDN gives you a 'globalcdn.biblepay' link at first and that is the direct URL to the sanctuary.  (But we back up files into our IPFS provider just in case) and I will show you how to check if its really deleted once you get BMS up and running and we do a Video test, I can show you how to go that dir and see if its deleted.

Anyway you can also check like this:  If you restart BBP drive and leave it on for at least 60 seconds, if that file stays deleted, then its really deleted and this web instance is just an IPFS backup.

I like your two suggestions and frankly I would like to do those but if we get more interest in using the program cause of course theres a long list of things to do with our youtube feature (like adding AI to it for example), but yes those are definitely needed.    I added a github issue for you for this:
https://github.com/biblepay/BBPDrive/issues/1

Note that anyone can add these feature request to each github if they want.


278
Hi Rob,

Is this where I should ask questions on issues that I am not clear on ????

Hi Pat,

Yes, this is the overflow area where people ask general questions about the coin that don't need a dedicated thread.

You can also create a dedicated thread if you have an ongoing discussion (for example we have one for mining issues). 

Thanks,
Rob

280
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 17, 2022, 08:51:05 PM »
Test case for BBP Drive:

Navigate to BBP Drive github from op post.
Install Dokan driver on windows box: PASS
Install BBP drive using the MSI: PASS
Launch "BBP Drive" from Start | Applications | BBPDrive
When BBP Drive boots it asks for API key.
Enter the API key you obtain from the wiki instructions:  PASS
Once BBP drive is running, verify we have an N: drive in windows : PASS
Drop 10 files on the N: drive in root folder and some in the subfolder : PASS
Launch some of the files in windows, verify they load normally (tested images by double clicking them, tested one video, tested some notepad files) : PASS
Edit a file and re-save it , verify the contents have changed : PASS
Rename a file, verify it renames : PASS
Delete a file, verify it deletes : PASS
Try loading one of your files from the external URL:
According to my bbpdrive when it launched my storage area is :
https://globalcdn.biblepay.org:8443/video/96/
The file I stored is in subfolder mypath.  The file name is "bbphoriz.png". 
So navigate to URL:
https://globalcdn.biblepay.org:8443/video/96/mypath/bbphoriz.png
Verify the image is visible on the internet:  PASS

Image hosted on bbpdrive (pasting bbp drive URL into our forum image tag):



281
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 17, 2022, 08:46:12 PM »
Test Case for TLT (Time locked Trust):

Download time locked trust and install it.
Verify the user can create a mainnet or testnet TLT keypair by generating a trust: PASS
Save the trust to a file and read the trust in notepad - does it look correct? : PASS
Generate one TLT trust in the past (March 2022), and one in the future (May 2022) for testnet : PASS
Boot biblepaycore and import the keys (importprivkey privkey) for each of the TLTs: PASS
Edit the names of the keys (I named one March-2022-TLT and another May-2022-TLT)
Now fund each wallet with 5K
Now try to spend from the March 2022 wallet : PASS (I was able to spend it)
Now try to spend from the May 2022 wallet: PASS (I was NOT able to spend it)
In unit test, verify the new error appears preventing the spend : PASS


282
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 17, 2022, 08:42:41 PM »
Test case for MainNet subsidies:

Boot up into mainnet using exodus, verify chain is synced: PASS
Verify the daily block reward (nextdailylimit) using getgovernanceinfo has increased to ~325K (for UTXO staking rewards): PASS
Verify the block subsidy for RX miners and Sancs has increased to approx 4400: PASS
Verify the monthly governance budget has increased to 10% of block emission for orphan charity (it was approx 4MM and the total was about 6.75MM including non charity expenses) : PASS


283
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 15, 2022, 08:36:58 AM »
Mornin!

Hey Rob could you update the BBP drive wiki when time , its still not restored.

Thanks.

Sure, I apparently saved it with an underscore this time.  I just updated the OP post.  Thanks.


284
Active Discussions / Re: June 2022 - TestNet Release - Exodus
« on: April 13, 2022, 07:01:11 PM »
Welcome back everyone (our original thread was destroyed).

Good block hash:
18:59:12
getblockhash 142700
18:59:12
539f1b8c495a568e4dcb69ae817679e4b5f53e4ef2ccba78f030543fe5ae6316


So far we had Earlz test TLT, and he tested a maturity date ending in the past successfully.  I tested one past (and was able to spend) and one future (and was not to spend).
Then we added an error message preventing a user from spending early (so they dont get stuck with needing to do zapwallettxes=1).


One thing you guys can jump on testing:  You can test BBP drive.  That's documented in the wiki in the OP post.





285
*** Our last Mandatory upgrade was released March 2nd 2022 ***
0.17.1.5-Mandatory Upgrade for Entire Network @320,000 Latest

https://github.com/biblepay/biblepay/releases/tag/0.17.1.5

- Reposting this for visibility


Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 263