16
TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« on: December 18, 2017, 10:02:32 PM »Just won for the first time. It was also a 'doubleblock'.
congrats ! I'm still emptyhanded
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Just won for the first time. It was also a 'doubleblock'.
You're welcome I wonder what will happen in the next couple of days, since we both haven't 'won' anything yet.
Nice to hear it already worked.
I found the fix that Alex posted. I'll just post it anyway for future reference:
https://bitcointalk.org/index.php?topic=2388064.msg26467807#msg26467807
Did you also restart your masternode with the 'masternode start-alias' function?
Anyway, there is a fix that I also applied when it didn't work. It involves generating a new private-key. Let me just try and find it
just applied WIN apdate and restaarted both MN and controller. still
"UPDATE_REQUIRED" andCode: [Select]"vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service": "2:40000",
"status": "Not capable masternode: Invalid protocol version"
./biblepay-cli getinfo
{
"version": 1000609,
"protocolversion": 70712,
"walletversion": 61000,
"wallet_fullversion": "1.0.6.9",
I also had that problem with a previous update. It will probably fix itself when you start the masternode from the upgraded wallet.
"vin": "CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )",
"service": "2:40000",
"status": "Not capable masternode: Invalid protocol version"
./biblepay-cli getinfo
{
"version": 1000609,
"protocolversion": 70712,
"walletversion": 61000,
"wallet_fullversion": "1.0.6.9",
That's cheap indeed I wonder what the hashrate will be.
I've been using your hyperexpert suggestion for my masternode. Working great so far
Yes I am doing that. The question is does it impact Masternodes and two, what is the ideal setting for those who are using Vultr.
Hi Tiras,
It should be very similar to testnet. Once the mandatory is released we will have a certain block number announced where the Sanctuaries actually enable themselves. You can still send the escrow to the address early, and get the VM ready. But the masternodelist wont populate until after that block number kicks over.
Once that kicks over, the sanctuaries should start talking to each other and voting to pay each other. We will also have a separate block number for the first superblock. I think we will need to space that out to give time for the new nodes to acclimate themselves (maybe 15-25 days later).
We also need to remember to send instructions for people to switch their watchman-on-the-wall configs over to Prod.
Rob
I think klondike already answered but I wanted to add:
The masternode requires a status of "999" before it actually listens to our commands (I know, pain), so add this into the process:
After rebooting a masternode wait until 'mnsync status' shows 999, then issue the commands from the controller like start-many etc.
I did prove the other day that you do not have to restart a masternode (physically) when it says new start required. You can do the start-many and it will respond, as long as its already synced.
Another words life in prod should be like this:
As days go by, and no upgrades are being pushed out: If you ever see new start required, you go to your controller and issue the start-many command.
Reboots should only be necessary when upgrades (to the software) are required.