Messages

16

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: May 07, 2022, 06:01:51 AM »

Mornin.

Here is a good hash:
14:45:32
getblockhash 143823

14:45:32
8768e6e083ba46ad58bfc3d1eeced588cf5066969f40116b094856bdb0d742f0

My testnet wallet syncs just fine now.

Code: [Select]

10:52:03
getblockhash 143823


10:52:03
8768e6e083ba46ad58bfc3d1eeced588cf5066969f40116b094856bdb0d742f0

Looks same as yours Rob, looks accurate.

On the installation of the  https://wiki.biblepay.org/Install_BMS

The manual upgrade of the BMS on the sanc went without any troubles , just copy paste commands for me.

Test 1, ensure your sidechain syncs:

Restart BMS.  Verify you are at block 152 or higher:
https://globalcdn.biblepay.org:8443/BMS/Status

To get the block hash try this:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=152

This will also show you the transactions in that block and the hash and the diff etc.

Looking at the bms i can see that its at block 172.

Code: [Select]

{
  "URL": "https://185.182.186.162:8443",
  "BMS_VERSION": 1047,
  "COMMON_VERSION": 1003,
  "Status": "OK",
  "Synced_Count": 145194.0,
  "File_Count": 145194.0,
  "Synced_Percent": 0.9999999311266352,
  "EOF": "<EOF>",
  "Memory_Pool_Count": 0,
  "Best_Block_Hash": "000047aeb2a015ba903b3279ae2dfcc183e035eeb11ead618ca3a9fadc59bdee",
  "Block_Count": 172,
  "Hashes": 81364
}
I also tested the blockhash

Code: [Select]

