Hello Rob.
I noticed that on 30th march that i received 2 utxo staking rewards in testnet, both said smart-contract-reward i believe.
Not sure if its normal?
On another note i figure i will see if i can manage to set up 1 masternode on friday.
I have read some diffrent guides and believe i should be able to do it, if not i will bring in the big guns, (you)
Anyhow have a good week.
Could you please paste the two txids so I can relate to them? Cause sometimes its mining - other times the 48 hour delay - or could be older utxostakes sent before we rejumped etc.
On the sanc, I highly recommend this method (this is how i do it):
- Send 4,500,001 to a new address labeled earlz1
- Create a masternode.conf file in /testnet3 directory, with the fields shown in it (earlz1 ip:port sanc_collateral ordinal)
- After a couple blocks type 'exec upgradesanc earlz1'
- After another block 'exec revivesanc earlz1'
That will create stuff in the deterministic.conf file. In there, you can copy the bls_priv_key over to your new sanctuary biblepaytest.conf file (that file I mean is the biblepaytest.conf file located on the target sanctuary vm). Set:
masternodeblsprivkey=xxxxxxxxxx
Btw, Vultr recently added clipboard functionality to the hosts! I use it in this case.
Then restart the new sanc and make sure it ssays 'masternode status' = all the stuff that is supposed to say.
Let me know if this helps! Its a lot easier than dashs method(s) of doing a whole page of stuff, imho.
I will try to make more test cases too. Thanks.
Btw, you can run your testnet sanc side-by-side one of your prod rented hosts too - they dont interfere. Thats what I am doing, I have 1 testnet sanc on each of my first 3 vultr hosts that host prod biblepay sancs.
Also, one other helpful hint: On your 'home controller', thats the bbp machine that "öwns" the collateral for the sancs (the one you vote from) you should have the Sanctuaries tab enabled (settings | checkbox check for that). You will need to look in there to see the new sanc on the list. Important note: Because of our POOS system, the sanc might say POOS banned. Its OK in testnet - its still not POSE banned unless its status is > 800. In testnet, its OK to have a status of between 0 and 700 (0 means healthy, 700 means non-paid but healthy). 900 means POSE banned. 900 is not ok. When we hit 900, we need to 'revivesanc' again. That only happens when your sanc is Offline during quorums etc.
