BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

No, thats cool, I dont mind going into more detail where need be.  We also do have some wiki guides on some of these concepts and when one is discovered that is really necessary to document we do make an end-to-end tutorial as a wiki.

First of the reason there are 3 flavors of Sancs now is because some people cant afford 4.55MM bbp for a sanctuary; so now we offer one flavor of sanc for 455,001 bbp and also a Temple for 45MM bbp.  They each have really the same reward (IE the altar pays 10%, the Sanc 100% and the Temple 1000%).

With a sanc you get a bigger reward because its doing the randomx mining in the pool, and you end up with the entire block reward every time your deterministic sanctuary is scheduled for payment. 

If you are an investor you will get 50% of the reward, but an active hosted sanc on a VM, you get 100%.

I would suggest to go back to the release where we ask you to create a deterministic sanctuary, and simply ask questions on any area that is confusing and I can try to help.
Most of this documentation was already established dash; so any terminology on the basics, you can get that from googling that term and Dash Masternode.

Weve simply enhanced and extended those Masternodes to become deterministic sancs with different sizes, and we ported the block miner into the sanc.  And we added the 50% active/passive rules.

Here is the guide to set up a sanc:
https://wiki.biblepay.org/Create_Sanctuary

Just let me know what you need help with.  If you simply want to set up one without renting an actual VM (IE as a passive investor) you just follow the guide, but you point it to your own IP address.

Substitute the 4,500,001 with 450001 to create an altar.

"Substitute the 4,500,001 with 450001 to create an altar."

Can it be any number, like 555,007?

Also, you said you imported the miner into this process.  Is this going to take more CPU/RAM than normal staking?

"Substitute the 4,500,001 with 450001 to create an altar."

Can it be any number, like 555,007?

Also, you said you imported the miner into this process.  Is this going to take more CPU/RAM than normal staking?

Hi CB and Good to hear from you and God bless you.

Because of many areas of the code, where we do collateral detection, it has to be exactly one of the three numbers (IE 4500001,450001,45000001).

The sanctuary will use more CPU only (not extra ram) during mining, yes, but its only doing it one thread in a non competitive way, so its something like 10% of the processor on a VM (not 100%).

I upgraded too.

Can someone help correct the info so I can set up a sanc and start staking?  The first step at least seems to have changed with the new wallet:

I asked Google: How to set up a sanctuary with BiblePay

I got:

Create Sanctuary
How to create a deterministic Sanctuary


Ground Rules: You must have a controller wallet (this is your home wallet that is used to manage one or more sanctuaries). The lines below marked with controller must be run by your home wallet. The Sanctuary wallet is your VPS that runs the actual Sanctuary Software.



Step 1:
From the Controller Wallet, launch Biblepay QT. Go to File | Receiving Addresses.

xx This step now seems wrong.  I don't see that under file.   So I just selected Receive to get a wallet address.

Create a new address for your sanctuary (by clicking new), then edit it and label it with a good name (for example, sanc1) Write this sanctuary name down in notepad. Copy that address to your clipboard. Close the dialog.
Step 2:
Now we will fund the sanctuary. Go to Send. Paste the Address of the Sanctuary (from the first step) in the To box. Populate amount 4,500,001. Send.

Am I required to have 4,500,001 as an amount or can I put in a lesser amount?

I guess the rest is correct, if not, please let me know.

Step 3:
Go to the Transaction List, and find the transaction that you sent. Double click on it. Copy the transaction ID to your clipboard. Now we need to find out the TXID ordinal. Launch Notepad, and paste the txid in notepad and label it Collateral TXID. Now go to Tools | Debug Console. Type:
getrawtransaction txid 1
The command will show the details of the transaction you just sent. Scan the output of this command for the leg of the transaction that has an amount of 4,500,001. Once you find that leg, copy the "n" value of it. Usually, this will be 0 or 1. Copy that "n" value to notepad and label it "txid-ordinal".

Step 4:
Now we need to add an entry to the Controller wallets masternode.conf file. In mainnet, this file is located at ~/.biblepay/masternode.conf. In TestNet, this is located at ~/.biblepay/testnet3/masternode.conf. Note that on windows, you need to replace ~/.biblepay with %appdata%\biblepay. Nano this file. We need to store a new entry in it like this:
sanctuary_name sanctuary_vms_ip:sanctuary_port mnp collateral_txid collateral_txid_ordinal
You should replace sanctuary_name with the name that you wrote in notepad. Replace vms_ip with the ip address of your sanctuary. Replace port with 40000 for mainnet, or 40001 for testnet. Leave mnp as is. Replace collateral_txid with the TXID in notepad. Replace txid_vout_ordinal with the TXID ordinal from notepad. Save the file. Exit nano.

