Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Rob Andrews

Pages: 1 ... 256 257 258 259 260 261 262 [263] 264
Can anyone help me with this? I'm not successful in creating a cold masternode. But maybe that's because both my computers are in the same network and have the same external ip? I'm not at all an expert in linux, so I just try to follow the guide as best as possible.

Also: should the biblepay.conf also be in the testnet3 folder? Or does the testnet use the same one as the main wallet? I put it in the testnet3 folder btw.

I'm also compiling biblepay on my raspberry as we speak. seems to work now I have the swapfile enabled. I wonder how much hps2 I'm gonna get with this :p
So what I have found so far about public IPs, is they really will be required in prod because your masternode payment will fall back to the end of the queue if the pings to the external IP fail.  Also in testnet, it will be hard to test watchman out properly if we dont simulate the prod environment with real permanent IPs.  You can use a dynamic IP though, it just has to be Public and Distinct (another words, a house IP is fine with port forwarding, but you can only have One masternode running in your house per public IP).
Anyway, if you will port forward port 40001 from your router to the PC that is going to be the masternode, and it has to run linux since watchman needs to run, do a test from another pc to telnet to the address (IE:      telnet my_public_ip 40001) and ensure it answers.  Then you know you have that public IP associated with the new masternode.

As far as binding it to the new hot wallet, you would need to put this line in the actual masternode (not the controller) in the biblepay.conf file:

On the controller wallet, you dont need the line with externalip.

Then, as far as directories, here is what I learned that is sort of frustrating:  For testnet, you need to go into the \testnet3 directory and create the masternode.conf file there, IE:  \testnet3\masternode.conf.  But for the standard settings in testnet, they go in : ~.biblepaycore\biblepay.conf (IE the root).

Been out of pocket for a few days, sorry.

I'm getting success with the swap file, I'll try and get time in the next few days to write up some more notes and submit them.  Again, apologies for editing the wiki when I wasn't having success.

Speaking of the wiki, it looks like it is getting spammed pretty hard.

Ok, I deleted the 7500 spammed fake articles, and 3250 fake accounts.

I added a math captcha on article edit, and on user create.  I enabled the option to require email verification and the requirement to have an account and be logged in before editing any pages.

Thanks for pointing out the mass defacation.

I already did all of that. I did it again now carefully to confirm the steps, but I still get the same error.  :-\ Currently I have no idea where else to look.

LOL, I've never seen that before. I wonder how Wikipedia deals with this.

Great, more things to deal with huh.

Looks like we need to put a captcha on the edit page.

If that doesnt stop it later on we can go to requiring an approved account.

Ill look into deleting all this garbage next.

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

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

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= 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).

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!

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

Worked for me.

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



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.

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

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


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.

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.

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.

ok... I found on first post, there now external cold wallet not working ;)
but... I found this:
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.

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

some anothers nodes with external IP ?
I think I'am banned on *
I only banned one IP this morning, what is your ip prefix? 


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 40001

Ensure you get a connection?

yiADn9XHSj58Vab9zqMooQCTsYmADNZRXJ - one 1mln please ;)
I mining half day, and have only 500k ;)

Pages: 1 ... 256 257 258 259 260 261 262 [263] 264