Bible Pay

Read 37652 times

  • Rob A.
  • Administrator

    • 1214


    • 20
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #30 on: October 06, 2017, 12:35:34 pm »
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!



  • jaapgvk
  • Hero Member

    • 566


    • 22
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #31 on: October 07, 2017, 06:25:49 am »

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?


  • jaapgvk
  • Hero Member

    • 566


    • 22
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #32 on: October 07, 2017, 06:50:24 am »
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 :)


  • Rob A.
  • Administrator

    • 1214


    • 20
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #33 on: October 07, 2017, 09:31:10 am »
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).



Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #34 on: October 07, 2017, 11:10:32 am »
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. 


  • Rob A.
  • Administrator

    • 1214


    • 20
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #35 on: October 07, 2017, 02:30:21 pm »
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.



  • Rob A.
  • Administrator

    • 1214


    • 20
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #36 on: October 07, 2017, 03:58:44 pm »
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.



  • togoshigekata
  • Sr. Member

    • 331


    • 19
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #37 on: October 08, 2017, 02:30:00 am »
500k tBBP please :) yPn4ibkbAHo9jB1SthLEFqzRVpsDmfWTN3

EDIT: Mined a bunch of coins, now waiting for them to mature

=====

Questions:
- How to start Biblepay Daemon in TestNet mode on linux command line?
« Last Edit: October 08, 2017, 04:24:55 am by togoshigekata »


  • jaapgvk
  • Hero Member

    • 566


    • 22
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #38 on: October 08, 2017, 04:41:06 am »
500k tBBP please :) yPn4ibkbAHo9jB1SthLEFqzRVpsDmfWTN3

EDIT: Mined a bunch of coins, now waiting for them to mature

=====

Questions:
- How to start Biblepay Daemon in TestNet mode on linux command line?

I was trying to send to tBP but when I fired up the testnet wallet I couldn't get synched...

But anyway, to start in testnet with the GUI-wallet, go to your Biblepay qt folder $BP_ROOT/biblepay/src/qt

And then run the following command:
./biblepay-qt -testnet

I don't know how to start the headless wallet, but I guess in general it will be the same procedure.


  • jaapgvk
  • Hero Member

    • 566


    • 22
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #39 on: October 08, 2017, 07:56:59 am »
I there also a walkthrough to create a hot-wallet sanctuary?

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


  • Rob A.
  • Administrator

    • 1214


    • 20
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #40 on: October 08, 2017, 09:21:34 am »
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:
externalip=my_public_ip

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

« Last Edit: October 08, 2017, 09:25:02 am by admin »


  • togoshigekata
  • Sr. Member

    • 331


    • 19
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #41 on: October 08, 2017, 05:50:14 pm »
TOGO NOTES

We are testing Masternodes (Sanctuaries) functionality on the Testnet chain, using Test Biblepay (tBiblePay) coins

Requirements
2 machines with 2 separate IP addresses

you are setting up a Masternode on a remote Linux server (Sanctuary Wallet)
and storing tBiblePay coins on a local Windows PC (Controller Wallet)

PART 1 - Controller Wallet (Windows) TestNet

On local/home Windows PC:

1. Download & Install latest version of BiblePay:
http://biblepay.org/

2. Enable and Run Wallet in Testnet Mode

Find and Edit biblepay.conf file in %appdata%/BiblePayCore folder,
Add line below and Save:
testnet=1
(Note: Can also edit biblepay.conf from Wallet Menu >> Tools >> Open Configuration File)

3. Run BiblePay

4. See Green Background on loading screen and on Icon, also See tBiblePay name for coins
On command line, use ./biblepay-cli getinfo command and check for: "testnet": true

5. After Loading, Close Wallet

6. Edit biblepay.conf file, add lines below and save:
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

7. Run BiblePay

8. Ask in this Forum for someone to send you 500,000 tBiblePay (Test Biblepay coins)
Post your Receiving Address:
Wallet Menu >> File >>> Receiving Addresses >> Right Click >> Copy Address
(or start mining coins: setgenerate true X)

==========

