BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

I only banned one IP this morning, what is your ip prefix? 

EDIT:

Btw, one thing you can do is: go into the \testnet3 dir, delete the peers.dat, banlist.dat, and the mncache.dat, and restart.  (With the 3 addnodes in).
One other thing, from a command line:
telnet node.biblepay.org 40001

Ensure you get a connection?

I started it from other server.
But I stuck on other thing.

On my sanctuary I have messeges like:

Code: [Select]

2017-10-05 05:19:08 CActiveMasternode::ManageStateInitial -- Checking inbound connection to '137.74.0.113:40001'
2017-10-05 05:19:08 AcceptConnection -- masternode is not synced yet, skipping inbound connection attempt
2017-10-05 05:19:08 CActiveMasternode::ManageStateInitial -- INITIAL: Wallet balance is < 500000 biblepay
2017-10-05 05:19:08 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Masternode not in masternode list
....
2017-10-05 05:30:53 CActiveMasternode::ManageStateRemote -- NOT_CAPABLE: Masternode not in masternode list
2017-10-05 05:31:30 12UpdateTip: new best=06ea4473c0e4cc9c63432a676e20730bf97ec27be9a91d61db977ef570af901a  height=4151  log2_work=42.877044  tx=4165  date=2017-10-05 05:31:33 progress=0.004809  cache=0.0MiB(10tx)
mnsync status:

Code: [Select]

{
  "AssetID": 2,
  "AssetName": "MASTERNODE_SYNC_LIST",
  "Attempt": 1,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
}
masternode list is empty.

on my laptop:
mnsycn status

Code: [Select]

{
  "AssetID": 999,
  "AssetName": "MASTERNODE_SYNC_FINISHED",
  "Attempt": 0,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": true,
  "IsWinnersListSynced": true,
  "IsSynced": true,
  "IsFailed": false,
  "MasternodesEnabled": true
}

masternode list

Code: [Select]

{
  "0b9b0bc476ba9fd11060d3aaced702bd90608a947259420d8f2dff97d189804d-1": "PRE_ENABLED"
}
my server and my laptop is connected to the same node (vultr5.biblepay.org).


EDIT
ok, in my office I forwarded 40001 port to my laptop.
now everything is connected, on my laptop I have locked tx for masternode, and is in masternode list,
but when I try to broadcast masternode node then on my sanctuary I see this in debug log:

Code: [Select]

2017-10-05 06:38:24 CMasternodeMan::CheckOutpoint -- Got mismatched pubKeyCollateralAddress and vin
2017-10-05 06:38:24 CMasternodeMan::CheckMnbAndUpdateMasternodeList -- Rejected Masternode entry: 0b9b0bc476ba9fd11060d3aaced702bd90608a947259420d8f2dff97d189804d-1  addr=137.74.0.113:40001


ok... I found on first post, there now external cold wallet not working
but... I found this: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/27197442/Guide+using+OS+X+local+Linux+remote
here is one more option ... masternodeaddr - that we need to put in our cold wallet
maybe this is a problem ?

I modified the install wiki a bit. 

One issue I hit was it exhausted the virtual memory while building BBP Core.  I'm rebuilding it from
./autogen.sh
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
sudo make

on the linux install docs.  Is 1 GB RAM enough to build?

Just a general note on this particular issue regarding the Create_Masternode wiki.
If you have not installed a Masternode successfuly and are not yet running a successful masternode yet, I would suggest not trying to modify the wiki page that you dont fully grasp yet.

I know the page is no where near perfect, but what is happening is you are making modifications to something that is not complete and potentially misleading us.

I think what we need to do is get our cold and hot masternodes working first, and then tweak the prod instructions with Successful known changes.

If you want, you can go ahead and clone the masternode create page to another testnet page name and tweak that one for testnet until its final.

Changing to 500,000 bbp is fine for testnet, but its not the final amount for prod.
The 'sanctuary server' is not the right nomenclature.  All the hosts are servers.  (IE this is not a client-server solution).  There are going to be one to many sanctuaries per single controller wallet. (So we have controller wallet, and sanctuary wallets).

I just wanted to mention this because I noticed you took out all the lines that said 'still from the main PC' to try to simplify it.  Thus leaving ambuiguity between the commands from the sanctuary wallet and the main controller wallet.  So lets clone the page to a create_masternode_testnet version and do whatever you want to it until its clear then we can overwrite the prod version.

ok... I found on first post, there now external cold wallet not working
but... I found this: https://dashpay.atlassian.net/wiki/spaces/DOC/pages/27197442/Guide+using+OS+X+local+Linux+remote
here is one more option ... masternodeaddr - that we need to put in our cold wallet
maybe this is a problem ?

Hi Svirus,

Great find.  Yeah, I had gone through that myself, and in the end the only way I could create the masternode was in hot mode, and then I did successfully boot two masternodes up, and they are running in cold mode.  In cold mode, I see the masternodes are now being paid through the masternode payment system (not through block subsidy) and the amounts seem to be correct.  I have not successfully activated one in hot mode.

You did find the key to the problem, whenever the hot wallet is 'activated' from the controller wallet, then I see this in the log on the *sanctuary*:
Got mismatched pubKeyCollateralAddress and vin

