Bible Pay

Read 19430 times

  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #615 on: July 30, 2019, 08:31:35 pm »
Dear Rob,

I just have three VPS running in TESTNET. I did have one sanc but it is now banned, I have no idea how to get it unbanned. I restarted it to no avail. How does one get banned, other than not running bbp daemon?

Code: [Select]
{
 "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
 "service": "45.62.239.200:40001",
 "state": "POSE_BANNED",
 "status": "Masternode was PoSe banned"
}

The VPS is up and running and port appears to be open
Code: [Select]
telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to sanc2.myseqtools.com<http://sanc2.myseqtools.com>.

mnsync status
{
 "AssetID": 999,
 "AssetName": "MASTERNODE_SYNC_FINISHED",
 "AssetStartTime": 1564531134,
 "Attempt": 0,
 "IsBlockchainSynced": true,
 "IsSynced": true,
 "IsFailed": false
}

If you want to check my machines, you can see the automatically polled hashes of my three machines at any time on:
http://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

They are pretty puny VPS  so one or more may be offline syncing or updatingÖ

Cheers,
Oncoapop

Hi Oncoa,

Nice hashes, so it looks like we are in agreement on that block hash (for your 3) plus mine.

As far as getting pose banned, you can get banned if:  Your masternodeblsprivkey does not match your deterministic.conf private key, or if you transmitted the same IP on more than one pro-tx, or if you are using the 'externalip=' setting in your wallet, or if your node is out of sync and acting strange in the quorums.  You would have to defer to the dash docs I pasted above for the rest of the reasons (as I am not familiar with the others yet).

If your not sure after reading this, I have found it is very easy to do this to recover:

Spent your collateral Tx in the controller wallet
Create a new public key for a new sanc
Create a new legacy sanc using the new address
Perform the upgradesanc command on it

I did that and Im chugging fine.

You can use the same address as long as you spend the old sanc funds first.  (Unlock them to spend them, spend them, then spend a new amount for the new sanc).




  • oncoapop
  • Jr. Member

    • 76


    • 9
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #616 on: July 31, 2019, 12:39:39 pm »
Hi Oncoa,

Nice hashes, so it looks like we are in agreement on that block hash (for your 3) plus mine.

As far as getting pose banned, you can get banned if:  Your masternodeblsprivkey does not match your deterministic.conf private key, or if you transmitted the same IP on more than one pro-tx, or if you are using the 'externalip=' setting in your wallet, or if your node is out of sync and acting strange in the quorums.  You would have to defer to the dash docs I pasted above for the rest of the reasons (as I am not familiar with the others yet).

If your not sure after reading this, I have found it is very easy to do this to recover:

Spent your collateral Tx in the controller wallet
Create a new public key for a new sanc
Create a new legacy sanc using the new address
Perform the upgradesanc command on it

I did that and Im chugging fine.

You can use the same address as long as you spend the old sanc funds first.  (Unlock them to spend them, spend them, then spend a new amount for the new sanc).

This would only happen in testnet but i lost / destroyed my controller wallet with my VPS and hence the collateral is locked and hence I cannot recreate the sancs using the same IP as you mentioned without spending the collateral which is not possible without the wallet!

Iíll have to destroy the VPS and recreate it with new A fresh IP and start from scratch. This might take awhile... sorry.



  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #617 on: July 31, 2019, 01:34:26 pm »
This would only happen in testnet but i lost / destroyed my controller wallet with my VPS and hence the collateral is locked and hence I cannot recreate the sancs using the same IP as you mentioned without spending the collateral which is not possible without the wallet!

Iíll have to destroy the VPS and recreate it with new A fresh IP and start from scratch. This might take awhile... sorry.

Oh ok, yeah you can't spend the collateral then, so you cant free that node the easy way, right.

Well, anyway, the other way to do it is if you have the deterministic.conf file (this has the bls private and public key in it and the original pro-tx-txid), you could send a  ProUpServTx, (because sending a new pro-register-tx with the same IP results in bad-protx-dup-key error), but you could only do this if you had all the pieces saved from deterministic.conf (proTxHash, blsPrivKey) - see this section for future reference :  https://docs.dash.org/en/stable/masternodes/maintenance.html#updating-masternode-information


Well anyway I hope you have a Vultr Snapshot then you can rebuild without all that work.  Good luck.


PS: Can you please try the quick sync from zero when you rebuild so we can test that?


« Last Edit: July 31, 2019, 01:37:30 pm by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #618 on: July 31, 2019, 01:37:02 pm »
I just updated the OP with "low hassle sync from zero". 

I also got windows to sync with this method last night, so it will be trivial to make a prod snapshot soon.




  • oncoapop
  • Jr. Member

    • 76


    • 9
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #619 on: July 31, 2019, 06:26:12 pm »
Oh ok, yeah you can't spend the collateral then, so you cant free that node the easy way, right.