Step 5:
Now we need to upgrade the sanctuary to deterministic from the Controller wallet. From the RPC console, type:
upgradesanc sanc_name
Note! If the response says: 'unable to find funds at address nnn', this simply means you need a little BBP to cover maintenance. In this case send 1000 bbp from your controller wallet to the address on the screen (copy it to clipboard) and send to it, then wait 3 blocks then try again.

If the command is successful, it will emit about 10 lines of technical details about your new sanctuary. You are primarily concerned with the BLS public and private keys. Copy the BLS public and private keys to notepad and label them the same names.

Step 6:
Now we are ready to spin up the actual VMS sanctuary. From the VMS Sanctuary, first install either biblepay-qt or biblepayd (the sanctuary will run from either one). Most people use biblepayd. cd ~/.biblepay From here, we need to enter the BLS_PRIVATE_KEY in the biblepay.conf file! nano ~/.biblepay/biblepay.conf (this is for mainnet). For Testnet: nano ~/.biblepay/biblepaytest.conf Insert the following line
masternodeblsprivkey=nnn
Replace nnn with your actual bls_private_key (from notepad). Save the file.

Step 7:
Now we can start the sanctuary. Start the sanctuary, wait for it to sync, then type:
masternode status
At this point if it says READY: you have a perfectly running sanctuary. Now all you need to do is monitor the POSE status from the controller, and ensure it stays at 0. If it goes up, you can always revive your sanctuary with 'exec revivesanc sancname'.

Correct, everything is still good in that doc to my knowledge (I created one relatively recently using the same old steps).
Except you are right, the receive address is in Receive now due to latest version of rebase, yes.
Just let me know if there is a specific area where you get a hang up now.

Thanks for the replies, Rob.

I just wanted to mention, Bololex is not allowing Doge deposits.  A bit hard to trade on there without funding the wallet with DOGE.  Also, other deposits and withdraws are disabled that I've noticed. 

Thanks for the replies, Rob.

I just wanted to mention, Bololex is not allowing Doge deposits.  A bit hard to trade on there without funding the wallet with DOGE.  Also, other deposits and withdraws are disabled that I've noticed.

Ahh, I didnt realize that, thanks.  I did see that they installed some type of auto trading bot (AMM) on bololex, (similar to the way SX used to work). 
Maybe it is good for volume in the long run as people want to liquidate things.

I hope they are going to stay in business.

So on the bright side since Trump won, this will be a very good time for Crypto.
All, keep praying that a Christian exchange owner steps up and lists us on a large exchange, for more volume.


In the mean time Ill start putting the roadmap together.
With the goal of outlining all of our ideas and where they are in a succinct way.

We will be having a mandatory upgrade in about 10 days (trying to give plenty of notice on this).

The primary driver is to finally seal up the LLMQ (Instantsend) - Quorums code to be fully operational.

A little back story on this.
We always had deterministic masternodes and LLMQs, since Dash released those.  However there is a mix of problems between the version we were on prior to the rebase and where we are today.

At one point, when we had the hybrid (non deterministic Sanc plus LLMQ bolted on), instantsend worked fine.
It was during the period where our sanctuary count decreased and people started to run Investor nodes, where the quorums started to be less reliable.
This caused instant send to revert to non deterministic rules (IE it worked, but it used Dashs legacy code and not LLMQs).
Dash eventually removed that code, which caused our LLMQs to switch between deterministic (IE pure LLMQ instantsend) and LLMQ being off (if a quorum wasnt active at that height).

To remove all the bore of this story, over the last 9 months of releases Ive been trying to ensure these are 100% reliable and always on.

