Messages

91

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 07, 2019, 05:54:33 PM »

Ok, I make the assumption you are also affected by the problem I pasted for Togo, so if you want to work quickly please self-compile and then retry your sanctuary revive or spend;  or alternatively please wait for 1.4.6.8.


I will work on this now for new release.

I’ll wait as compiling failed....

In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9965: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[1]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[1]: Leaving directory '/home/bbp/biblepay-evolution/src'
Makefile:11637: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

92

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 07, 2019, 05:18:16 PM »

Could you confirm what platform version this is, is this a linux qt build?  Or windows?

Self compiled or a binary?

Linux command line
cli -version
BiblePay Core RPC client version 1.4.6.7

binaries from
https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz

93

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: November 07, 2019, 05:08:35 PM »

Ok, with PODC 2.0 coming soon, lets not use the Christian Spaces thread for testing.

Lets focus on:
-reviving our sanctuaries
-reviving our state in testnet
-ensuring we are synced
-enabling WCG miners so we can utilize the CPID and credit RAC in testnet

In the mean time, I will add a command to the develop branch that allows us to send the pro_reg Update Service command (the BiblePay way) - that takes advantage of the deterministic.conf file, so we can revive our failing sancs.

Is this what chainlocks is all about? I cannot spend anything on any of my wallets in testnet. Hence am unable to revive my two sancs.

Error code:-4
Signing transaction failed

94

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 07, 2019, 04:56:33 PM »

Glad you are back dude, hey you can type 'exec revivesanc' and it should have the instructional command.

If not, IE if you are missing the blsprivkey, Ive learned its also pretty easy to just spend the output and recreate the sanc.  But the bls priv key is in the sanc itself in the config file, and right clicking on the sanc in the home host reveals the pro-tx-id.  The Sanc IP is of course, public already.

Sorry, I can’t revive my sanc Nor can I spend the transaction....

cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9
error code: -32603
error message:
No funds at specified address (special transaction error)

ok - I choose an address with funds
 "ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV": 9.93668000,

cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9 ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV
error code: -32603
error message:
Signing transaction failed

cli walletpassphrase
error code: -15
error message:
Error: running with an unencrypted wallet, but walletpassphrase was called.

95

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 06, 2019, 06:17:56 PM »

I think we need Oncoapop back, I see the POSE banned sancs are causing safe mode- Oncoapop are you available to unban?

I’m trying to restart them but i used the Dash DIP3 route and hence do not have a deterministric.conf

96

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: September 25, 2019, 06:06:04 PM »

1) It appears your remote sanc node is not listening on 8080 (I tried to telnet to it).
Try to add "port=8080" to your sanctuary config file and restart it.

2) Were you able to resolve not being synced yesterday, was it a non issue?

Thank you. It was not working with ip:port but adding port=8080 as an extra line in the config works. Now shows ready.

Syncing was not the issue. I accidentally deleted the entire .biblepayevolution folder but I learnt my lesson from before and restored from a backup wallet.dat. So all 3 sancs synced and ready.

97

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: September 25, 2019, 04:40:01 PM »

Update to non standard port not working

The sanc appears enabled on the list but is unable to connect to the non standard port.

 >sanc status

Code: [Select]

{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "104.167.116.179:8080",
  "proTxHash": "71ac8f0a0b11a7070b4aa2e1862c19a8c5d5106bc5172502ebe8ce87772afc5d",
  "collateralHash": "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583",
  "collateralIndex": 1,
  "dmnState": {
    "service": "104.167.116.179:8080",
    "registeredHeight": 6092,
    "lastPaidHeight": 6097,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "votingAddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "payoutAddress": "yTwJA2VCYQWpWXH8HS7UvEpqRE3Aj5ciUV",
    "pubKeyOperator": "139234c6a2d2f2f449fe5b25006fef684a5be440372756d903f1c793da49812202933c13a8d750ebeb270ea96b62480d"
  },
  "state": "ERROR",
  "status": "Error. Could not connect to 104.167.116.179:8080"
}

>sudo ufw status

Code: [Select]

Status: active

To                         Action      From
--                         ------      ----
22/tcp                     LIMIT       Anywhere                 
8080/tcp                   ALLOW       Anywhere                 
40000/tcp                  ALLOW       Anywhere                 
9998/tcp                   ALLOW       Anywhere                 
19998/tcp                  ALLOW       Anywhere                 
40001/tcp                  ALLOW       Anywhere                 
22/tcp (v6)                LIMIT       Anywhere (v6)             
8080/tcp (v6)              ALLOW       Anywhere (v6)             
40000/tcp (v6)             ALLOW       Anywhere (v6)             
9998/tcp (v6)              ALLOW       Anywhere (v6)             
19998/tcp (v6)             ALLOW       Anywhere (v6)             
40001/tcp (v6)             ALLOW       Anywhere (v6) 


98

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« 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.

99

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« 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.

100

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« 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.

101

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« 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

102

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« 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.

103

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: September 05, 2019, 12:23:41 PM »

Dear Rob,

Based on published data Ref: http://wiki.biblepay.org/Emission_Schedule
And the approx current output, I have calculated the approx BBP allocation based on current QT, can you please confirm? Thank you.

Planned emission   

                %                BBP
Total monthly    51,914,467.00
Per day                  1,730,482.23
Curr QT    0.6        1,038,289.34

Sanc          0.25         259,572.34
PoBHv2    0.25         259,572.34
SB(?)         0.10         103,828.93
GSC           0.40          415,315.74

GSC breakdown:
POG            0.475     197,274.97
POOM        0.475     197,274.97
HEALING    0.050      20,765.79

104

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: September 05, 2019, 11:33:12 AM »

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.

Thank you. Initially, the testnet sancs were enabled even when the entire VPS was off for extended periods of time; now when they temporarily drop connection, all of the sancs appear to be banned and none appear to gave recovered without intervention.

 sanc count
{
  "total": 6,
  "enabled": 0
}

Am I on the same chain as you, as all the sancs on this testnet chain appear banned?

105

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« 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