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

[bible_pay]

We still need help in TestNet to test Cameroon:

https://forum.biblepay.org/index.php?topic=391.new#new

We only have one tester so far (and hes on a road trip).  

what do you need to have? if only spinup several wallets, then maybe we can create some automation

We don't really need much hashpower over there as POBH and ABN are the same, but we could use some brains over there to regression test everything prod does.

And also to sponsor a couple simulated children through cameroon one testnet - and see the daily payments.  It would be good to have some eyes on the GSC payments without children compared to GSC participants with testnet children.

We can talk more about it in that thread if you want to join.

[capulo]

thats the problem i have not enough free time, but i can provide hw and so

[bible_pay]

** 70734 Sanctuary Update **


As far as health of our network, we are now healthy.  Since we started enforcing GSC-contract votes to originate from 70734 or higher (IE the minimum GSC protocol version), we now have 99% positive votes for the GSC contract.

As of this morning the 50 sanctuaries running 70732 still have not upgraded, but I believe their payments have stopped (as 70734 nodes vote against them, they are moving to new_start_required).

I did double check with GIN to ensure they were running the latest, and they did already upgrade to 70734, so they are not the root of the problem.

So I'm not sure who the mystery investor is - if they are an institution or what the situation is, but hopefully they will upgrade now that they have been disbanded from the network.

I took a look at watchman-on-the-wall (our integrated superblock payment manger) and everything looks good (we are 30 blocks away from our last non-deterministic governance superblock).

Once this passes, we can look toward the next phase of our mission - upgrading to deterministic sancs.

[yaronidon]

Once this passes, we can look toward the next phase of our mission - upgrading to deterministic sancs.

please explain what is the meaning of "deterministic sancs."

[bible_pay]

Once this passes, we can look toward the next phase of our mission - upgrading to deterministic sancs.

please explain what is the meaning of "deterministic sancs."

Deterministic sancs are DIP3 compliant sancs, that are created with a valid on-chain pro-tx collateral transaction (in contrast to a normal masternode.conf file broadcast).
Once we have our sancs upgraded to DIP3, we will have a new masternode (sanc) list (its a new protocol), new protocol for voting, and new protocol for sanc payments.

The sanc payments in the deterministic world use Dash-Evo's new code to loop through POSE (IE non POSE banned) sancs for payments.
They also are certified to participate in the new LLMQ quorums in the future.

This step is necessary because non-deterministic sancs will be retired sometime between August and our next release (as the next BiblePay release, following Dashs 0.14 branch lead) requires all deterministic to implement the next features (like ChainLocks).

Once you upgrade to deterministic, your sanc will be listed in the DIP3 tab.

Later in the next version, the other tabs (for non-deterministic) will be removed.

[bbptoshi]

seems like the wiki is down... how to upgrade sanctuary? i am doing 'git pull origin master' but it says its already up to date.

[bible_pay]

seems like the wiki is down... how to upgrade sanctuary? i am doing 'git pull origin master' but it says its already up to date.

Its up:
https://wiki.biblepay.org/Imminence_of_Jesus

When you say upgrade sanctuary, are you running an older protocol version (getinfo) < 70734?

[bbptoshi]

yes, running 70732

[bible_pay]

yes, running 70732

Just a guess, but you may have to delete the old biblepay dir:
rm ~/biblepay -r

Then to upgrade the sanc:
cd ~/biblepay-evolution (or wherever this is) sometimes its cd /biblepay-evolution (etc).
git pull origin master
make
(This assumes you built it from source before).

We are up to v.1.4.3.9:
https://github.com/biblepay/biblepay-evolution/commit/693d141d983af2d1982847d51eaa85946ce7e858

[bbptoshi]

yes, running 70732

Just a guess, but you may have to delete the old biblepay dir:
rm ~/biblepay -r

Then to upgrade the sanc:
cd ~/biblepay-evolution (or wherever this is) sometimes its cd /biblepay-evolution (etc).
git pull origin master
make
(This assumes you built it from source before).

We are up to v.1.4.3.9:
https://github.com/biblepay/biblepay-evolution/commit/693d141d983af2d1982847d51eaa85946ce7e858

Thanks.  I did the 1 click sanctuary script and got version 1.4.3.3.  What would I do in this case?

[bible_pay]

yes, running 70732

Just a guess, but you may have to delete the old biblepay dir:
rm ~/biblepay -r

Then to upgrade the sanc:
cd ~/biblepay-evolution (or wherever this is) sometimes its cd /biblepay-evolution (etc).
git pull origin master
make
(This assumes you built it from source before).

We are up to v.1.4.3.9:
https://github.com/biblepay/biblepay-evolution/commit/693d141d983af2d1982847d51eaa85946ce7e858

Thanks.  I did the 1 click sanctuary script and got version 1.4.3.3.  What would I do in this case?

If you compiled from source, you can do what I posted.  If you ran from the binary choice you would have to ask MIP as I've not used the script since the very first days (and its changed since then).

[slovakia]

MIPs script again download and again run it

[bible_pay]

** UPGRADING YOUR SANCTUARIES TO DETERMINISTIC (DIP3) **


Recently we explained during our getting started with Evolution guide steps that at height 129,150 we would start upgrading our sancs to deterministic.

