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 ... 111 112 113 114 115 116 117 [118] 119 120 121 122 123 124 125 ... 127
- You only have to send the 500,000 BBP once From somewhere, To the Controller wallet escrow address (using the sendtoaddress command), Once per COLD sanctuary.  Once the funds are sent they are LOCKED.  (see masternode outputs)
- If you want to perform a dry run of emptying out the funds, follow the paragraph we posted about COIN CONTROL.
- If you need more Testnet funds paste your address here and then you can start more
- You cannot accidentally spend the 500,000 locked escrow unless you accidentally went in coin control and unlocked the funds
- The main part of the guide (up to the FAQ beginning) covers everything you need to do to start a new sanctuary, you dont need to follow whats in the FAQ unless you are having troubles

admin+togo=thanks for no help=

my 500k in masternode wallet was disappeared=

now im broken stick on masternode and all with bbp=

no dev help

happy time with this shit coin


togo+admin= 2 testers= nice, noob coin

Mine are humming along with no problem, and Im running on 3 different platforms:  Jessie, Vultr debian, and Windows, and havent had any problems.

Maybe just come back after you let the big dogs figure it out.

Also very strange

I remembered I had like 30+ million tBBP coins

From Yesterday:
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "",
  "balance": 33548253.56424391,
  "privatesend_balance": 0.00000000,
  "blocks": 38467,
  "timeoffset": 3,
  "connections": 7,
  "proxy": "",
  "difficulty": 0.2178060202002745,
  "testnet": true,
  "keypoololdest": 1507446796,
  "keypoolsize": 1003,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

And now after running some of these retirement commands I now have:

Today/This Morning
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "",
  "balance": 7569.69500000,
  "privatesend_balance": 0.00000000,
  "blocks": 39347,
  "timeoffset": 3,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.3709311342166779,
  "testnet": true,
  "keypoololdest": 1507446797,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

Im not sure why I didnt notice this sooner O_O

Inbetween those two getinfo commands, my Console window history shows I ran:

setgenerate false
setgenerate true 2
setgenerate true 1
exec retirementbalance
exec tradehistory
exec listorders
exec order buy 1000 rbbp .5
exec listorders
exec listorders
exec retirementbalance
exec retirementbalance
exec listorders
exec tradehistory
exec retirementbalance

Good catch, yeah, I had 80MM tbbp yesterday also, and now only have 300K.

Alright this was worthwhile, I have a huge bug to fix, so lets stop testing retirement accounts til I get back with the patch.

To free up your missing funds, just restart the wallet and it will come back.  (Its technically still there, its just not adding things up right after executing the retirement commands).

Hmm I dont believe my testnet wallet is locked, not seeing a locked symbol in bottom right either?

Heres a paste of my testnet3/debug.log:

Looks like my log is 6 hours ahead of BiblePay RPC

exec retirementbalance
  "Command": "retirementbalance",
  "balance": 75982

(Ill try to keep helping testing, Ill keep periodically checking the thread, Im at work atm hehehe, Dont tell my boss :P)

LOL on the boss.  Hmm, just to verify, your wallet is not encrypted is it?  If not then its probably not locked either.
Maybe we can try this backward as I dont see anything in the log so I would need to add special logging for this but first, maybe if you try selling and I try buying?

Try to sell a different quantity I just did this:
exec order buy 8000 rbbp .01

Try to Sell 8000 ?

I have an issue with my controller node not syncing for 29 hours . 
It happened after I upgraded the sanct node to v "" . 

Windows wallet is still v.

telnet to sanct node at port 4001 connects np.

Code: [Select]
mnsync status

  "AssetID": 1,
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

masternode start-alias MNode1
  "alias": "MNode1",
  "result": "failed",
  "errorMessage": "Sync in progress. Must wait until sync is complete to start Masternode"
whats the IP of the node that wont sync? Ill check to see if you were banned.
Also see if you delete your banlist.dat and restart you may sync?
Next if it does not sync then check the end of the debug.log for an error.

I see my wallet sent the escrow but nothing happened- is your wallet unlocked btw?

Also please see if there is an error in your debug.log, something about Unable to send escrow for trade?

Im 34.208, been 18+ hours active, still hummin!

Retirement Accounts WIki:

Tools >> Debug Console

exec retirementbalance
exec tradehistory
exec orderbook
exec listorders
exec order [  Buy/Sell/Cancel ]   Qty  Symbol [Price]

