Bible Pay

Read 59612 times

  • Rob Andrews
  • Administrator

    • 1978


    • 27
    • 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 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 Andrews
  • Administrator

    • 1978


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #31 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

    • 427


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #32 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

    • 614


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #33 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

    • 614


    • 31
    • September 01, 2017, 08:02:57 pm
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #34 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 Andrews
  • Administrator

    • 1978


    • 27
    • 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 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

    • 427


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #36 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

    • 427


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #37 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

    • 427


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #38 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 »


  • Rob Andrews
  • Administrator

    • 1978


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #39 on: October 10, 2017, 09:24:12 am »
Togo,

Thanks for the guide buddy, you are the man!  I think what we can do is, once we get this process down, Ill edit the create_masternode to be the 'highly technical' version, just to refer to as a sanctuary owner.  We can take your version, which includes more details and make a linked page for newbies who need more help (or something to that effect).

Anyway let me just try to answer the questions from your post first, instead of reposting the entire big post, Ill be back.


  • Rob Andrews
  • Administrator

    • 1978


    • 27
    • 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 10, 2017, 09:45:08 am »
I just wanted to mention that I have been a little busy lately (other than being interrupted to upload the pool, which is a huge necessity), with a brand new cryptocurrency feature for biblepay.  I think it might be "the killer" feature for us.

I'm thinking about adding colored coins into biblepay with an integrated 401k or retirement account fund inside the wallet.  And in-wallet trading.

I'm thinking maybe we can be the first coin with the ability to trade BiblePay for our second asset inside the wallet (other than Ripple, but technically, Ripple is a network of market makers making existing markets).  This is a little different.

I'm thinking we emit a new deflationary colored currency (called either retirement coins or 401k coins) inside the wallet on a schedule decreasing by 1% per day.  Then, the wallet will keep track of both normal balance and "colored coin" balances.  So you would have your BBP balance and your rBBP balance. 

   Starting on the day we have retirement coins, the retirement system would emit 1 million retirement coins per day equally divided over 202 daily blocks to the miners who mine the blocks.  However each day, the emission rate would decrease by 1% .  So on day 2 we would emit 10,000 coins less (or 990,000 retirement coins over 202 blocks).  Each block solver would receive normal BBP, plus a separate share of colored retirement coins.  If you mined 4,000 retirement coins on day #1, your balance would now be:  1,000,000 BBP and 4,000 rBBP (retirement bbp). 

You cannot send colored coins to an exchange to sell them and cannot buy colored coins on an exchange.
All colored coins must be sent in a transaction that includes a reference to the root of the colored coins (another words, the colored indicator on the tx, the previous output is colored, and the new vout for the receiver is colored).

Available coins for spending will never select colored coins for spending (IE They cannot be spent). But they can be Traded for BBP with other holders through Trade transactions.

A new RPC command will allow you to send colored coins back and forth among others, if you want to give them to others.

Now here is where it gets interesting.  If we view the colored coins as a deflationary retirement account (assuming that IF they are becoming scarcer, storing FIAT in rBBP would theoretically result in a gain in value).

We implement in-wallet trading to allow trading from BBP to rBBP.  So we would have RPC commands to "execute order SELL 9000 rBBP for 1100 BBP" for example.  Other in-wallet users would "execute order BUY rBBP 5000 for 700 BBP".  When the matching engine matches an order over the nodes, one masternode  who is the chosen winner of the round (chosen winner meaning which masternode has the closest hash to the center of the blockhash for the current BBP block, can be active market maker for this tx).

At this point, the masternode jumps in, Locks the trade, grabs the collateral from the seller and the buyer, crosses the trade, then unlocks it and it is completed.  We will have a Trading log in biblepay, so you can go into your separate debug file and monitor STEPS that occur during trading.  (In case something goes wrong partially through).

Lastly, partially executed orders would be changed via a MODIFY - so if only 1000 got filled your order would readvertise with the partial amount left.

In this way, we would have in-wallet trading, colored coins, and a second deflationary asset inside biblepay.

My projection shows that the retirement coins would deflate for 4000 days before reaching a floor where they would be emitted at approximately 1 per day (if we start with a million per day).  I think at that point, I would like the system to reverse split the coins and start over, so that we perpetually have a deflationary retirement asset inside BBP.

One benefit of having this particular feature is we would attract outside investors that would need to buy BBP in order to have the ability to buy rBBP and they also potentially download the wallet and be users and might have a tendency to be long term holders.






  • Rob Andrews
  • Administrator

    • 1978


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #41 on: October 10, 2017, 10:39:41 am »

QUESTION: Are we sending coins to ourself?
It is OK to send the balance to yourself or from another node (I tested both).  The important thing is to make the amount exactly 500000 and dont click instant send or any other options.

If you are creating a Hot wallet (IE funds live on the masternode) you would send the 500k to the masternode wallet.  Now that we know cold wallets work, the recommended way is to send the funds To the cold wallet (IE the home controller wallet).


QUESTION: Which node is the Masternode?
  -> The masternode is the sanctuary running at the hosting company with the static IP.

QUESTION: Does the Masternode actually hold coins?
-> In a Hot masternode scenario, the masternode holds the coins, otherwise the masternode wallet is empty.
Biblepay puts a lock on the escrow when the masternode starts.

