Thank you for the tBBP - I have set up 2 DIP3 sancs.
104.167.118.24:40001
45.62.239.200:40001
Although they both appear to be enabled on the masternode list (and both receiving block rewards on consecutive blocks 5802,3), masternode status on both say
"state": "WAITING_FOR_PROTX",
"status": "Waiting for ProTx to appear on-chain"
I struggled for quite a while in the set up as unlike previously, this time the VoteAdd must be the same as the OwnAdd. As can be seen from my post (on Jul 31, 2019, for example, my last sancs had different addresses for both, as I set them up from scratch using the dash method.
Thank you also for the tip about the deletion of the SAN directory, the VPS are now mining without ABN.
I can see both of your sancs as enabled (however in the phase we are in, we arent in LLMQs yet, so they wont be pose banned anyway until after block 8400). Anyway when I right click on those I can see the Pro-tx. Did your status ever update in the sancs themselves to Enabled?
I just created 3 sancs. In my case, one of the three already went to enabled (in the masternode status in the sanc) with all of its info. In the other 2, I also see waiting for pro-tx to appear on chain. So Im going to leave mine like this and see if that changes later.
In my case, I used our upgradesanc command. Heres how I created a deterministic using the legacy with upgrade method:
- Send 4,500,001 to myself using QT wallet
- Type masternode outputs - copy the TXID and ordinal
- Edit the controllers testnet3/masternode.conf file
- Past IP:Port MNP txid ordinal (in the file)
- Type 'upgradesanc sancname 0' . Verify this will work.
- Type 'upgradesanc sancname 1'. Copy the masternode bls priv key to the Sanc "biblepay.conf" file. Also ensure the sanc has masternode=1 in it.
- Reboot the sanc so it uses the bls priv key.
On another note, Im testing an upcoming feature that will let Apollon host deterministic sancs, and let Apollon (or biblepay users) host sancs on nonstandard ports.
I wanted to see - do we need any code changes in testnet (or in the upgradesanc command) to support nonstandard ports.
So I did this: In the sanctuary itself, in the biblepay.conf, add "port=nnnn" where nnnn is your non standard port #. In my case I used 39998 (as you can see from the sanctuary list now).
Then in the masternode.conf file, I changed 40001 to 39998 (in my controller wallet).
I see our upgradesanc command did honor that without any changes, and - because we have recently merged in a change that allows nonstandard ports for pro-tx the tx was broadcast.
I was able to successfully create two more sancs on non standard ports.
So now you all should be able to see in the masternode list: ports 40001, 39998, 39999. Lets see if these nodes survive.
Recent Posts
. So we will have to figure this out for sure soon.