Well, anyway, the other way to do it is if you have the deterministic.conf file (this has the bls private and public key in it and the original pro-tx-txid), you could send a  ProUpServTx, (because sending a new pro-register-tx with the same IP results in bad-protx-dup-key error), but you could only do this if you had all the pieces saved from deterministic.conf (proTxHash, blsPrivKey) - see this section for future reference :  https://docs.dash.org/en/stable/masternodes/maintenance.html#updating-masternode-information


Well anyway I hope you have a Vultr Snapshot then you can rebuild without all that work.  Good luck.


PS: Can you please try the quick sync from zero when you rebuild so we can test that?

Set it up using the binaries from MIP and the quick sync script and it was fast and effortless! Used the Dash method from scratch (bit more complicated) and here it is...
 
Code: [Select]
"33ff087061fad94af7e4f1f73ff56af47f9b34e802cd845f5cf765b13944d453-1": {
   "proTxHash": "520ebc4e8fb36d335e89d3527c88e0096bb605983efbd339f78d17be12ce453e",
   "address": "104.167.113.181:40001",
   "payee": "yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq",
   "status": "ENABLED",
   "posescore": 100,
   "posescoretries": 0,
   "posescoresuccesscount": 0,
   "lastpaidtime": 1564615177,
   "lastpaidblock": 182751,
   "owneraddress": "ygXsP7NRxDJtKKqRc2i1JXvxKZmXysYf76",
   "votingaddress": "ya5TqeZC7GRbibSzT8jbfHCLEQNTKT6LDL",
   "collateraladdress": "ydbZ7ppEEbq28Awyt2iQXTnM3JSn5fxKHF",
   "pubkeyoperator": "90856729abbe57866ec136e1505b59bf2fb5c399e04581df8264ba0ce49709cccd8c3e74c45ea1815e71572d602110c0"
 }


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #620 on: July 31, 2019, 06:32:57 pm »
Set it up using the binaries from MIP and the quick sync script and it was fast and effortless! Used the Dash method from scratch (bit more complicated) and here it is...
 
Code: [Select]
"33ff087061fad94af7e4f1f73ff56af47f9b34e802cd845f5cf765b13944d453-1": {
   "proTxHash": "520ebc4e8fb36d335e89d3527c88e0096bb605983efbd339f78d17be12ce453e",
   "address": "104.167.113.181:40001",
   "payee": "yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq",
   "status": "ENABLED",
   "posescore": 100,
   "posescoretries": 0,
   "posescoresuccesscount": 0,
   "lastpaidtime": 1564615177,
   "lastpaidblock": 182751,
   "owneraddress": "ygXsP7NRxDJtKKqRc2i1JXvxKZmXysYf76",
   "votingaddress": "ya5TqeZC7GRbibSzT8jbfHCLEQNTKT6LDL",
   "collateraladdress": "ydbZ7ppEEbq28Awyt2iQXTnM3JSn5fxKHF",
   "pubkeyoperator": "90856729abbe57866ec136e1505b59bf2fb5c399e04581df8264ba0ce49709cccd8c3e74c45ea1815e71572d602110c0"
 }

Thats awesome.  I see .181 in my sanc list now also, with 0 POSE.
Just a guess, but maybe it was your masternodeblsprivkey on the old one, not matching?  In both of my cases it was using externalip=.  I found after I recreated without that, they stay up. 

Yes, good to know you were able to use the Dash method.  The pro for the dash method is you have more control over the operator and voting keys (which, we can expose in the future in our upgradesanc command, for more versatility).  The con is you have to remember to save those private keys in a file by yourself.  (In the case of a person who has a lot of sancs, the deterministic.conf might be convenient.  In my case, the deterministic was more useful for me to write a monitoring program to manage the sancs later - I need to loop through them and control them, etc.)

Great, we have 5 sancs now enabled!  We can start testing chainlocks pretty soon.
MIP, is yours up?

Have I forgotten to answer any questions about .14 other than making a test-list?

Btw, how did you lose your testnet controller wallet, was it a rabid animal, or a mad family member?

« Last Edit: July 31, 2019, 06:34:41 pm by Rob Andrews »


  • oncoapop
  • Jr. Member

    • 76


    • 9
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #621 on: July 31, 2019, 08:42:40 pm »
Thats awesome.  I see .181 in my sanc list now also, with 0 POSE.
Just a guess, but maybe it was your masternodeblsprivkey on the old one, not matching?  In both of my cases it was using externalip=.  I found after I recreated without that, they stay up. 

Yes, good to know you were able to use the Dash method.  The pro for the dash method is you have more control over the operator and voting keys (which, we can expose in the future in our upgradesanc command, for more versatility).  The con is you have to remember to save those private keys in a file by yourself.  (In the case of a person who has a lot of sancs, the deterministic.conf might be convenient.  In my case, the deterministic was more useful for me to write a monitoring program to manage the sancs later - I need to loop through them and control them, etc.)

Great, we have 5 sancs now enabled!  We can start testing chainlocks pretty soon.
MIP, is yours up?

Have I forgotten to answer any questions about .14 other than making a test-list?

