Messages

31

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

« on: July 12, 2023, 12:19:49 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

32

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

« on: July 07, 2023, 11:09:56 PM »

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

33

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

« on: June 09, 2023, 02:23:17 AM »

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.

34

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

« on: July 10, 2022, 06:01:49 PM »

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

35

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.

36

Archived Proposals / Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020

« on: July 27, 2020, 04:08:02 PM »

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.
 

37

Archived Proposals / Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020

« on: July 24, 2020, 02:47:43 PM »

Ok, I made your 89c* sanc and your 07ba* sanc as if you didnt pay, so now you should see the POOS level increase.
Btw, you can see your sanctuary POOS level in the QT wallet - in the Sanctuaries UI.

You should then start receiving only 1 bbp for those two sancs.

EDIT:  I just made the biblepayd (non-qt non-gui wallet) also show the POOS level in 'masternodelist full' - this will be in the next release, but its not a high priority to get it out yet (until we find a bug, etc).

1. "613535d6ea651c5b5c3c224ab782409da6a873b8c10dda3216c6da9a6098f7de-1": "       POSE_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595486691  52832 45.62.240.90:19998",
Result of update: (initially updated, tried again and this is the second result. Sanc
  "service": "45.62.240.90:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned")
error code: -26
error message:
18: protx-dup

2.   "7392277be75eac0b90f2faea5a023565d1b408ecc045a17074d49bc227532a60-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595467363  52785 104.167.116.179:19998",
Result of update:
error code: -25
error message:

3.  "900c710e527cd634ca2c0e3d30d8f0a9983f0b8a5b93964adb1b8a7f5902b034-1": "       POOS_BANNED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 1595468292  52786 104.167.108.63:40002",
Result of update:
error code: -25
error message:

Note the error messages on the sanc themselves
BiblePay Core RPC client version 1.5.1.8
> sanc status
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:19998",
  "state": "POSE_BANNED",
  "status": "Masternode was PoSe banned"
}

Don't know reason for ban - mandatory upgrade (POSE) or POOS when queried from sanc itself.

38

Archived Proposals / Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020

« on: July 22, 2020, 04:02:20 PM »

Ok great, lets start by pretending you paid for the first month and just fell behind on payments to cameroon-one.

Please give me a couple sanctuary public keys so I can put your bios in non-payment mode.

My 3 that are enabled
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.108.63:40002
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 104.167.116.179:19998
 ENABLED yXmJk6MpzoSej7dThs99kLr92Bt6BYy1YQ 45.62.240.90:19998

39

Archived Proposals / Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020

« on: July 22, 2020, 02:25:03 PM »

I made biographies for the 6 sancs that are POOS banned in testnet.

So please try to revive now.

Sancs are synced and revived. There are 7 enabled sancs on testnet now.

40

Archived Proposals / Re: POOS Testnet Thread (Proof of Orphan Sponsorship - Sanctuaries) - September 2020

« on: July 22, 2020, 12:33:56 PM »

Ok, this version is ready for testnet.

Hi Rob. Sorry for the absence. I have synced my sancs but unable to revive them
error code: -2
error message:
Safe mode: Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade.

Even though they are all on the correct blockhash
cli getblockhash 52500
12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1

41

TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION

« on: March 05, 2020, 03:44:39 AM »

-erase chain and resync on mainchain - ok

>cli getblockcount
180392

>cli getblockhash 180392
7b90b5fbb0cfbfd06b4c47981ebca34c7b06a909b970a979e34f4a8074c2fe0e

(Matches with CryptoID explorer)

BiblePay Core version 1.5.0.4 (64-bit) appears to hash on main chain

>getmininginfo

Code: [Select]

{
  "blocks": 180393,
  "currentblocksize": 1330,
  "currentblocktx": 1,
  "difficulty": 4694.69442578912,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 4,
  "networkhashps": 537711.1247468939,
  "hashps": 3518.900343642611,
  "minerstarttime": "03-05-2020 09:41:24",
  "hashcounter": 1024,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true
}


42

TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION

« on: March 05, 2020, 03:37:50 AM »

BiblePay Core version 1.5.0.4 (64-bit)
Windows qt

- syncs to the top of main chain
getblockhash 180368
32d69ae1ce3aec5415a01d07704f1f6253bd6e471fe636d6541b8381f2c11176
- wallet loads fine
- 186 sancs listed in sanc tab
- Leaderboard appears to be correct

-erase chain and resync - taking a very long time (will report back later)

-erase chain and resync on mainchain - ok

>cli getblockcount
180392

>cli getblockhash 180392
7b90b5fbb0cfbfd06b4c47981ebca34c7b06a909b970a979e34f4a8074c2fe0e

(Matches with CryptoID explorer)

43

TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION

« on: March 05, 2020, 01:19:55 AM »

Yea, good point on the traffic and stuff.  When Vitalik called me on my cell phone back then I really didn't understand the gravity of the situation - at the time he sounded like he was designing a rocket engine, but it was so advanced... it's something I'll have to discuss some time.

So yes on the donate, I did put the 'suggestion' in the code, but yes good idea to make it on the display: I added it to the next version.

10-4 on the new users, that will be very good.

So an update for everyone, I did add the spork last night, and we can test that during the next release.  I believe I will be able to unit test that change locally so no rush.
I also erased my chain and resynced my local node, and I see it made it to the top block without a problem, so I believe this latest patch is all we needed for prod.

