BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

[T-Mike]

Its possible that it massively changed enough for google to remove it from the safe cache list.  (I remember we needed 500 downloads originally to get in the list).

Its also possible the new image files triggered it - but they are only pngs. 

Whats interesting is all the new code has nothing to do with mining, so thats kind of strange, because proof-of-dc is all business logic.

All I can say is I just installed it and Im running it - and to possibly scan it, on a 3rd party site first, and let me know how the result is?

My build environment is *very* secure.  Nothing comes into it but the existing opensource builds, and no dependencies have changed.

The cache may be what is causing it, I'm not too worried, just letting you know.

[Rob Andrews]

list -l
total 0

Mine says enabled.

Thanks!  When you did the 'exec dcc' did it say 1?  Also could you please try again while tailing the log and see if there is a bug in there (an error)?

Thanks!

[T-Mike]

Can I monitor the hot Sanctuary from my windows wallet? Do I just need to fill in biblepay.conf or masternode.conf or both? Thanks.

[T-Mike]

Thanks!  When you did the 'exec dcc' did it say 1?  Also could you please try again while tailing the log and see if there is a bug in there (an error)?

Thanks!

Yes, it said 1.

Do you meen the debug.log?

2018-02-07 19:41:41 Biblepay Core version 1.0.8.8 (2018-02-07 07:42:02 -0600)
2018-02-07 19:41:41 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-07 19:41:41 ***************************************** BIBLEPAY  ***************************************************
2018-02-07 19:41:41 ProdMode: Prod 0.000000Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-07 19:41:41 BiblePayVersion 1.0.8.8 (2018-02-07 07:42:02 -0600)
2018-02-07 19:41:41 Using OpenSSL version OpenSSL 1.0.2g  1 Mar 2016
2018-02-07 19:41:41 Default data directory /home/biblepay/.biblepaycore
2018-02-07 19:41:41 Using data directory /home/biblepay/.biblepaycore/testnet3
2018-02-07 19:41:41 Using config file /home/biblepay/.biblepaycore/biblepay.conf
2018-02-07 19:41:41 Using at most 125 connections (1024 file descriptors available)
2018-02-07 19:41:41 Using 0 threads for script verification
2018-02-07 19:41:41 scheduler thread start
2018-02-07 19:41:41 HTTP: creating work queue of depth 16
2018-02-07 19:41:41 No rpcpassword set - using random cookie authentication
2018-02-07 19:41:41 Generated RPC authentication cookie /home/biblepay/.biblepaycore/testnet3/.cookie
2018-02-07 19:41:41 HTTP: starting 4 worker threads
2018-02-07 19:41:41 Creating backup folder /home/biblepay/.biblepaycore/testnet3/backups
2018-02-07 19:41:41 Using wallet wallet.dat

[T-Mike]

The error stopped by the way, haven't seen one today although there is still no file in SAN.

[Rob Andrews]

Can I monitor the hot Sanctuary from my windows wallet? Do I just need to fill in biblepay.conf or masternode.conf or both? Thanks.

On the hot sanc, all you really have to do is send the collateral to yourself (the 500,000 even), then add:
masternode=1
masternodeprivkey=yyyyy

In the biblepay.conf, and leave the masternode.conf alone.  (On the testnet sanctuary itself).

You could monitor it in windows, but since testnet is so small I would just click on Sanctuaries on the windows wallet and look by IP.

I dont know if the hot sanc vout will be possible to add to your Win pc, but if you wanted to try : you would copy the 'masternode output' (from the sanctuary itself) TXID & VOUT n to your notepad, then construct the masternode.conf file on the windows PC to include it.  Probably not worth it as it might hose your prod file, etc.  I would just look for the sanc in the list.

[Rob Andrews]

The error stopped by the way, haven't seen one today although there is still no file in SAN.

Hmm, trying to reproduce now by killing my setup...

[T-Mike]

On the hot sanc, all you really have to do is send the collateral to yourself (the 500,000 even), then add:
masternode=1
masternodeprivkey=yyyyy

In the biblepay.conf, and leave the masternode.conf alone.  (On the testnet sanctuary itself).

You could monitor it in windows, but since testnet is so small I would just click on Sanctuaries on the windows wallet and look by IP.

I dont know if the hot sanc vout will be possible to add to your Win pc, but if you wanted to try : you would copy the 'masternode output' (from the sanctuary itself) TXID & VOUT n to your notepad, then construct the masternode.conf file on the windows PC to include it.  Probably not worth it as it might hose your prod file, etc.  I would just look for the sanc in the list.

Alright, I'm not going to try it. I literally spend all day setting up the testnet masternode yesterday. How many masternodes do we need? I can potentially host 10 of them by cloning but I don't want to do that until it's needed.

[Rob Andrews]

Hmm, trying to reproduce now by killing my setup...

Aha!  Ok the st13 last_writetime_error is fixed for the next testnet version later today.

In the mean time, anyone who has either run into the problem , or never experienced the problem type:
exec dcc

You should see "1".
This fixes the problem temporarily until the next release.

[T-Mike]

Aha!  Ok the st13 last_writetime_error is fixed for the next testnet version later today.

In the mean time, anyone who has either run into the problem , or never experienced the problem type:
exec dcc

You should see "1".
This fixes the problem temporarily until the next release.

Great! Thanks.

[Rob Andrews]

Alright, I'm not going to try it. I literally spend all day setting up the testnet masternode yesterday. How many masternodes do we need? I can potentially host 10 of them by cloning but I don't want to do that until it's needed.

LOL, yeah the first couple I set up were tricky now for some reason they seem easy. 
Uhh, I would just be happy if you did a couple, because I think we only need 10 total sancs in testnet to prove the quorum side features are all working correctly, lets talk about that soon.
But in the mean time, I would definitely like to get 50 boinc cpids out here, because not only do I want to get a feel and give everyone a taste of what we would be doing, but also to test the superblock frequency and verify the payments per mangitude and all the security.

I have 2 running, so if you did 2 + Togos, we would be halfway there.

Ill start getting the commands to show what rules the sancs go through in the morning.

[Rob Andrews]

Great! Thanks.

Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

[T-Mike]

LOL, yeah the first couple I set up were tricky now for some reason they seem easy. 
Uhh, I would just be happy if you did a couple, because I think we only need 10 total sancs in testnet to prove the quorum side features are all working correctly, lets talk about that soon.
But in the mean time, I would definitely like to get 50 boinc cpids out here, because not only do I want to get a feel and give everyone a taste of what we would be doing, but also to test the superblock frequency and verify the payments per mangitude and all the security.

I have 2 running, so if you did 2 + Togos, we would be halfway there.

Ill start getting the commands to show what rules the sancs go through in the morning.

Sure, just let me know when. The only problem right now is I only have enough tBBP for one more. You have my e-mail, it's a headache trying to keep up with the forum. How many cpids are running right now?

[Rob Andrews]

Sure, just let me know when. The only problem right now is I only have enough tBBP for one more. You have my e-mail, it's a headache trying to keep up with the forum. How many cpids are running right now?

Looks like 4 cpids.

Well I mean we could do it in 5 mins and make it a learning experience for everyone to understand the high security in place.

[T-Mike]

Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

Hmm, it says:
error code: -1
error message:
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"

MY sanctuary is this one by the way:
"749df434020e56e87a48607eaa1cbd504fcc62eb90056a39d2d58c315b9ebda4-1": "ENABLED",