Just like you do.  Now it is possible, that my first 7 tests didnt actually honor the 'masternodeaddr'.  I do remember this, it is quite different to fully qualify the addr and the port.  If you want you can try this:  masternodeaddr=YourIP:40001. Note the fully qualifyied port number for testnet. 
Could you see if that works?  Btw, our port is 40000 for prod and 40001 for testnet, so anytime you see a 9999 for dash its 40001 for our testnet.

Im thinking we try to get hot mode going a little while longer, and eventually over the next day or so, we put someone else here on a mission to keep working on hot mode and we bring up 5 or so in cold mode to keep us moving as a team, so that I can add the code for the sanctuaries on the web site for testnet.

Does anyone here have a dash masternode?  I was kind of wondering how long it takes to see the other masternodes in the all sanctuaries list.

Sorry to tinker with the wiki, just was trying to make it cleaner and easier to read as I went along and didn't consider the nomenclature being as significant but understand.

Also, have you installed the wallet on a 1GB Vultr?  If so, do you have any thoughts about the memory issue.?

No, sorry, I really never ran into that memory problem, I dont even have any input here.  You would be better off googling that one.

Hang on guys, I see a fundamental error in the instructions.

The masternode genkey command should actually be done on the SANCTUARY!  LOL. 

Let me do another çold wallet test, and if it works Ill edit the wiki, hang on.

OK. Btw, is there anything else to do after following the wiki instructions? Or that's it, then just keep the node online?

Were going to have to see if it stays in sync, shows a global list of masternodes that agree, if the payments are correct for Inbound payments, how to install watchman-on-the-wall, if watchman helps the masternode show ÄCTIVE (instead of just synced), and how to create a proposal.

So far, we have achieved absolutely Zilch.

I have to step out but if anyone wants to continue creating a cold sanctuary tonight you can refer more to this video:

https://www.youtube.com/watch?v=Lybtz7iucVs

Note that he definitely creates the masternode genkey on the sanctuary side.

 

Can someone send me 600k (or whatever is enough for a sanctuary) testnet biblepay?

yiVg3gjd2UiyeCmFrbvL8phqUnLTYdVroK

Can someone send me 600k (or whatever is enough for a sanctuary) testnet biblepay?

yiVg3gjd2UiyeCmFrbvL8phqUnLTYdVroK

Sent.


So Im a little frustrated with the 'cold wallet' creation process (on my end), and at this point Im going to move on and spin up 3 hot wallet masternodes.  As I need to move further.

At least with hot masternodes, theoretically, we can still test to see if the masternode list is being broadcast and that we stay in sync, and that the payments and votes work.

The biggest disadvantage of the hot wallet masternode is your hosting provider can steal your biblepay.  Yes thats a problem we will have to solve separately, but I dont want it to stop our progress.

Here is a link to create a swap file on the vultr server if you hang up during compile:

https://digitizor.com/create-swap-file-ubuntu-linux/

Worked for me.

I am elated to inform everyone that a bug existed in 1047, preventing sanctuaries from being verified and broadcast to other nodes.  I believe this even caused a small d-dos issue!  The problem is fixed now in 1048.  Code has been sent in to github.  Windows is compiling now.

Sorry about the inconvenience.  It took 3 full days out of my life.

So, now if anyone feels like testing a hot wallet, please do it over.  For now, Ive already created 3 cold wallets this morning and Im going to go ahead and test those out first.

Also, I updated the 'CompilingBiblePayOnLinux.txt' doc in the root of github.  There is a section in there for watchman-on-the-wall.  Feel free to install it on your linux node and test it.  I have it running, and it appears to be working.  Now we are making some progress again!  Thank God!

So, now if anyone feels like testing a hot wallet, please do it over.  For now, Ive already created 3 cold wallets this morning and Im going to go ahead and test those out first.

I finally got a linux version compiled on my laptop. I tried it on a Raspberry 3 first (with ubuntu 16.04), but it doesn't seem up to the task. It freezes when compiling.

I there also a walkthrough to create a hot-wallet sanctuary?

Make sure you have enough memory. Follow admin's post above or for me I have found these commands to be working well for a 1 GB RAM machine:

Code: [Select]

free (check if swap is 0)
dd if=/dev/zero of=/var/swap.img bs=1024k count=1000
mkswap /var/swap.img
swapon /var/swap.img
free (check if swap is 1024)
Then compile again.

Thanks! I saw the earlier post but didn't link it to my specific situation, but it's indeed what I was looking for. Will try again

OK, I compiled 1.0.4.8 and also followed the steps to install watchman, but I encounter this:

~/.biblepaycore/watchman$ venv/bin/python bin/watchman.py

Code: [Select]

[Errno 111] Connection refused
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.
biblepayd is running, but I don't know how to do the second part.

Yea, and I know we need to modify the master wiki with better instructions, sorry, I plan on doing that once we get a stable set of instructions, but anyway on this issue:

Ensure the 'watchman.conf' file (in the watchman dir) is pointed to testnet and not mainnet (by putting a # in front of the main and unpounding the testnet)
- Ensure rpcallowip=127.0.0.1 is set along with rpcuser and rpcpassword in the main 'biblepay.conf' for the node (the one in the root) and then restart. 

When you rerun watchman, if the nodes 'mnsync status' is 999, watchman should return empty meaning everything is working (in contrast to an error).