I placed a buy RBBP order, 1000 RBBP at 0.5 BBP each
Sweet, thats cool, well let me write my retirement balance first before we trade.
Mine is "exec retirementbalance" 572054
Now Im going to trade with you:   exec order sell 1000 rbbp .5
exec orderbook
I see that in order to see this orderbook properly, you have to drag and widen your RPC console out! Please widen it then you can see matching sales and buys
Togo I dont see you in the orderbook.
I just did an exec order buy 5000 rbbp .5
Can you please try an opposing sell now?

Also please write your balance down first so we can see if it changes.

Hahaha, I guess we shall see what happens in a few hours :) , masternode/sanctuary has been live for 5 hours 20 minutes so far. Im not sure if I was just impatient on v1.0.5.6, or if v1.0.5.8 fixed my issue, or if my crontab actually is wrong.

Ive just modified crontab:
crontab -e

Changed this:   
* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/ >/dev/null 2>&1

To this:
* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/

Hows it going guys?  Is it still humming along?

I see 207.244 and 34.208 figured it out (and my 3 nodes).  So we have 5, thats pretty good.
Everyone else is still hosed.

So is anyone ready for a retirement trade? Can someone post their retirement account balance here?


oooo Interesting, no changes ( other than updating to v1.0.5.8 ) and now later masternode has Enabled status!

My crontab is:

* * * * * cd /home/ubuntu/.biblepaycore/watchman && ./venv/bin/python bin/ >/dev/null 2>&1

My login name is:  ubuntu
Hmm, note that 1058 relaxes the watchdog timeout for the network from 4 hours to 8 hours, so the problem will still reappear if the crontab doesnt work LOL, so anyway just try running the crontab without the >/dev/null suffix, see if it works, if it doesnt try changing to the shortcut ~/.biblepaycore for the beginning CD part of the command etc.

where i have to setup configs+watchman
i see 2 folders with biblepaycore

cd /home/klondike/biblepaycore
cd ~/.biblepaycore$
Its possible to put it anywhere, but I recommend ~/.biblepaycore as the logs go there and its considered ONE installation if you put watchman in there.

Hmmm, my Masternode has been stuck in PRE_ENABLED as well, I waited a good 45+ minutes, but was still stuck in that state, Ill try updating from v1.0.5.6 to v1.0.5.8 and report back
Sorry if this sounds dumb as I read your prior post, but could you also check this :
Please dump your crontab -e contents and try to exec that manually? Just to ensure the whole line minus the "dev null" part runs without an error?

I had this problem the other day, my watchman ran from the command line but not from crontab- that put me in the "PRE_ENABLED" state.  But since crontab was not running every 5 mins, it never transitioned to "ENABLED".  Once I fixed the crontab, everything was fine, and now ive been up for 2 1/2 days. 

I also learned the way watchdog and POSE work in a more detailed way.

Basically, watchdog enforces the Public IP and the proof-of-service.  If another node catches your nodes public IP not responding once in an 8 hour period it remembers that, and tries to vote you for Non payment.  You have up to 8 hours to fix it.  If a person is on vacation and their node is down more than 8 hours, the watchdog expires. 

This is good, because it means to get paid in Sanctuaries you have to rent public VMs and they have to stay up, otherwise you fall out of payment pool.

I updated my Sanctuary/Masternode and Home Wallets to v1.0.5.6
and updated Watchman to

Im getting WATCHDOG_EXPIRED status

The tests for watchman ran fine,
but when I run I get the below simplejson.scanner.JSONDecodeError error:

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

Traceback (most recent call last):
  File "bin/", line 244, in <module>
  File "bin/", line 191, in main
  File "bin/", line 24, in perform_biblepayd_object_sync
  File "lib/", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/", line 116, in import_gobject_from_biblepayd
    object_hex = biblepaylib.SHIM_deserialise_from_biblepayd(object_hex)
  File "lib/", line 204, in SHIM_deserialise_from_biblepayd
    obj = deserialise(biblepayd_hex)
  File "lib/", line 229, in deserialise
    obj = simplejson.loads(json, use_decimal=True)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/"                                 , line 533, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/",                                  line 370, in decode
    obj, end = self.raw_decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/",                                  line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
simplejson.scanner.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 115 (                                 char 114)

Togo, could you please try deleting the /watchman directory, and completely reinstalling watchman, and delete mncache.dat, and restart the biblepayd, then retry the test with watchman from the command line? Lets see if it was a permission error when writing the dependencies from the "install.txt" list, or possibly, something loaded into the Watchman database that cant be parsed as JSON.

my node is  stuck in "pre-enabled" status.
not sure if it's relevant but it's happening after i upgraded to ""