{
  "Version": 1,
  "PreviousBlockHash": "0000b39315a9de15a80a41f7f31cbd1a93fcd73ecf2b0eb51b1bfbf4794cd4e8",
  "MerkleRoot": "37feb5947ec3c60f5d05af7bbbf023997862b90bb66dccfb4622bebc7d78fa59",
  "Time": 1651493630,
  "Target": 1766847064778384329583297500742918515827483896875618958121606201292619775,
  "Nonce": 393054,
  "BlockNumber": 152,
  "Transactions": [
    {
      "Data": "{\"field1\":\"https://7e825619-9da1-4b87-bcba-577aeef9bd28\",\"field2\":\"https://99bde5a8-da37-49da-99ff-929794a3756d\",\"me_id\":4000,\"table\":\"Junk2\",\"nMeID\":1.0}",
      "Time": 1651493625,
      "BlockHash": "00001107a8f9f1803b15ebddf30fd0bf0277d852d722372cac9c1c44977a19c8",
      "Height": 152
    },
    {
      "Data": "{\"field1\":\"https://3b168786-1e58-46bb-8377-e4f777a195ab\",\"field2\":\"https://62cd6ce1-12a2-4ccf-9ca7-770d97a88f97\",\"me_id\":7000,\"table\":\"Junk2\",\"nMeID\":1.0}",
      "Time": 1651493625,
      "BlockHash": "00001107a8f9f1803b15ebddf30fd0bf0277d852d722372cac9c1c44977a19c8",
      "Height": 152
    },
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Note that social.biblepay.org is already using our sidechain for Photos and Videos.
So this next test, lets add a photo to a group in social.biblepay.org.  To do this go to any group (or you could go to your home profile timeline) and then Add a picture.  Save the post.
Now quickly go to this page
https://globalcdn.biblepay.org:8443/BMS/Status


At this point the memory pool should have 1 transaction waiting.  Once it is mined, you can then go to the new block number (IE if its one higher, you have to change the block height here):  Change NNN to the correct height:
https://globalcdn.biblepay.org:8443/BMS/GetBlock?id=NNN

Then look for the transaction that contains your image.
This shows how we not only have a decentralized file storage system, but now a decetranlized DSQL system also.

Next i uploaded a image to social and followed the instructions:

Code: [Select]

"Transactions": [
    {
      "Data": "{\"URL\":\"upload/photos/2022/05/ZwJcrXZVlWIrxRYxGNGy_07_c846a84e7dee71ba98459c475ec2da98_image.jpg\",\"Added\":\"5/7/2022 5:37:18 AM\",\"userid\":\"3\",\"size\":11535,\"syncedlocal\":\"0\",\"syncedremote\":\"0\",\"table\":\"pin\"}",
      "Time": 1651919838,
      "BlockHash": "000003f84d42083417689806396c3cfe6689df21d5611764c1806449ef6bc32b",
      "Height": 173
    },
    {
      "Data": "{\"URL\":\"upload/photos/2022/05/ZwJcrXZVlWIrxRYxGNGy_07_c846a84e7dee71ba98459c475ec2da98_image_small.jpg\",\"Added\":\"5/7/2022 5:37:17 AM\",\"userid\":\"3\",\"size\":14519,\"syncedlocal\":\"0\",\"syncedremote\":\"0\",\"table\":\"pin\"}",
      "Time": 1651919837,
      "BlockHash": "000003f84d42083417689806396c3cfe6689df21d5611764c1806449ef6bc32b",
      "Height": 173
    }
and upon inspecting my picture at social hitting the "open original"  button :

Code: [Select]

https://sanc1.cdn.biblepay.org:8443/upload/photos/2022/05/ZwJcrXZVlWIrxRYxGNGy_07_c846a84e7dee71ba98459c475ec2da98_image.jpg
i can see them matching.

17

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: May 03, 2022, 12:52:27 PM »

*** Additional Instructions Added to BMS Install Wiki ***


Testers, the BMS installation procedure has been enhanced to allow our sidechain to work with MySQL.
This will give us the unique ability to be the first known coin that can leverage DSQL in mainnet (allowing our social media product to run on the sidechain, and, giving us many other Layer 2 features).

The wiki guide here has been extended:

https://wiki.biblepay.org/Install_BMS

For those of you who already have BMS running please do the following:

Stop BMS by going to the node, to the terminal, and simply press ctrl-c.  (It may already be stopped due to the failed upgrade, simply continue from here with the BMS program stopped).

Find the place in the document where it says "Installing MYSQL".  Start running those commands as root until "End of MySQL".

Once finished, start BMS again (by running the command to start the node:  dotnet BiblePay.BMSD.dll).

At this point the menu should appear and the node should not crash.

Post if you have trouble.

Evenin Brother Rob.

I got the BMS up and running again.

The  part : Installing Local MySQL database  , went just fine for me no hickups there. Copy pasting the terminal commands no problems.

 I did check now in the browser and got:

Code: [Select]

{
  "URL": "https://185.182.186.162:8443",
  "BMS_VERSION": 1039,
  "COMMON_VERSION": 1002,
  "Status": "OK",
  "Synced_Count": 1070.0,
  "File_Count": 144628.0,
  "Synced_Percent": 0.007398290275860118,
  "EOF": "<EOF>",
  "Memory_Pool_Count": 0,
  "Best_Block_Hash": "00005450cb29ae91e2a2decd27c2d8d101b6c1cb49cbd7f5e92cd459f9818807",
  "Block_Count": 159,
  "Hashes": 519
}
I will do the test cases you posted tomorrow.
Talk to you laters.

18

Announcements & Fundraisers / Re: Third fundraiser for Water Wells in Pakistan

« on: May 01, 2022, 01:35:16 PM »

Third week update

For the third week we have raised additional 155 USD and a total of  881 USD 62.9% of the goal.

Im thinking let the fundraiser keep going for the duration of may unless we get to the goal before then.

Thanks for the donations.

19

Announcements & Fundraisers / Re: Third fundraiser for Water Wells in Pakistan

« on: April 24, 2022, 07:53:54 AM »

Second week update

For the second week we have raised additional 276 USD and total 726 USD ,  51% of the goal.
I want to thank everyone who has donated so far. 

20

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: April 23, 2022, 11:03:19 AM »

Automatic Upgrade test case:

So the BMS nodes have a nice feature in that they can automatically upgrade themselves when we have a new version.
So to test this, we were on version 1029 last night.  I just added a tiny feature to demonstrate this upgrade ability.
In this page:

https://globalcdn.biblepay.org:8443/BMS/Status

I made it JSON instead of homegrown.
This page itself also reveals the version (which should now be 1030).

From your sanc IPs, please hit this page and see if your version increased?

I just checked the vps and i see that the bms has changed from 10.2v to 10.31 version.

21

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: April 22, 2022, 03:46:45 PM »

Hey.

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

Indeed. when i pointed the cli to the test config file it worked just fine..  Haah can be that easy sometimes right      I also tested to pound out all the rpc commands , external ip and such on another node and it still worked so seems they are not needed indeed.

Test case to ensure an individual sanctuary can play a video directly from the sanc:

This is a nice feature even though it would be a long shot to actually use it, this allows you to play a Sanc video directly from the sanc into the browser (no CDN required).  So if your videos are synced, and you have a connection to the sanc, and the rest of the world is down, the video will still play.

URL:

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

Note that this video list will grow as your sanc syncs to 100%.  We only have about 300 videos right now being stored (these videos are the ones uploaded into social.biblepay.org into the video room, that is what we are hosting).

So to perform the test just click on one of the videos, and notice the sanc will generate a local url (a url playable directly from the sanc), then skip around in the video and ensure it plays.

I tested to play some videos from the sanc, its cool man...  I like the BBP logo on the video player. The buffering wasnt to bad either when scrolling thru the videos.
Looking sweet rob. 
I noticed when clicking from the sanc onto the video it says the  "certificate is not valid" 

Here is a little tiny test case that shows which nodes Your sanc knows about (this is so it knows how to reach out and refer video streamers to another sanc, if your sanc if missing a piece for example).  It also comes into play with our VIDEO-POSE (where sanc operators dont get paid if they run inferior nodes, ie low proc count and low hard drive size):

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

If you run that command from a browser you should see everyone that your node connected to.
Note that the 64 processor machine is my home desktop but its not always on, so it would be a prime example of one getting POSE banned.
And I see your new node has 6 procs, way to go man.

We will also have other VIDEO-POSE rules (like hashes per sec) so that people cant cheat this etc.  I think when the sidechain is released we can also test that a node is fully synced too.  (For now however we do ensure the node can do 1MM HPS, that the hard drive is 399gb or greater and 6 proc count) so that this is very fair...

Pretty cool to see this stuff coming into fruition. I mean one thing talking about it, another ball game to test it out.  On the sancs what do the "FullyQualified":false}]   mean? 
I noticed some of the nodes had  true or false.

Well i saw that you wrote more in the post :

And so how does this actually work for users?
The way it works for users is when the user hits our global CDN (thats our load balancer), this load balancer pushes the traffic out to one of our 'fully qualified bms nodes' (they get fully qualified when their reverse dns record is established and they are synced), and when that video request starts, it is only for seconds 1-5 of the video.  Each 5 seconds are re-evalutaed and the video is streamed from whichever node has the piece.  So a 20 min video might have 200 pieces, and each 5 sec piece is streamed independently from a different sanc (it is not designed for one sanc to stream an entire video but rather each piece is evaluated as the video is played, and pulled from the sanc that has it).

22

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: April 22, 2022, 02:32:41 PM »

Evenin.

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?

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 

23

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: April 22, 2022, 07:11:47 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
 

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

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.   

24

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: April 18, 2022, 04:56:31 PM »

Evenin.

I have also done some testing on this  BBP drive.

https://wiki.biblepay.org/BBP_Drive

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:

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.

25

Announcements & Fundraisers / Re: Third fundraiser for Water Wells in Pakistan

« on: April 15, 2022, 06:08:49 AM »

First week update

For the first week we have raised 450 USD  or 32.14% of the goal , thanks for donating.

26

Active Discussions / Re: June 2022 - TestNet Release - Exodus

« on: April 15, 2022, 04:24:39 AM »

Mornin!

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

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

Thanks.

27

Announcements & Fundraisers / Third fundraiser for Water Wells in Pakistan

« on: April 13, 2022, 02:24:58 PM »

Status update, as of 22 of May the goal of 1400 USD have been met.
This project has been fully FUNDED do not donate thank you

I want to thank all of you for making projects like this happen. Thank you and may God bless you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------




Hello Biblepay community. This time we are seeking donations for seven water wells in rural Pakistan.

From 2020 onwards Biblepay has donated funds for 29 water wells in partnership with Paani Project  https://www.paaniproject.org/

I believe that we in the western world take things like fresh water for granted, just turn the water tap and thats it. If we have the funds and the means to help others, children, families then i think thats a privilege, a way for us to show compassion.

Matthew 10:42  And if anyone gives even a cup of cold water to one of these little ones who is my disciple, truly I tell you, that person will certainly not lose their reward.”


So whats the goal of the fundraiser?

Each of the Tube wells costs 200 USD.
The goal is to get enough funds for 7 wells to be built. A total of 1400 USD


 Like in previous fundraisers, once the goal has been achieved i will send the funds over to Rob and let him handle the rest of the process.

Below you can find the link to the page with all the previous wells that biblepay has sponsored.

https://foundation.biblepay.org/Wells

Biblepay donation adress :

Code: [Select]

BDkBhuuLtRgzZHenK43xaod5i9FsM5J651 

If you would like to donate in another crypto currency just give me a shout and i will see if i can fix it.
I will do a weekly update on how the fundraiser is going.

Thanks all, God Bless!

28

Mining / Re: Sudden Connection Errors

« on: October 09, 2021, 01:18:08 PM »

Evenin Haze.

Yeah if pool goes down its good to have backup set up.
If you want check out my guide how to setup backup pool: https://www.reddit.com/r/BiblePay/comments/m5rezk/how_to_add_failover_pool_in_xmrig/

Have a good one.

29

Mining - Resolved Issues / Re: Reward for solomining BBP.

« on: October 09, 2021, 01:08:45 PM »

Evenin.

If your machines work as they should the the reasons would be higher difficulty and that your "luck" has gone down.
If you look at difficulty charts you can see it was high difficulty 06 october for example.

you can check historical difficulty at: https://chainz.cryptoid.info/bbp/#@diff

30

TestNet Discussion Archive / Re: December 2021 Release - Barley - TestNet - BiblePayCore - Next Release

« on: October 09, 2021, 12:58:42 PM »

Evenin Brother Rob.

Test Case #5

Q1. What is the name of your NFT so we can buy it?


The name of my NFT is called: Take me home, country roads


Q2. Did you buy the NFT successfully, and you can see the NFT in your nft list?


Indeed, bought back  footprints in the sand.

Code: [Select]

Success


You have successfully purchased NFT 25cf90e3d9f4ed22abf3010f44d8536c59261ca6ab2ac5c09b91547336b1d3d4 on TXID 25cf90e3d9f4ed22abf3010f44d8536c59261ca6ab2ac5c09b91547336b1d3d4!
Q3. Were you able to Edit your NFT and can you see that your NFT is now visible in the NFT marketplace?


Edited worked just fine changed the prices aswell as reposted the NFT to the marketplace.

I noticed that someone bought another of my NFT "take me home, country roads" 
well my balance went from 200 000tBBP to 225 000tBBP so it looks successfull to me.
It showed up in invoices aswell.