Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 130. (Read 243386 times)

Looks like they are coming back up now; about 140 out of 182 have re-propagated into the active sanc list (I think this takes about an hour).

I just tested one that I started (in my case I pushed Start-All), then went to the sanc itself, and it did start (masternode status) is fine now.

On a side note in this case no one should have to re-sync the whole chain, its just a re-synchronization issue of the masternode list data.

(IE mnsync reset will also help).

I think in an hour or two we will see 90%+ coverage again in enabled.

all Sancs are in pre-enabled status in controller GUI .

running "masternode status" on the Sanc returns "   "status": "Not capable masternode: Masternode not in masternode list""

attempting to start a sanc from the controller doesn't do anything .

I did try rebooting the sanc and re-downloading the blockchain as well .
It didn't help  either.

blockhash on controller and sanc:

19:02:46
getblockhash 129427
d053f86021908481059fbc65b5e8d257882c1d5cb5f097a0d949fef8cfdca947

If anyone in QT has trouble seeing their sanc list in the GUI, please reboot and ensure they are started.

any video tutorial for this hard things  
jesus,nobody understand again this steps

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

Yes, you are right, second time was with "1", it was a typo.

So I ran again in 129407 and got the same error.


Edit: despite the error, this transaction happens:

So, out of curiosity when you received the bad-tx-type, was it when you passed the "1", or did it also happen with "0" (dry run)?
The reason I ask, is I can successfully run the dry run but I havent run the "1" yet in my case.

So, I recently set DIP3 to officially start on block 129407 (spork 15).
Lets try again in one block and see if that was the problem?

22:54:09

exec upgradesanc MN1 1


22:54:09

bad-tx-type (code 16) (code -1)

Estado: 0/no confirmado, en el equipo de memoria, transmitir a través de 8 nodos
Fecha: 03/07/2019 22:58
Total de débito: -1.00000000 BBP
Total de crédito: 1.00000000 BBP
Comisión de transacción: -0.00243000 BBP
Cantidad neta: -0.00243000 BBP
ID de transacción: 6bec34a9adc797ac19e01d6b2b74cd633bcbc928ec3efaf6db1fcade8d98a2f4
Indice de salida: 0
Tamaño total de transacción: 243 bytes


Débito: -13.40463347 BBP
Crédito: 1.00000000 BBP
To: B7ppCVgaN1rymNBSdjK9SizCeVKf9JbNZt 1.0000 BBP
Crédito: 12.40220347 BBP
To: BNXLWXKEdxJt3g1mZzZDAhuAsTVUguNbkD 12.0000 BBP

Transacción:
CTransaction(hash=6bec34a9ad, ver=1, type=0, vin.size=1, vout.size=2, nLockTime=129407, vExtraPayload.size=0)
    CTxIn(COutPoint(29455945d3525106336b830431e24a0750c981ed5f56ff34af91f8cc9f77735a, 1), scriptSig=483045022100e59d21c5ddbc, nSequence=4294967294)
    CTxOut(nValue=1.00000000, scriptPubKey=76a9142504a897182268d83dbba658)
    CTxOut(nValue=12.40220347, scriptPubKey=76a914c6405c368080489426f265d5)

This is a long shot, but it cant hurt to try, could you please try going to coin control and check the row for the CHRISTIAN-PUBLIC-KEY, and then run the 'exec upgradesanc sancname 0' (dry run) again, and see if it actually emits?  If so, we have to relax the rules in the next version.

Status: 1/unconfirmed, broadcast through 9 nodes
Date: 03.07.2019 22:43
Total debit: -1.00000000 BBP
Total credit: 1.00000000 BBP
Transaction fee: -0.00243000 BBP
Net amount: -0.00243000 BBP
Transaction ID: 2f57d242c8e5cc4615d8375aaf17d43db32618b3cbe386a2d9cf7fbdda84b02a
Output index: 0
Transaction total size: 242 bytes

Height: 129407
Difficulty: 5010.29
Time: 07-03-2019 20:43:47
Subsidy: 5519.6978

Debit: -1.59708742 BBP
Credit: 0.59465742 BBP
To: BByCR19ExW8yUWZnj1A7SrvGrYyYtPSpSg 0.0000 BBP
Credit: 1.00000000 BBP
To: BC2kWHxwREa9htb34wutbwgxMFnPhyMBCE 1.0000 BBP

Transaction:
CTransaction(hash=2f57d242c8, ver=1, type=0, vin.size=1, vout.size=2, nLockTime=129332, vExtraPayload.size=0)
    CTxIn(COutPoint(a09af9d34b7065710682c4e14c6b550128c222015897122d05047cefa3c1394b, 1), scriptSig=47304402203afa0f2a4a2903, nSequence=4294967294)
    CTxOut(nValue=0.59465742, scriptPubKey=76a914527b08b965629bd94e916463)
    CTxOut(nValue=1.00000000, scriptPubKey=76a91453271202ceb79965ed4392d7)

Yep, it's there and has several thousand BBP in various denominations in it, which almost all date from 2nd or 3rd of July. There is one older input, but it's <1BBP.

Ok, we will try other things then.  The wallet does need the "CHRISTIAN-PUBLIC-KEY" to send 1bbp to, can you check to see if yours exists and has more than 1bbp in it?

(IE it hasnt been renamed or deleted right)?

Yes and yes, but still no luck.

1) You are running this from QT, correct?
2) Could you please ensure your coin control has absolutely no coins selected when you run the command?  If one coin is selected, it might be unable to fund the dry-run pro tx.

I tried to upgrade a sanc and after


21:47:15

exec upgradesanc MN1 0

I saw a list of json data


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.

Nope, that can't be it. My wallet is unlocked and has more than enough coins. The command actually initiates a "payment to yourself" each time I execute it:

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.

Status: 1/unconfirmed
Date: 03.07.2019 21:56
Total debit: -1.00000000 BBP
Total credit: 1.00000000 BBP
Transaction fee: -0.00391000 BBP
Net amount: -0.00391000 BBP
Transaction ID: a36e60b6e483cd42d6f47e8ae8091b28f10e7db86594d4b216686257d5f8666d
Output index: 0
Transaction total size: 389 bytes

Height: 129404
Difficulty: 2975.01
Time: 07-03-2019 19:57:18
Subsidy: 2868.8632

Debit: -1.00000000 BBP
Debit: -0.13399582 BBP
Credit: 0.13008582 BBP
To: BB5o9DyyrrwPJhwcKw4rX8csfhZdppQFHL 0.0000 BBP
Credit: 1.00000000 BBP
To: BC2kWHxwREa9htb34wutbwgxMFnPhyMBCE 1.0000 BBP

Transaction:
CTransaction(hash=a36e60b6e4, ver=1, type=0, vin.size=2, vout.size=2, nLockTime=129403, vExtraPayload.size=0)
    CTxIn(COutPoint(a09af9d34b7065710682c4e14c6b550128c222015897122d05047cefa3c1394b, 0), scriptSig=47304402203b690e40f5b571, nSequence=4294967294)
    CTxIn(COutPoint(dcdfae64eedf2c1037b84c38f3d09b651576cbce1bfd7dd042b69347c5f66974, 0), scriptSig=4730440220149688a0ea5378, nSequence=4294967294)
    CTxOut(nValue=0.13008582, scriptPubKey=76a91448c264bc9886d57c57516652)
    CTxOut(nValue=1.00000000, scriptPubKey=76a91453271202ceb79965ed4392d7)

I tried to upgrade a sanc and after


21:47:15

exec upgradesanc MN1 0

I saw a list of json data


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.

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