"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"
Yeah, that happens when watchman is not actually running in the cron.
Please do this:
type 'crontab -e' , copy the exact command you typed into your cron into notepad.
exit crontab.

Now type the command from bash.  Tell me if it throws an error (Im sure it will most likely).
Then fix the crontab.

Klondike,  this guide is not for newbies.  Why dont you have your Senior IT specialists google other coins like Chaincoin and Dash and explain how their video is better?  Its NOT.  It requires patience and doing it exact.  I went through the guide and it works.  I updated the one entry for the crontab yesterday.  I believe your "WATCHDOG EXPIRED" is the same issue as above.  Let me know what the output of the above command is.

Once you figure it out, go ahead and make a video for us, and we will post it here.

By the way, the correct commands are not preceded by biblepay-cli.  Some people use RPC, some use bitnet, some use biblepayd, its common sense to precede your commands with biblepay-cli, so the guide stays as is.

General Discussion / Re:
« on: November 13, 2017, 07:44:11 am »
why is  dead?

ROB can you fix it? thanks
This is happy_merchants BX.  I sent him a PM this morning.

togo: your tutorial about run mining under linux is perfect!!!

im tried do my tutorial

.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  =if blocks readed then we can start compilation
3.  ./biblepay-cli -testnet masternode genkey   =got it
4.  ./biblepay-cli -testnet getaccountaddress TEST =got it
5.  i send 500k from testnet wallet to masternode wallet got it.... i see 500k in da MN wallet and its confirmed 7/7
6.  ./biblepay-cli -testnet masternode outputs  =got outputs
7.  im opened masternode.config in tesnet3 folder and addded POKUS IP:40001 93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR 7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c 1

7.5   ./biblepay-cli -testnet mnsync status   =ASSETID:999   =999 its OK

8.   now on testnet wallet in folder biblapaycore im opened config file and added this


Saved it, closed and restarted testnet wallet  =WORK

9.on linux the SANCTUARY WALLET STOPED wallet and open biblepay.conf and added this

rpcport=9998  biblepay aka admin doesnt know that this rpcport have to/must be add in this config  >:(

saved config and run masternode-linux-wallet again

and here is your tutorial bugs:

1st bug:

PART 4 - Run Sanctuary Linux Wallet Testnet
On remote Linux machine:
1. Enable & Run Wallet in Testnet mode:
  newbies dont know how run testnet wallet add this command

./biblepayd -testnet -daemon

when i added rpcport=9999 to linux=masternode wallet WATCHMAN ran without errors:


tommorow ill do VIDEO TUTORIAL for idiots=newbies

i have this questions:

masternodewallet is HOT wallet?
controllerwinwallet is COLD wallet?

masternodewallet raising balance=why,when my setup was wrote only testnet=1, why mining?
masternodewallet cancelled/delete= i receive 500k coins back?
masternodewallet raise balance for % reward for block?
controller wallet balance raising same like on masternode wallet? using same like when i have wallet.dat on 2 different wallets,but see same coins on both of it?

thanks for understanding this things

ADMIN: immediately fix your wiki tutorial:

add this line when compiling watchman

on linux config you add this rpcport=9998

YES, Your Sanctuary is Running!  Right On.


Ill add the biblepay -testnet to the wiki - note daemon is not required as you should have daemon=1 in the config.

Your questions:

masternodewallet is HOT wallet?

-> The Sanctuary is HOT when the BBP is in it (not recommended).  The Sanctuary is Cold when the BBP is in the controller wallet (RECOMMENDED).

masternodewallet raising balance=why,when my setup was wrote only testnet=1, why mining?
-> The Sanctuary Can mine, if it is in sync.  No problem.

masternodewallet cancelled/delete= i receive 500k coins back?
-> Yes, to cash out your sanctuary, Enable coin control from SETTINGS, then go to Send Money, then click COIN CONTROL, then UNLOCK ALL YOUR LOCKED FUNDS BY TOGGLING THE LOCK, Then check the 500k, then click OK, then Send the money Out of the sanctuary and it will not be a sanctuary anymore.

masternodewallet raise balance for % reward for block?
-> I dont know please refrase this.

controller wallet balance raising same like on masternode wallet? using same like when i have wallet.dat on 2 different wallets,but see same coins on both of it?
-> No, the rewards for running the sanctuary go to the Controller wallet (wherever the Hot funds are).

ADMIN: immediately fix your wiki tutorial:

add this line when compiling watchman

on linux config you add this rpcport=9998

-> OK

Pages: 1 ... 111 112 113 114 115 116 117 [118] 119 120 121 122 123 124 125 ... 127