The goal is to finish this process by the end of July (before our July superblock emits).  So we have 28 days to perform this.
This will allow us to emit a superblock entirely from dip3 based sancs (and set us in a position for the next step in August).

Here are two resources we can start with containing instructions to upgrade your sanc from legacy to deterministic:
How to upgrade a legacy Sanc to a deterministic Sanc using the BiblePay upgrade tool (built in the core wallet):
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch the Dash way:
https://docs.dash.org/en/stable/masternodes/setup.html#option-2-registering-from-dash-core-wallet

Very important info for you to know:
If you use the BiblePay upgradesanc tool, BiblePay will automatically create a file called deterministic.conf in your Data directory (this is where your masternode.conf file is).  We will automatically add a new row to this file every time you upgrade a sanctuary to deterministic.  This file will contain your sanctuary name, ip, port, collateral txid, pro-tx txid, bldsrivkey, blspubkey, and all other pertinent tx info on one row.

Note that you should back up this file occasionally, in case you destroy your cold sanctuary (VMSs).  This will allow you to retrieve the masternodeblsprivkey, which is required to recreate a deterministic sanctuary!  So remember, back up your deterministic.conf along with backing up your wallet.dat.  If you create sancs using the Dash method above you will need to manually copy your masternodeblsprivkey over to notepad and create a backup system to back up your notes.

Summarizing the process:

1.  We assume you have a sanctuary named 'biblical1'.    This sanctuary exists in your masternode.conf file.
2.  Type 'exec upgradesanc biblical1 0' into the RPC.  If an error is thrown, post here and we will help.  Otherwise continue to step 3.
3.  Type 'exec upgradesanc biblical1 1' into the RPC.  This results in many lines of output with all the keys etc.
4.  Edit your remote hosted sanctuary biblepay.conf file (your cold sanc VMS's biblepay.conf file).
5.  Add an entry:  masternodeblsprivkey=nnnnnn  (replace the n's with the blsprivkey which is found in the output of the command.  Alternatively you can also get this value from viewing the deterministic.conf file we created in your datadir).
6.  Remove the existing 'masternodeprivkey=nnnnn' from the file (or comment it out by putting a # in front of it).  Note that this step is optional, as it will no longer be used anyway.
7.  Reboot the remote sanctuary.  
8.  Verify the sanctuaries masternode status is ENABLED.

How do I upgrade many sanctuaries at once:

If you own a massive number of sanctuaries, you can run the upgradesanc command on all of them first, then write a program to loop through your deterministic.conf file on the controller wallet, and for each entry, connect to the remote host (by IP found in the data row), edit the remote cold sanc masternode.conf file, adding the masternodeblsprivkey=nnnn entry in the file.  Then rebooting the remote sanc via script.

** Recommendation **

It is recommended that each of us upgrade one today and take a look at the network and verify everything looks fine, then continue with more.

[dave_bbp]

I just tried it and I get this:

Code:


exec upgradesanc MN1 0

No funds at specified address (special transaction error) (code -32603)

What specified address is it referring to?

[bible_pay]

I just tried it and I get this:

Code:


exec upgradesanc MN1 0

No funds at specified address (special transaction error) (code -32603)

What specified address is it referring to?

I believe any address you have funds in; you need at least 1 bbp to run the command.  Please ensure the wallet is unlocked and has at least 1 bbp plus the 4.5MM locked collateral for the sanc in the same wallet.

[bible_pay]

I just tried it and I get this:

Code:


exec upgradesanc MN1 0

No funds at specified address (special transaction error) (code -32603)

What specified address is it referring to?

I believe any address you have funds in; you need at least 1 bbp to run the command.  Please ensure the wallet is unlocked and has at least 1 bbp plus the 4.5MM locked collateral for the sanc in the same wallet.

NOTE: There was an error in the Dash link above - I corrected it (it was expired).

Note2:  I will try to upgrade one of my prod sancs now using upgradesanc.

[MIP]

Thanks.  I did the 1 click sanctuary script and got version 1.4.3.3.  What would I do in this case?

This means something went wrong when replacing older binaries, as the current published version is 1.4.3.9.
Try to stop daemon manually then, download latest script version and then run

./masternode-setup.sh -u -n

This should run an unattended update.

[bible_pay]

** SOUTHXCHANGE IS ONLINE **

[MIP]

I tried to upgrade a sanc and after


21:47:15

exec upgradesanc MN1 0

I saw a list of json data

Code:

{  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary MN1 with IP 209.xxx.xx.xx:40000 with TXID xxxx",
etc.

But then I got an error here
21:47:15
exec upgradesanc MN1 1
bad-tx-type (code 16) (code -1)

Still I see a tx happening despite the error.

[bible_pay]

I tried to upgrade a sanc and after


21:47:15

exec upgradesanc MN1 0

I saw a list of json data

Code:

{  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary MN1 with IP 209.xxx.xx.xx:40000 with TXID xxxx",
etc.

But then I got an error here
21:47:15
exec upgradesanc MN1 0
bad-tx-type (code 16) (code -1)

Still I see a tx happening despite the error.

Hmmm, let me try to upgrade one now first and see if it does this.