PART 2 - Rent Linux Cloud Machine

1. Research and Choose Cloud Provider (AWS, Google, Azure, [Vultur], etc)  and Create Account
2. Choose Machine to Rent (Recommend: Ubuntu 16.04, 2GB RAM)
3. Payment Method
4. Connect to it / SSH (Putty http://www.putty.org/ SSH Client for Windows)

==========

PART 3 - Install Sanctuary Linux Wallet
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

==========

PART 4 - Run Sanctuary Linux Wallet Testnet

On remote Linux machine:

1. Enable & Run Wallet in Testnet mode:

Edit ~/.biblepaycore/biblepay.conf file and add
testnet=1
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

2. Close wallet:
./biblepay-cli stop
-or if stuck-
ps -ef #view processes
kill PID

3. Run BiblePay:
./biblepayd -daemon

4. Check that blocks number matches home Windows wallet and that testnet=true:
./biblepay-cli getinfo

===========

PART 5 - Financing your Sanctuary Masternode

http://wiki.biblepay.org/Create_Masternode

1. Generate private key on Sanctuary Masternode Linux machine

./biblepay-cli masternode genkey

(Store this as your MASTERNODE_PRIVATE_KEY)

2. Controller Wallet - Show Proof of Coins
getaccountaddress MASTERNODE_NAME #creates MASTERNODE_ADDRESS
sendtoaddress MASTERNODE_ADDRESS 500000 "" ""

3. Wait for 15 confirmations
(Note: Testnet chain mines blocks every 1 minute,
turn on miner if no one else is mining so confirmations can go through: setgenerate true 1)

4. Controller Windows Wallet - Edit masternode.conf:
%appdata%/biblepaycore/testnet3/masternode.conf
Add line below and Save:

ALIAS IP:40001 MASTERNODEPRIVKEY TRANSACTIONHASH INDEX

ALIAS: Any name/label that you want to call your masternode
IP: Your masternode IP (Your masternode VPS's IP)
MASTERNODEPRIVKEY: This is the private key that you placed in your remote configuration
TRANSACTIONHASH: This is the transaction hash for the transaction in which you got your 500000 BBP deposited.
INDEX: This is the Index of your transaction for that address I'll show you how to get it in a bit.

4.a Get TRANSACTIONHASH and INDEX from running this command:
./biblepay-cli masternode outputs

You will get a string that looks like this:
{
"06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb" : "0",
}
The long string is your TRANSACTIONHASH, and the last number is the INDEX.


5. Controller Windows Wallet - Edit biblepay.conf:
Find and Open: %appdata%/BiblePayCore/testnet3/biblepay.conf
Decide on RandomUsername and RandomPassword to use for RPC credentials
Add Lines below and Save:

rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

6. Restart Controller Wallet

7. Sanctuary Wallet Remote Linux Machine, Run Firewall/Port commands:
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 logging on
sudo ufw enable
sudo ufw status

8. Sanctuary Masternode Linux Wallet - Edit ~/.biblepaycore/biblepay.conf:
rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
logtimestamps=1
externalip=MASTERNODE_PUBLIC_IP
maxconnections=256
masternode=1
masternodeprivkey=MASTERNODE_PRIVATE_KEY

(MASTERNODE_PUBLIC_IP, Public IP Address of Remote Linux Sanctuary Wallet_

9. Sanctuary Masternode Linux Wallet - Restart BiblePay:
./biblepay-cli stop
./biblepayd -daemon

10. Controller Windows Wallet - Start Masternode?
masternode list
masternode list-conf
masternode start-alias MASTERNODE_NAME
(Note: MASTERNODE_NAME is from Step 3. b when you added Masernode information to /testnet3/masternode.conf file)

mnsync status
(Masternodes take a few minutes to sync(

masternode start-alias MASTERNODE_NAME

masternode help
masternode debug

11. Sanctuary Masternode Linux Wallet, Check Status:
masternode status

==========

PART 6 - Watchman
How to install Watchman on the Wall
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman

1, Clone & Install Watchman
sudo apt update
sudo apt 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

2. Set Watchman Config
nano watchman.conf
- 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)
[For nano editor, ctrl+O to save file, ctrl+X quit]

3. Run Watchman
venv/bin/python bin/watchman.py

4. Setup Watchman in Cron:
crontab -e
Add this line:
* * * * * cd /home/YOURUSERNAME/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

===========

Wallet GUI PROTIP
Settings >> Options >> Wallet >> Show Masternodes Tab >> OK

References:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman
http://wiki.biblepay.org/Create_Masternode
https://www.youtube.com/watch?v=Lybtz7iucVs

Dash Masternode Guides:
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867820/TAO+S+SETUP+GUIDE+FOR+DUMMIES+12.1
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867877/Start+multiple+masternodes+from+one+wallet+start-many
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/24019061/Newcomer+Section+-+What+is+...+and+how+do+I+set+one+up

More References:
https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)#JSON-RPC
https://bitcoin.org/en/developer-reference#remote-procedure-calls-rpcs
https://github.com/dashpay/dash/blob/master/contrib/debian/examples/dash.conf
« Last Edit: November 12, 2017, 08:31:38 pm by togoshigekata »


  • togoshigekata
  • Sr. Member

    • 331


    • 19
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #42 on: October 09, 2017, 09:21:02 pm »
Im stuck installing watchman:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt
https://github.com/biblepay/watchman

This command I get an error:
venv/bin/python bin/watchman.py

[Errno 111] Connection refused
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.


  • togoshigekata
  • Sr. Member

    • 331


    • 19
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #43 on: October 09, 2017, 10:37:22 pm »
https://www.youtube.com/watch?v=Lybtz7iucVs&t=75s

he did run "masternode genkey" command in the remote Linux wallet, interesting, Im still confused on that

he also sets in vivo.conf
rpcport=10000
masternode=1
bind=PublicIP:Port
masternodeprivkey=asdf

Wallet GUI PROTIP
Settings >> Options >> Wallet >> Show Masternodes Tab >> OK

These Dash Guides look like their masternode genkey is run on local home wallet
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867820/TAO+S+SETUP+GUIDE+FOR+DUMMIES+12.1
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867877/Start+multiple+masternodes+from+one+wallet+start-many

https://dashpay.atlassian.net/wiki/spaces/DOC/pages/31326216/Simple+MN+on+a+Windows+machine
" a more simple method of running a mastermode directly on a Windows platform, if you have enough confidence that your digital cash is safe. With this method, you will be using your wallet directly as a masternode, keeping it open 24/7."
« Last Edit: October 09, 2017, 10:52:42 pm by togoshigekata »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #44 on: October 10, 2017, 12:50:56 am »
https://www.youtube.com/watch?v=Lybtz7iucVs&t=75s

he did run "masternode genkey" command in the remote Linux wallet, interesting, Im still confused on that

he also sets in vivo.conf
rpcport=10000
masternode=1
bind=PublicIP:Port
masternodeprivkey=asdf

Wallet GUI PROTIP
Settings >> Options >> Wallet >> Show Masternodes Tab >> OK

These Dash Guides look like their masternode genkey is run on local home wallet
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867820/TAO+S+SETUP+GUIDE+FOR+DUMMIES+12.1
https://dashpay.atlassian.net/wiki/spaces/DOC/pages/1867877/Start+multiple+masternodes+from+one+wallet+start-many

https://dashpay.atlassian.net/wiki/spaces/DOC/pages/31326216/Simple+MN+on+a+Windows+machine
" a more simple method of running a mastermode directly on a Windows platform, if you have enough confidence that your digital cash is safe. With this method, you will be using your wallet directly as a masternode, keeping it open 24/7."

I ran masternode genkey on the MN wallet.

Added the fields (to biblepay.conf)
masternode=1
masternodeprivkey=XXXXXXXXXXX
externalip=IP

but it get " "status": "Not capable masternode: Broadcasted IP doesn't match our external address. Make sure you issued a new broadcast if IP of this masternode changed recently."
« Last Edit: October 10, 2017, 01:21:23 am by 616westwarmoth »