Reason being is, instantsend and chainlocks are actually required for unchained.biblepay.org and our sidechain and for NFTs to work correctly (if you lose instantsend, the experience becomes severely bad for the user, simply because they buy an NFT and it takes 20 mins to lock the tx.  Meaning, they cant see the NFT on the screen for 20 mins.  (The rule prevails that says do not accept a tx in a block until at least 1 block has passed after it was mined).  For us, thats a minimum of 14 mins (7 min block times) which is not acceptable.

So finally, InstantSend is fixed.  Release will be out this weekend.

Biblepay v0.21.8
Mandatory Upgrade - Cutover Height 555,000


- Make LLMQ quorums ignore investor nodes (more reliable quorums)

Release:
https://github.com/biblepay/biblepay/releases

Dear Rob,
I managed to recreate my sanc. However, it appears that the controller wallet (Windows Biblepay-qt) displays that my sanc is in INVESTOR mode while the sanc itself shows READY. See attached screenshot. I checked that (at time of posting) almost all of the other sancs also appear to have the same status - INVESTOR.
Is this intended behaviour?
Thank you. Keep up the good work!
Blessings
oncoapop

Dear Rob,
I managed to recreate my sanc. However, it appears that the controller wallet (Windows Biblepay-qt) displays that my sanc is in INVESTOR mode while the sanc itself shows READY. See attached screenshot. I checked that (at time of posting) almost all of the other sancs also appear to have the same status - INVESTOR.
Is this intended behaviour?
Thank you. Keep up the good work!
Blessings
oncoapop

Dear oncoapop,
Are you directly connected to public internet or are you behind a NAT by router ?

What is the IP and port configured in your masternode.info because I have always the seame error:

"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "ERROR",
  "stat[/li][/list]
  "us": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."

Thanks for you help
Ale

Dear oncoapop,
Are you directly connected to public internet or are you behind a NAT by router ?

What is the IP and port configured in your masternode.info because I have always the seame error:

"outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "ERROR",
  "stat[/li][/list]
  "us": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."

Thanks for you help
Ale

Dear Ale,
Thanks for your question. I have them both behind NAT and also in a datacenter.

This is the one behind NAT.
$ cli masternode status
{
  "outpoint": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193-0",
  "service": "108.180.46.33:41000",
  "proTxHash": "f64ce28c46d989035dc00e48fd5c2906050d20ad471b9ef7188d3fc32e3365a5",
  "type": "Regular",
  "collateralHash": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193",
  "collateralIndex": 0,
  "dmnState": {
    "version": 2,
    "service": "108.180.46.33:41000",
    "registeredHeight": 551815,
    "lastPaidHeight": 552264,
    "consecutivePayments": 0,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
    "votingAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
    "payoutAddress": "BKcbU8zYxfHGfaytRowYQLkyVA1U2BDYx4",
    "pubKeyOperator": "a8aba6cd5915acb888c5b7c689808f015b1c417d7fa9edbf3042a1ee1168ba17446cfdb1f0b5492fcaf6924629d0081c"
  },
  "state": "READY",
  "status": "Ready"
}
To make this work, as an example, I needed to go to my router IP 108.180.46.33 (get this from whatsmyip.com) and map 41000 to an internal port 41000 in this case, on my internal server 192.168.1.16 (get this from ifconfig)

Add this to your biblepay.conf

externalip=108.180.46.33:41000
masternodeaddr=192.168.1.16:41000
port=41000
maxconnections=128
masternodeblsprivkey=......132b9d4ef47f91bdc7a692820e.....

Blessings
oncoapop

Dear Ale,
Thanks for your question. I have them both behind NAT and also in a datacenter.

This is the one behind NAT.
$ cli masternode status
{
  "outpoint": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193-0",
  "service": "108.180.46.33:41000",
  "proTxHash": "f64ce28c46d989035dc00e48fd5c2906050d20ad471b9ef7188d3fc32e3365a5",
  "type": "Regular",
  "collateralHash": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193",
  "collateralIndex": 0,
  "dmnState": {
    "version": 2,
    "service": "108.180.46.33:41000",
    "registeredHeight": 551815,
    "lastPaidHeight": 552264,
    "consecutivePayments": 0,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
    "votingAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
    "payoutAddress": "BKcbU8zYxfHGfaytRowYQLkyVA1U2BDYx4",
    "pubKeyOperator": "a8aba6cd5915acb888c5b7c689808f015b1c417d7fa9edbf3042a1ee1168ba17446cfdb1f0b5492fcaf6924629d0081c"
  },
  "state": "READY",
  "status": "Ready"
}
To make this work, as an example, I needed to go to my router IP 108.180.46.33 (get this from whatsmyip.com) and map 41000 to an internal port 41000 in this case, on my internal server 192.168.1.16 (get this from ifconfig)

Add this to your biblepay.conf

externalip=108.180.46.33:41000
masternodeaddr=192.168.1.16:41000
port=41000
maxconnections=128
masternodeblsprivkey=......132b9d4ef47f91bdc7a692820e.....

Blessings
oncoapop

Hi Oncoapop,

I believe you have everything set up correctly, because I can telnet to your port 41000 from my house, and as you show above you have the masternode status returning successfully.

The issue is within our code, we have specific requirements for non-investors:
if (nPort == 40000 || (nPort >= 10000 && nPort <= 10100))
    fPortPassed=true;

The public port has to either be 40000 (Prod), or 10000-10100 in Prod.

If its not in our docs, I will add a todo to put that in asap.
Sorry for the inconvenience.

Once you recreate your sanc on one of those ports, it should switch to non investor.

On a side note, it is possible to edit your deterministic.conf and masternode.conf (both entries) with the new port number and do an 'exec upgradesanc sancNN' and that should also change your port number on chain.

Good luck,
Rob

Dear Rob,

Thank you for that tip!

I changed my port using the command "protx update_service <protx_hash> "<ip:new_port>" <operator_privkey>" as the proposed "exec upgradesanc sancNN" command gave the error "bad-protx-dup-key (code -1)" and chatGPT gave me the solution (which I shared!)

Thank you - my updated sanc appears to be ONLY ENABLED SANCTUARY on the BBP Blockchain at the moment! Time to update my other sancs...

Blessings
Oncoapop

Hi Oncoapop,

I believe you have everything set up correctly, because I can telnet to your port 41000 from my house, and as you show above you have the masternode status returning successfully.

The issue is within our code, we have specific requirements for non-investors:
if (nPort == 40000 || (nPort >= 10000 && nPort <= 10100))
    fPortPassed=true;

The public port has to either be 40000 (Prod), or 10000-10100 in Prod.

If its not in our docs, I will add a todo to put that in asap.
Sorry for the inconvenience.

Once you recreate your sanc on one of those ports, it should switch to non investor.

On a side note, it is possible to edit your deterministic.conf and masternode.conf (both entries) with the new port number and do an 'exec upgradesanc sancNN' and that should also change your port number on chain.

Good luck,
Rob

Dear Rob,

Thank you for that tip!

I changed my port using the command "protx update_service <protx_hash> "<ip:new_port>" <operator_privkey>" as the proposed "exec upgradesanc sancNN" command gave the error "bad-protx-dup-key (code -1)" and chatGPT gave me the solution (which I shared!)

Thank you - my updated sanc appears to be ONLY ENABLED SANCTUARY on the BBP Blockchain at the moment! Time to update my other sancs...

Blessings
Oncoapop

Hi Oncoapop,

I do not see the same sanctuary view as you do.  On my end 50% of the regular sancs are up and 90% of the temples are up.

Please confirm that you have updated your sancs to the latest version?  V0.21.8 - Hamans Hanging II.  And your home node?


10:54:02
getblockhash 552842


10:54:02
0000013a9221fdd81e13939ffb22b2e7bc1ebb53ab6b8dc24ddd0bc77f588e1f


I do believe there is a problem on bololex and chainz however, probably due to the Sancs agreeing on the latest quorum rules.
I asked Chainz to reindex, and I sent the upgrade to bololex.

Can you please try stopping your sanc wallet, delete all files but wallet.dat and reindex from scratch? (This is different than a -reindex=1, I call it an erase chain).

I did confirm on two of my sancs, after an erasechain, I do agree with the hash above (IE nothing changed on my end before or after the erasechain, but it confirms the hash is correct as I agree on all my nodes, which is more than 6).

Note that 'revivesanctuary' should work, if you were synced.  The problem with protx update is it does not update the deterministic.conf file.

Have a good one,
Rob

Hi Oncoapop,

I do not see the same sanctuary view as you do.  On my end 50% of the regular sancs are up and 90% of the temples are up.

Please confirm that you have updated your sancs to the latest version?  V0.21.8 - Hamans Hanging II.  And your home node?


10:54:02
getblockhash 552842


10:54:02
0000013a9221fdd81e13939ffb22b2e7bc1ebb53ab6b8dc24ddd0bc77f588e1f


I do believe there is a problem on bololex and chainz however, probably due to the Sancs agreeing on the latest quorum rules.
I asked Chainz to reindex, and I sent the upgrade to bololex.

Can you please try stopping your sanc wallet, delete all files but wallet.dat and reindex from scratch? (This is different than a -reindex=1, I call it an erase chain).

I did confirm on two of my sancs, after an erasechain, I do agree with the hash above (IE nothing changed on my end before or after the erasechain, but it confirms the hash is correct as I agree on all my nodes, which is more than 6).

Note that 'revivesanctuary' should work, if you were synced.  The problem with protx update is it does not update the deterministic.conf file.

Have a good one,
Rob

Dear Rob,

Thank you. All my wallets have the same hash. One of my sancs on port 40000 appears to be READY, is on the "masternodelist status" list as ENABLED but appears on the wallet as INVESTOR. All the rest are ENABLED.

How do I use the "revivesanctuary" command to revive it?  Ah, it is exec revivesanc sancname.

Blessings
oncoapop