Btw, how did you lose your testnet controller wallet, was it a rabid animal, or a mad family member?

Hmm, my sanc has the external IP in the biblepay.conf:

Code: [Select]
addnode=testnet.biblepay.org
addnode=dns1.biblepay.org
addnode=dns2.biblepay.org
addnode=dns3.biblepay.org

rpcuser=XXX
rpcpassword=XXX
rpcallowip=127.0.0.1
rpcport=9998
daemon=1
listen=1
server=1
daemon=1
externalip=104.167.113.181
maxconnections=256
masternode=1
masternodeblsprivkey=XXXX

Not that exciting, Iím afraid. I thought each time in testnet we start from scratch so I didnít pay much attention to the wallets. Anyway, I managed to resurrect the 239.200 as the VPS was still around.


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #622 on: July 31, 2019, 09:04:53 pm »
Hmm, my sanc has the external IP in the biblepay.conf:

Code: [Select]
addnode=testnet.biblepay.org
addnode=dns1.biblepay.org
addnode=dns2.biblepay.org
addnode=dns3.biblepay.org

rpcuser=XXX
rpcpassword=XXX
rpcallowip=127.0.0.1
rpcport=9998
daemon=1
listen=1
server=1
daemon=1
externalip=104.167.113.181
maxconnections=256
masternode=1
masternodeblsprivkey=XXXX

Not that exciting, Iím afraid. I thought each time in testnet we start from scratch so I didnít pay much attention to the wallets. Anyway, I managed to resurrect the 239.200 as the VPS was still around.

Oh good on the reason :), haha, OK.
Yes, I remember the two I had trouble with had the port in there also and yours does not.
It makes me think you could comment out yours, as it might not be used.



  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #623 on: August 17, 2019, 08:38:21 am »
** TestNet Update **

Just to give everyone an update as to what is going on:
Of course our TestNet testing is vital and is not being deprioritized by any means.

We still want to shoot for roughly an end of October timeline to at least have our next codebase ready for deployment (in case something accelerates the need for the release, as its important to be safe and on the ball).

The reason for the recent lack of posts is I've been in 'programming hermit' mode working on some of the promised features for EOQ 3.  For example BIPFS (BiblePay IPFS).

I will be posting a wiki very soon explaining all of this.

The schedule is on-track for an on-time release, so I feel confident we can begin testing chainlocks very soon and get back to more testnet as well.

Some of the code in BIPFS requires some code changes in the core in testnet btw (leisure changes).

Note that Dash recently had to tweak .14 in Prod due to some hackers spamming prod transactions.  We will pull these things in ASAP and ensure we are up to date.



  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #624 on: September 03, 2019, 03:01:25 pm »
1.4.6.2 - Mandatory Upgrade for TestNet

- Merge in Prod changes up to 1.4.4.6
- Merge in Reindex fix (MIP)
- Add feature to slow mining of empty blocks in TestNet only
- Add feature to upload nested folder into BIPFS
- Add transparent background image for windows toolbar


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #625 on: September 03, 2019, 04:07:18 pm »
Let me know when our sancs have upgraded, because I would like to set the spork to slow the testnet chain down to keep the testnet chain from generating thousands of empty one minute blocks (causing longer sync times in the future).



  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #626 on: September 03, 2019, 04:21:38 pm »
Let me know when our sancs have upgraded, because I would like to set the spork to slow the testnet chain down to keep the testnet chain from generating thousands of empty one minute blocks (causing longer sync times in the future).

I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.



  • MIP
  • Developer

    • 227


    • 26
    • February 13, 2018, 11:55:52 am
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #627 on: September 04, 2019, 10:47:50 am »
I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.

I switched off mine in the Vultr VPS. I made a snapshot so maybe I can take it back again.

Apart from that, what else do you need from me to test?


  • oncoapop
  • Jr. Member

    • 76


    • 9
    • October 23, 2018, 12:31:17 pm
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #628 on: September 04, 2019, 04:40:58 pm »
I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.

I have the following machines on testnet but all my sancs have been pose banned so i need to reactivate them but this back-to-school week is a bit busy for me.

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


  • Rob Andrews
  • Administrator

    • 2031


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)
« Reply #629 on: September 05, 2019, 09:10:14 am »
I have the following machines on testnet but all my sancs have been pose banned so i need to reactivate them but this back-to-school week is a bit busy for me.

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

Thanks guys!

Yeah, one of my 3 was pose banned too.  I have been deliberately waiting to see if it revives by itself.

As the Dash-Evo code hints at an automatic revival process; but - when I read about people who were POSE banned, they generally recreate their nodes.  But that doesnt make too much sense to me, because there is a strict control on not being able to re-use the same IP.

I have one well known working method to undo a POSE ban - but its like using a cannon - you can spend the output and recreate the sanc using upgradesanc - and that is allowed - because the network sees it as spent and undoes the lock on it first - and allows recreation.

Before I recreate my third sanc, let me do some more expirimentation.