One side note guys that could help:  If anyone wants to try mining (solo mining in the wallet) against Prod in this random-x QT wallet (not randomx mining, regular POBH mining against prod).  Just make sure this 1.5.0.4 version syncs to the top in prod and solo mines (-erasechain=1 first).  This is for our regression testing (to ensure we didnt break any existing features before the RX cutover height).  We need to see that prod masternodes can also be seen in the Sanc list, and that the governance data is visible in this branch.

Finally, I am just about ready to create a wiki page for the game plan for 'corporate whitebranding'.  The reason this ties into testnet is we could potentially start the initiative (that replaces all of biblepay's branding information with monikers).  Monikers allow CSS, logos, brand slogans, narratives, and coin phrases to be replaced with the corporations identity.  I'm just mentioning this because if the plan becomes solid, we can potentially test part of this in testnet while we wait to upgrade to RX.  On a side note, I'm still shooting for a potential end of March roll-out.  (We can't upgrade more than once per quarter due to the exchange rules).  However I also don't want to release 'too much' good information at once for BiblePay as that might rocket us accidentally up to the top 5 coins too quickly, etc.

BiblePay Core version 1.5.0.4 (64-bit)
Windows qt

- syncs to the top of main chain
getblockhash 180368
32d69ae1ce3aec5415a01d07704f1f6253bd6e471fe636d6541b8381f2c11176
- wallet loads fine
- 186 sancs listed in sanc tab
- Leaderboard appears to be correct

-erase chain and resync - taking a very long time (will report back later)

44

TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION

« on: March 01, 2020, 08:41:27 AM »

Yes, I see the underlying issue (dash's very strict policy for sanc-quorums to never be allowed to go out of sync, nor recover), but one thing I want to say, my sancs actually never did go out of sync.  They made it to the top height, so I assume this problem occurs when you tried to resync your sanc from zero (it shouldnt have went out of sync by itself).  Or did one of yours die by itself?

Anyway, I have added a special rule to allow us to get through this situation, and Im releasing leisure now.

If you are on the self compiled nodes you can go ahead and try to upgrade to 1.5.0.4 and resync from zero and our sancs should agree then.
Over the next 15 days or so we should clearly see if we all stay in sync, as I think the true nature will come out.  Im attempting to leave chainlocks on straight through to the end of testing.

We will also make a release for this.

So in summary, anyone who tried to re-sync from zero *after* we enabled chainlocks gets hosed at the 29680 or so height, due to the strict rules.  After the next upgrade anyone can resync but also should stay in sync with chainlocks on.

Ah... got to know. I updated and rebooted my servers and somehow decided to sync from zero but I remember that at least one was already stuck on block 29680. So in production, we should never resync sancs from zero once chainlocks are in place? what would happen if by mistake we do, we have to recreate the sanc?

Anyway, I used the zip as the binaries do not appear to be ready; all my sancs are now synced to 31991 with hash 200ddb5167d7e601d0c4359f8db2a85b940d91150207ced941de7b905da784d7. Thank you.
 

45

TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION

« on: February 29, 2020, 02:41:31 AM »

** Chainlocks Enabled in TestNet **

We have 7 active sancs; let's see how things go in testnet with chainlocks enabled.

I see our last GSC superblock worked correctly also. (IE the leaderboard).

I have only one of my sanc that made it to block 30912 (but the block height on the NOMP pool is 31689)
The rest of my other sancs appear to be stuck on 29680 and nothing appears to be able get them to pass that block (ie sync from zero, reassess chains etc)

>cli getchaintips (from the one on block 30912)

Code: [Select]

[
  {
    "height": 31749,
    "superblock": false,
    "hash": "27c3e670d07c122c6702ae7a964a236f77b420a9c500083a8093e075cc4c6cb8",
    "difficulty": 0.01117096611785549,
    "chainwork": "00000000000000000000000000000000000000000000000000016ce13d3eec99",
    "branchlen": 837,
    "forkpoint": "c7bf513d861d05b59afd542901820122ecb4417aef84d0c5a95097b20ebf868d",
    "forkheight": 30912,
    "status": "headers-only"
  },
  {
    "height": 30912,
    "superblock": false,
    "hash": "c7bf513d861d05b59afd542901820122ecb4417aef84d0c5a95097b20ebf868d",
    "difficulty": 0.03535418162797442,
    "chainwork": "00000000000000000000000000000000000000000000000000016ce0455291bd",
    "branchlen": 0,
    "forkpoint": "c7bf513d861d05b59afd542901820122ecb4417aef84d0c5a95097b20ebf868d",
    "forkheight": 30912,
    "status": "active"
  },
  {
    "height": 30416,
    "superblock": false,
    "hash": "9da1ee9b4ca5b2f008ebfd3052692b7b076129fe48d6cddf62eec303bccab594",
    "difficulty": 0.0191308836772212,
    "chainwork": "00000000000000000000000000000000000000000000000000016cdf8bfe8b47",
    "branchlen": 1,
    "forkpoint": "49b60d1911e62bbc40c0269c1e572abcb2c611bed679977d48385c06beaf5fa2",
    "forkheight": 30415,
    "status": "valid-headers"
  },
  {
    "height": 30234,
    "superblock": false,
    "hash": "5d75d3c2bd9228add55addb36da784b3524434122f59b24041eec5b4f22f7f89",
    "difficulty": 0.011886394687722,
    "chainwork": "00000000000000000000000000000000000000000000000000016cdf2cc32730",
    "branchlen": 1,
    "forkpoint": "1f8b5ab00cd917d1407409a6ab4b32721a9873be77c3984254689ed3942c0201",
    "forkheight": 30233,
    "status": "valid-headers"
  }
]