QUESTION: Is there a certain label that should be used for getaccountaddress?
One pitfall I noticed is if you use the same label more than once sometimes I get a new address.  I would recommend something short such as "MN1".  To ensure its only in the book once, click Receiving addresses and if it is already there as MN1, copy it to clipboard.

QUESTION: How to deal with fees when sending? Does amount have to be 500,000 exactly?
Fees are OK as long as you dont click the checkbox to Subtract fees.  Fees are stored in a different vector, so the vout is still 500,000.


QUESTION: Why port 51472? And does it need to be changed in any firewalls?
-> Oh no, this is a mistake, I will modify the guide.  This should be 40001.  Also in the UFW command list, it should be 40001.
Port 40001 is BBP testnets P2P port, 40000 is Prod BBP p2p port.



QUESTION: What IP address goes in this part of the config? "externalip=your_public_ip"
-> So when you rent your VM, and click into its hosted properties, you should see a public IP.  You should copy that and make it like this:
externalip=your_masternode_public_ip
NOTE: This is only required on the sanctuary side, not on the controller wallet side.


QUESTION: What are these config settings doing? Can the Home Wallet now control the Linux Wallet? or reverse of that?
-> These config settings only allow the home controller wallet to start and stop the masternode.  This is not only to safeguard your eventual 1 million BBP escrow if it goes up in value (to prevent vultr host from stealing it), but also because of Proof-Of-Service.  Dash has created POSE, which monitors how much uptime your masternode has stayed up and eventually becomes important if we have more than about 800 masternodes, these nodes start falling to the back of the payment queue and do not get paid if they need restarts.  When they fail and need restarted, it is easy for home computer controller wallet to start the masternode again.


QUESTION: Im stuck, help! :)
I opened /testnet3 debug.log with baretail and I see action happening, is their a syncing Period?
-> Yes, unfortunately this is a very frustrating, thats one reason I had to go to 1 minute blocks in testnet.  The wallet requires blocks to be moving for the 'mnsync status' command to iterate to the next step.  Do a setgenerate true 5, to keep blocks moving.  After 'mnsync status' shows 999, then you can start and stop the masternode and see the masternode list 'masternodelist'.


QUESTION: Where does Watchman fit in the process? What is Watchman? what is it doing?
-> Yes, I know.  Why we have to have yet another piece of software called Watchman-on-the-wall?  Watchman implements proof of service and one major superblock budget feature.  Let us say without it, Dashs POSE system would be in tatters.  Basically, if BBP ever reaches say $50 million market cap and then we have 1000 masternodes, situation A is without watchman, all the nodes who do a start on windows and then start playing video games a few hours later and kill the node by accident those nodes would not be doing anything for us, and would still get paid fully.  With watchman, every node has to send a watchdog alert every couple hundred blocks and prove their static IP and how long they been online.  This means as competition heats up you really have to have provided good service to stay in the payment queue. The other thing watchman does is collects a database of gobjects.  Governance objects are stored in tables.  Votes are kept.  It allows deleting governance objects by masternode.  The most important thing it does is when we create a very complicated budget that got approved from a proposal, it creates a text file of budget items for the superblock.  Without it the superblocks dont work very well.  Dash probably could have added code to masternode governance for all of it, but they chose this modular design in case they want to have masternodes upgrade the superblock code side and NOT the entire network to upgrade the wallet.  We inherited it so we have to embrace it now - what I am hoping is the version we ported is already stable and I can code a lot more on the web side and sort of freeze what we have for a year and grow as we are until we have our extra few IT devs helping me out to ensure we have the bitcoin commits committed constantly.

Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.

STUCK: What am I doing wrong here?
-> In this case I would go to the masternode and edit the biblepay.conf, and ensure rpcallowip=127.0.0.1 is set.
Also check to make sure watchman.conf has testnet uncommented and prod commented.


  • togoshigekata
  • Sr. Member

    • 427


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #42 on: October 10, 2017, 01:01:28 pm »
Thank you so much for answering my questions!!!  :D


  • Rob Andrews
  • Administrator

    • 1978


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #43 on: October 10, 2017, 01:08:19 pm »
Thank you so much for answering my questions!!!  :D

No problem.  I am going to edit the create_masternode wiki page now (with that port number) etc.  I tested a cold masternode yesterday and it worked.

What I would like to do is get a few of us together here in a synced quorum, so we have at least 4 running masternodes on our synced list.
Then I can go ahead and create a governance object and see if everyone sees it.

Please, post here if you have your running static IP masternode in the masternode list.


  • Rob Andrews
  • Administrator

    • 1978


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #44 on: October 11, 2017, 08:25:12 am »
My node is a cold node.  The only thing I've yet to get working is the watchman. 

Mine is 104.207.140.159 (cold node, no watchman, Vultr).

Could you please tell us something about a non-watchman node?  I am under the impression from interpreting the watchdog code that after a certain number of blocks passes, your non-watchman node status should go from "ENABLED" to NEW_START_REQUIRED.   

It will be interesting to know if you get paid your masternode fees with watchman off.  Are you receiving subsidies of 8300~ or so?  Note in your receiving list, the subsidy to the masternode comes in BY NAME, not by address.  For example I named my masternode DEBIAN in the cold sanctuary, so the payments come in the receiving list to DEBIAN.

Either way you will probably get tripped up when we get to the voting but it is interesting to know if you are getting paid, and when you get tripped up without watchman.