This setup lets you run testnet side by side your prod node or masternode, and allows you to avoid problems finding a separate testnet configuration file.

To set up a hot testnet sanctuary:

Ask a forum member for 500,000 bbp.Launch the wallet.Type: masternode genkeyCopy the key to the 'masternodeprivkey=xxxx' in the biblepaytest.conf file.Send 500,000 bbp to one of your own receiving addresses.

Restart the wallet.

Testing objectives:

- Ensure monthly (weekly in testnet) superblock is capable of paying a dispursement, ensure getgovernanceinfo is correct- Ensure daily PODC superblock is also capable of dispursing, ensure exec getboincinfo podc budget is correct (The above two tests verify the cascading superblock bug will be mitigated)- Ensure wallet boots without memorizing prayers on the primary thread, but yet in the background thread (this is the speedy bootup feature)- Ensure active proposal list view is available (Bhavani)- Ensure active proposal list vote works (Bhavani)- Ensure active proposal list pie chart works (Bhavani)- Test new PODC mature consensus feature (Rob will explain) ( // Mature means we stake a point in history (one timestamp per day) as Yesterdays point, and mature means it is older than that historical point. // This should theoretically allow the sancs to come to a more perfect consensus each day for PODC elements: DCCs (Distinct CPIDs), UTXOWeights (UTXO Stake Amounts), TaskWeights (Task confirmations), and Unbanked Indicators.)

I just wanted to mention, I was shooting for making this a little easier on everyone who already has a running Prod sanctuary: To possibly save you some money and just run the testnet instance in the same VMS.

I tweaked the OP post with a hint that allows you to run the testnet instance side by side on your prod sanc.But whatever is easier for all of you by all means.

The need for at least 5 hot sancs in testnet is primarily because we need to test the ability for the wallet to emit both a daily and weekly superblock and verify the chain does not throw any errors, and of course that requires the hot sancs to actually vote.

So do we need 1.1.2.5 on both Sanc and windows controller wallet or just in Sanc?

Edit: ok I read again and it's about testing on a hot wallet Sanc.

You really just need a hot sanctuary running in testnet - if you dont mind voting from a QT hot sanc. But if you do have a controller testnet QT wallet then it will make testing Bhavanis prod proposals the same as prod.

When I try to associate my CPID's I get a 'already in chain' message. Is this because this is still the old testnet? If so, I'll re-associate. I presume it's no problem to have the same CPID on both testnet and prod, right?