Show Posts
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.
Dash's notes have the instructions to do it, but those notes are very complicated (to create a deterministic sanc from scratch).
Yes, the sanc throws a warning right now if the masternodeblsprivkey is missing, but it still starts. (Using the masternodeprivkey).
Thats great!
Hey everyone I want to mention something important.
Before we enable dip15 (deterministic masternodes), we need to copy our 'masternodeblsprivkey' to our cold sanctuary biblepay.conf file (just like we usually copy the masternodeprivkey over there).
This is not used until we flip dip15. As I believe the moment we flip dip15 the sancs will rely on this privkey to sign all the messages (and thats likely why we had hundreds of failed votes yesterday once I flipped it for a couple mins).
So either way its mandatory that we copy the key to the sanc before dip15, so lets make that part of the upgrade to deterministic process.
I also forgot to mention this is the main reason I added the deterministicsanctuary.conf file - so you can open it back up and get the value out of it (or write a script to copy the value to the sanc).
I agree with you. Ill stick it out for a while and keep the chain, lets see how we do.
(I'll still put these 3 new features in however, for the next mandatory).
Thats awesome man! So to elaborate a little more:
1) Dash allows a sanctuary owner to specify where future rewards go (IE they allow you to tell the wallet a specific address to receive sanc rewards). This is useful if you are trying to make an untraceable wallet.
2) Dash allows any designated public key to be a voting delegate. This means a friend can vote on a sanc poll for you if you provide their pubkey.
To make this easy to start, the upgradesanc command fills those two things in for you.
To find out how we filled them in, go to receiving addresses, look for:
Yoursancname-D and Yoursancname-V.
The D is the address biblepay set up for your rewards.
The V is the address we created for your voting.
The vote-many and vote-alias automatically finds your V address to vote from (no changes are necessary there).
The rewards will start coming in to the D address (theoretically), lets check that.
I can confirm that the D and V addresses have been created. You're doing a great job Rob!
*** UPGRADING A LEGACY BIBLEPAY SANCTUARY TO A DETERMINISTIC SANCTUARY ***
Guys, go ahead and try this.
1. You must have a *cold* sanc (that means your sanctuary doesn't have the locked funds in it and you have a controller wallet with the funds locked, and the old sanctuary works (IE its probably ENABLED right now), and your controller wallet has a masternode.conf file.
2. From your controller wallet, go to the RPC terminal and type:Code: [Select]exec upgradesanc sanctuary_name 0(where 0 means dry run, and sanctuary_name is the name of the sanctuary (the first field) in the masternode.conf file).
3. Check the output of that command and make sure there are no errors. If so continue to the next step.
4. From the controller wallet, RPC terminal type:Code: [Select]exec upgradesanc sanctuary_name 1Ensure this command does not throw an error.
If the results are successful, you will be in the dip3 sanctuary tab (from the Sanctuaries page | Dip3 sancs).
Note that we create a deterministicsanctuary.conf file for your convenience (this is a biblepay feature). We automatically add all your dip3 sancs to that file.
This will be useful if you have more than say 10, then you can write a script to pull values from this file and do things like update remote configs, run remote commands etc. Its also highly useful if you need to access your BLSprivkey or BLSpubkey, or voting information.
That seems to have worked
This usually happens if one of the mn* files wasnt deleted, I would delete the gov* and the .dat files and restart the controller, let the mnsync status go to 999, then restart it.
Then post your sancs ip and I will also see if it says enabled on my end too.
It's in PRE-ENABLED mode now because I restarted it. My sancs IP is the 84.92 one.
Sent, but Im not sure that we have enough sancs for this to work properly, but we will see.
I just enabled InstantSend autolocks. I believe this feature allows us to instantly send money and get an immediate 6 confirms for the receiver.
If anyone wants to paste their address I can send some IX to you ?
Great, well I see 6 enabled now - thats great. For some reason only 4 voted. Maybe 2 upgraded synced and shut off.
I think these two are easy ones, but Im not sure
1) To start biblepay-qt:
cd ~/biblepay-evolution/src/qt
./biblepay-qt -conf=biblepaytest.conf
(I believe you were one level down)
2) To get past the rpc error:
cd ~/biblepay-evolution/src
./biblepayd
....
In another terminal, run
./biblepay-cli
(The RPC is thrown if biblepayd is not running)
Of course I needed to run it from the qt path. I did it like that in the past, but somehow I forgot.
bible@bible-GA-A55M-DS2:~/biblepay-evolution/src$ ./biblepay-qt
bash: ./biblepay-qt: No such file or directory
error: Could not locate RPC credentials. No authentication cookie could be found, and no rpcpassword is set in the configuration file (/home/bible/.biblepayevolution/biblepay.conf)
Thanks (and also thank you Togo)!
I already tried deleting everything (including the 'SAN' folder) except my wallet.dat a couple of times, but that didn't help. I now upgraded to the latest version and put the gen=0 in my biblepay.conf. Let's see how that goes
I don't have a lot of spare time at the moment, but I'm going to try and keep up with you guys!
Please try 'gen=0' in the biblepay.conf first, then see if it reaches the top?
It is probably trying to mine every time the blocks pause.