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

just compiled 1.0.8.8 sourcecode,but can't sync blocks.
it's still not working after i added these node:
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

any other node ?

Figured it out, the testnet also uses the biblepay.conf in the /.biblepaycore folder, not the /.biblepaycore/testnet3 folder.

Just got an error while sitting in console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()       

It keeps coming up over and over again.

Just got an error while sitting in console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()       

It keeps coming up over and over again.

Hmm, do you have any special permissions set up or is biblepay running as root?

Try creating /home/biblepay/.biblepaycore/SAN and see if it goes away?

Ill check this issue out also...

HOW TO SETUP HOT TESTNET LINUX SANCTUARY (MASTERNODE)

References:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
http://wiki.biblepay.org/Create_Masternode#BiblePay_Sanctuaries_Setup_-_Linux_Server
http://wiki.biblepay.org/Create_Sanctuary_2

=====================================================

A. Setup Remote Linux Server
http://wiki.biblepay.org/Create_Sanctuary_2#PART_B_-_Rent_Linux_Cloud_Machine

B. Install, Run and Stop BiblePay
http://wiki.biblepay.org/Create_Sanctuary_2#PART_C_-_Install_Sanctuary_Linux_Wallet
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

C. Set Wallet to Testnet
cd ~/.biblepaycore
vi biblepay.conf
testnet=1
:wq

cd home/biblepay/src
./biblepayd -daemon

=====================================================

1. Ask for 500,005 tBBP (test BiblePay) on the forum, post your address:
./biblepay-cli getaccountaddress ""

2. Create a new address to send escrow to:
./biblepay-cli getaccountaddress MN1

Copy the Address Output
yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo

3. Send 500,000 tBBP to escrow address:
./biblepay-cli sendtoaddress yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo 500000

Copy the TXID Output
da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772

4. Turn on mining for a few minutes to make blocks advance
./biblepay-cli setgenerate true 1
./biblepay-cli getinfo
./biblepay-cli getmininginfo
./biblepay-cli setgenerate false

5. Get the VOUT
./biblepay-cli masternode outputs

Copy the VOUT Output
1 or 0

6. Get the Private Key
./biblepay-cli masternode genkey

Copy the Private Key Output
92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

7. Stop BiblePay
./biblepay-cli stop

7. Add Sanctuary to masternode.conf
cd ~/.biblepaycore/testnet3
vi masternode.conf  (i insert, :wq to write and quit)

[SANCTUARY_ALIAS] SPACE [SANCTUARY_PUBLIC_IP:40001] SPACE [SANCTUARY_PRIVATE_KEY] SPACE [ESCROW_TXID] SPACE [ESCROW_VOUT]

MN1 34.208.206.95:40001 92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772 1

8 Add flags to biblepay.conf:
Note: I added same to both biblepay.conf files, in main folder and in testnet3

rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=34.208.206.95
masternode=1
masternodeprivkey=92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

9. Open Ports in Firewall
sudo apt-get update
sudo apt-get install ufw
sudo ufw allow ssh/tcp
sudo ufw limit ssh/tcp
sudo ufw allow 40001/tcp
sudo ufw allow 9998/tcp
sudo ufw logging on
sudo ufw enable
sudo ufw status

10. Start masternode
./biblepay-cli masternode start-alias MN1
NOTE: Weird mine was already started somehow

11. Masternode Debugging
./biblepay-cli mnsync status
./biblepay-cli masternode list
./biblepay-cli masternode status

Wait for Masternode info to sync, AssetID 999 MASTERNODE_SYNC_FINISHED:
./biblepay-cli mnsync status

12. Install Watchman
sudo apt update
sudo apt -y install git python-virtualenv virtualenv
cd ~/.biblepaycore
git clone https://github.com/biblepay/watchman.git
cd watchman
virtualenv venv
venv/bin/pip install -r requirements.txt

