Bible Pay

Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Hmm am i on a different chain? I seem to have lost the tBBP you sent....

I had to stop the controller wallet to lock the outputs and when i restarted ( several times), the balanced was not updated.

Im still in sync on all my nodes:


15:20:49

getblockhash 5888


15:20:49

e66d1015bc4847c20fae2e73d9bd6d9655d0ceca85e0c0e9b0cc5bda9267b735


32
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 24, 2019, 02:26:56 pm »
Well, I think it was the reboot that did it.  After poring through the code yesterday on that non default port stuff, the code uses the testnet default port if its missing the port #.

But more specifically in our case, I think what happens is we set up a sanctuary, we run it, and if the pro-tx is sent after the sanc boots, (I think) the sanc actually starts up and goes to enabled, but -- I could be wrong about this -- but I think the activeMasternodeInfo (this is the struct that displays its status) isnt actually updated until you reboot.

My big question on that will actually need an answer soon for apollon, because they want us to provision a deterministic sanctuary without asking them to reboot the node :).  So we will have to figure this out for sure soon.

Hmm am i on a different chain? I seem to have lost the tBBP you sent....

I had to stop the controller wallet to lock the outputs and when i restarted ( several times), the balanced was not updated.
33
Thank you for the advice.

All mine were still waiting for ProTx but when i added the port to the IP and restarted it immediately went to ready, so the port ( even if default 40001) is needed in the conf.

Iíll try a non standard port later tonight.

Well, I think it was the reboot that did it.  After poring through the code yesterday on that non default port stuff, the code uses the testnet default port if its missing the port #.

But more specifically in our case, I think what happens is we set up a sanctuary, we run it, and if the pro-tx is sent after the sanc boots, (I think) the sanc actually starts up and goes to enabled, but -- I could be wrong about this -- but I think the activeMasternodeInfo (this is the struct that displays its status) isnt actually updated until you reboot.

My big question on that will actually need an answer soon for apollon, because they want us to provision a deterministic sanctuary without asking them to reboot the node :).  So we will have to figure this out for sure soon.

34
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 24, 2019, 12:27:03 pm »
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.

Thank you for the advice.

All mine were still waiting for ProTx but when i added the port to the IP and restarted it immediately went to ready, so the port ( even if default 40001) is needed in the conf.

Iíll try a non standard port later tonight.
35
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.












36
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 24, 2019, 05:41:28 am »
Thats awesome you are firing up 5!  Thanks!  Yeah, Im firing up 3 sancs + 1 controller, so we should have most of the bases covered this time.

I sent something like 12 mil-13 mil I believe to you.

EDIT:

I forgot an important note for everyone; Oncoa can you please do this also;
please delete your SAN/prayers*.* files and restart (just delete the whole directory SAN if you want), and then you will see that ABN isn't required.

This is because in testnet, our sporks are cached (until they get replaced with a new value).  Since we restarted the chain, the wallet thinks its still in ABN required mode.

(ABN is currently not required in testnet).

EDIT 2:

Yes, our hashes match, great job!

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.
37
Starting testnet from scratch

cli getblockhash 5682
42358d51bdb4eba605c37d78c623b68febb3126f2bcaf77c9e5db92429ea603a

New address:
ye4XGGwV9wWupZMV1Fqaxi3KLoHmxKB27G

I cannot mine and accumulate tBBP due to ABN. Can you please send enough for setting up of Sancs if thatís required. Thank you.

Thats awesome you are firing up 5!  Thanks!  Yeah, Im firing up 3 sancs + 1 controller, so we should have most of the bases covered this time.

I sent something like 12 mil-13 mil I believe to you.

EDIT:

I forgot an important note for everyone; Oncoa can you please do this also;
please delete your SAN/prayers*.* files and restart (just delete the whole directory SAN if you want), and then you will see that ABN isn't required.

This is because in testnet, our sporks are cached (until they get replaced with a new value).  Since we restarted the chain, the wallet thinks its still in ABN required mode.

(ABN is currently not required in testnet).

EDIT 2:

Yes, our hashes match, great job!

38
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 23, 2019, 06:06:58 pm »
Starting testnet from scratch

cli getblockhash 5682
42358d51bdb4eba605c37d78c623b68febb3126f2bcaf77c9e5db92429ea603a

New address:
ye4XGGwV9wWupZMV1Fqaxi3KLoHmxKB27G

I cannot mine and accumulate tBBP due to ABN. Can you please send enough for setting up of Sancs if thatís required. Thank you.

I have 5 VPS synced and ready.

http://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

39
Active Discussions / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Last post by oncoapop on September 23, 2019, 03:50:11 pm »
Starting testnet from scratch

cli getblockhash 5682
42358d51bdb4eba605c37d78c623b68febb3126f2bcaf77c9e5db92429ea603a

New address:
ye4XGGwV9wWupZMV1Fqaxi3KLoHmxKB27G

I cannot mine and accumulate tBBP due to ABN. Can you please send enough for setting up of Sancs if thatís required. Thank you.

40
BiblePay - TestNet
1.4.6.3-Mandatory upgrade for TestNet

- Add checkpoint @ 5000 to enforce new testnet chain
- Make enforcement of sanctuary port # configurable.  Set sanctuary port enforcement to OFF (false).  This allows us to test creation of new sancs on non-standard ports in both Mainnet & Testnet.
- Implement Sanctuary Raise (from 25% to 35%) and GSC budget reduction to 25% from 30% (https://forum.biblepay.org/index.php?topic=435.0) @ block 8400 in testnet & TBD in MainNet
- Merge Prod changes into Develop up to 1.4.4.7
- Switch TestNet to 7 minute blocks (1 min blocks up to block 5000 to get us started quickly)
- Change chainparams to enable deterministic DIPS at block 5000, QT at 5000, ABN at 5000, however DIP3 enforcement is set at block 8400 (this gives us 3400 blocks to set up deterministic sancs after block 5000); we must have 3 sanc LLMQ quorums after 8400
- Added Chinese bible reader to QT
- Added exec masterclock RPC command
- Added masternode genkey legacy command for Apollon - to help support deterministic sancs in this branch


We are on block 5500~ or so.


Pages: 1 2 3 [4] 5 6 7 8 9 10