13. Set Watchman to Testnet
vi watchman.conf
Comment network=mainnet  (add # in front)
Uncomment network=testnet (remove # in front)
:wq

cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py

Make sure this command gives no output and then add it to crontab

crontab -e

# i insert
* * * * * cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1
# :wq

14. Wait for Masternode Status to go from PRE_ENABLED to ENABLED,
turn on mining if no one is mining
./biblepay-cli masternode list

=====================================================

Let me know if this is correct, seems to be working for me so far, but Im still in PRE_ENABLED state

Im also getting this message randomly in my console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::last_write_time: No such file or directory: "/home/ubuntu/.biblepaycore/SAN/magnitude"
biblepay in ProcessMessages()

Try creating /home/biblepay/.biblepaycore/SAN and see if it goes away?

cd ~/.biblepaycore
ls SAN

Looks like SAN directory exists, but its empty, so I guess it cant write the magnitude file?

Who can send me 1 test bbp to my address yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh

I wan to associate my boinc account with biblepay,but it said Balance too low to advertise DCC, 1 BBP minimum is required.

Who can send me 1 test bbp to my address yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh

I wan to associate my boinc account with biblepay,but it said Balance too low to advertise DCC, 1 BBP minimum is required.

I sent some. Hope it worked buddy!

I sent some. Hope it worked buddy!

thanks very much,it worked!

"Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"

Finally, windows is ready.  Turned out that "cancer" image caused all kinds of problems in the build. 

Summary of what has changed:

1.0.8.8p - Windows & Linux - Leisure for Testnet

- Since protocol version has been increased, you will need 1088p (Windows) to start/stop a 1088 sanctuary
- Added more features to the rpc command : exec getboincinfo.  It now loops through all your cpids, and shows the RAC of each cpid and the total magnitude.  It also finds the last superblock you were in and prints some info about that (like total payments).
- Added the ability to Re-Associate a CPID with a new wallet.  This is Only if you lose your wallet or want to move your CPID to a brand new wallet.  Most of the time if you keep your wallet.dat you will never want to do this.  But if lets say you throw away your old PC and move, and buy a new PC, yet your existing CPID has say 100,000 credits, and you just want to associate that old CPID with a brand new wallet, Biblepay would say "Already_In_Chain".  To perform this action type : exec associate rosetta_email rosetta_pass force.  This will forcefully kill the old burn transaction and reassociate you. 
- Note the windows wallet has a GUI for DC association.
- Fixed the issue 616w mentioned where we show the POL weight info in prod (removed in prod), and Also verified that DC is not visible in Prod

** I have not looked at the SAN/Magnitude ST13 error yet, I will be looking at that next **

** I apologize to everyone I offended.  I want to take a breather and start over, but I want you all to keep an open mind and give DC a chance before disregarding it.  Lets test it, Ill add a vote for it, and if it fails the litmus test and the vote Ill go back to supporting POL/POBH fully.  But until then I feel we have created a feature that is #1 in crypto, especially when you take into consideration the security issue that has been solved in Biblepay (Sanctuary Quorum) **

Finally, windows is ready.  Turned out that "cancer" image caused all kinds of problems in the build. 

Summary of what has changed:

1.0.8.8p - Windows & Linux - Leisure for Testnet

- Since protocol version has been increased, you will need 1088p (Windows) to start/stop a 1088 sanctuary
- Added more features to the rpc command : exec getboincinfo.  It now loops through all your cpids, and shows the RAC of each cpid and the total magnitude.  It also finds the last superblock you were in and prints some info about that (like total payments).
- Added the ability to Re-Associate a CPID with a new wallet.  This is Only if you lose your wallet or want to move your CPID to a brand new wallet.  Most of the time if you keep your wallet.dat you will never want to do this.  But if lets say you throw away your old PC and move, and buy a new PC, yet your existing CPID has say 100,000 credits, and you just want to associate that old CPID with a brand new wallet, Biblepay would say "Already_In_Chain".  To perform this action type : exec associate rosetta_email rosetta_pass force.  This will forcefully kill the old burn transaction and reassociate you. 
- Note the windows wallet has a GUI for DC association.
- Fixed the issue 616w mentioned where we show the POL weight info in prod (removed in prod), and Also verified that DC is not visible in Prod

** I have not looked at the SAN/Magnitude ST13 error yet, I will be looking at that next **

** I apologize to everyone I offended.  I want to take a breather and start over, but I want you all to keep an open mind and give DC a chance before disregarding it.  Lets test it, Ill add a vote for it, and if it fails the litmus test and the vote Ill go back to supporting POL/POBH fully.  But until then I feel we have created a feature that is #1 in crypto, especially when you take into consideration the security issue that has been solved in Biblepay (Sanctuary Quorum) **

That's great! Will test it out.

Thanks for apologizing, let's continue to work on this as a body.

Im also getting this message randomly in my console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::last_write_time: No such file or directory: "/home/ubuntu/.biblepaycore/SAN/magnitude"
biblepay in ProcessMessages()

cd ~/.biblepaycore
ls SAN

Looks like SAN directory exists, but its empty, so I guess it cant write the magnitude file?

Before I break this, anyone who is having this issue, Id like to ask one test first.

Could you please go to the console and type 'exec dcc'
Then wait about 15 seconds and see what is in :
~/.biblepaycore/SAN

Please post the ls -l from that directory?

Also, please tell me if you are a sanc and if your 'masternode status' is enabled?  This procedure is only supposed to run on the "chosen sancs".  Those are the ones with a rank less than 10:1.

Before I break this, anyone who is having this issue, Id like to ask one test first.

Could you please go to the console and type 'exec dcc'
Then wait about 15 seconds and see what is in :
~/.biblepaycore/SAN

Please post the ls -l from that directory?

Also, please tell me if you are a sanc and if your 'masternode status' is enabled?  This procedure is only supposed to run on the "chosen sancs".  Those are the ones with a rank less than 10:1.

list -l
total 0

Mine says enabled.

By the way, I installed the new Windows wallet but I'm getting a smartscreen error saying the file is potentially dangerous.

Thanks for the Hot Sanctuary guide Togo - so just to confirm - the Hot sanctuary is all you need in testnet.  We dont need to deal with starting and stopping those from the controller wallet or protecting the funds.

(Its a funny analogy that I envision the Controller wallet to be the only one running the POW-pobh algo in the next revision, but that is for prod.  The controller wallet would be your wallet to send/receive funds, run POBH on one thread, and start-stop sancs).

Alex asked a question yesterday about the rewards.
In Testnet, the Heat miners (if you solve a block with POBh) only receive about 550 BBP.  The Sanc reward is about 5500 BBP. 
The DC Reward is 1.2 MILLION per day divided by the researchers Share (This is equal to TotalDailyEmission minus 20% standard budget minus sanctuary rewards minus heat rewards).   All figures above assume that our normal 20% budget has been held back from every block (for the monthly budget).