Bible Pay

Read 69005 times

  • tiras
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #150 on: November 10, 2017, 01:23:27 pm »
finished configuring the test sanctuary .

now it shows in the "masternode list" output  as "PRE_ENABLED" .
Do I need to do anything else to finalize it ?


[email protected]:~/biblepay/src# ./biblepay-cli masternode list
{
  "2b41b04ac488c033073562090aba186ccf57faf8ecae00dbc1f072a0ac9eebdf-1": "ENABLED",
  "82da38dd4db20bc6fa5fd30ebeda707d1edbce1b3890c386497db7f4abffe90c-1": "ENABLED",
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"


status has changed to "ENABLED".   
is it OK now?   can you confirm it from the admin side ?


  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED"


  • klondike
  • Full Member

    • 189


    • -10
    • October 10, 2017, 09:00:24 am
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #151 on: November 11, 2017, 07:47:49 am »


all tutorials doesnt working

0.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  if block 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

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  WORK

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

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

saved config and run masternode-linux-wallet again


10. in controller windows wallet opened debug win and write this command masternode start-alias POKUS







where is bug on my side? any help guys?



« Last Edit: November 11, 2017, 09:32:34 am by admin »


  • Rob Andrews
  • Administrator

    • 2165


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #152 on: November 11, 2017, 09:33:39 am »

all tutorials doesnt working

0.    installed linux wallet
1.  ./biblepayd -testnet -daemon
2.  ./biblepay-cli -testnet getinfo  if block 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

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  WORK

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

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

saved config and run masternode-linux-wallet again


10. in controller windows wallet opened debug win and write this command masternode start-alias POKUS







where is bug on my side? any help guys?

I removed your swear comment.
Please dont swear here. 


Try going to the controller wallet and copy your txid of your collateral to the clipboard, and type

getrawtransaction tx_id_of_collateral 1

Note how nothing comes back.  That means you have no collateral set up for the masternode.




  • Rob Andrews
  • Administrator

    • 2165


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #153 on: November 11, 2017, 03:20:14 pm »
Anyone who has "restart required" or "watchdog expired" please check your watchman-on-the-wall status.
If watchman isnt running, POSE fails, then watchdog expires, then your node fails to get paid its sanctuary payment.

In my case, 2 of my sanctuaries crontabs were working fine, but one linux box kept showing watchdog expired.
In this particular case, I had a local user account that was set up to run biblepay and watchman.  However, in my crontab I had the path for watchman configured as the root home directory as the start dir (not the local user).  So please, verify the user that you will run biblepay as, grab the full user path, and ensure the start directory is correct for watchman, then edit your crontab -e as the actual user and make the adjustment.  Once I did that, my watchdog status went back to ENABLED.

So now my 3 nodes are running.  Will you all please ensure your masternodes are running?  As we only have 30 days left for testing.

Also please get ready for a new release.

Those on Linux, go ahead and update to 1.0.5.6.  Then we will try a few retirement account trades.

Windows is compiling now.

« Last Edit: November 11, 2017, 03:22:10 pm by admin »


  • Rob Andrews
  • Administrator

    • 2165


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #154 on: November 11, 2017, 08:51:22 pm »
1.0.5.6-Testnet-Leisure Upgrade

All,

1.0.5.6 is now available for download.  Please upgrade including controller wallets.

To start testing retirement accounts please see this page:

http://wiki.biblepay.org/Retirement_Accounts


  • Rob Andrews
  • Administrator

    • 2165


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #155 on: November 12, 2017, 07:52:29 am »
i have to have install any watchdog?what is it? where is here in this forum tutorial how to install it?




please set on your web what wallet is last ... its so hard for you add icon above button downloading wallet what version wallet we downloading?  ::)



Watchman has been in the help guide since the beginning.  Watchdog is part of watchman.
It clearly says in the tutorial you have to comment out mainnet and uncomment testnet.
I have no clue how to answer your question when you say "it didnt work" because that could mean a million things.
The question is when you make ONE change not TWO to the watchman conf file, then follow the instructions, run it again and see if it runs without any output - and only do it when biblepay dameon is already running.  You have to do some things yourself, we dont know your machines paths.

As far as the version number on the web download, put a ticket into github with that suggestion and be very detailed as to what you are talking about.

If you dont like the tutorial try using dashs tutorial or tell us how to make it better.  Its NOT for newbies. 

« Last Edit: November 12, 2017, 10:30:59 am by admin »


  • togoshigekata
  • Sr. Member

    • 466


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #156 on: November 12, 2017, 10:46:34 am »
These are my notes from doing Masternode testing a month ago:  http://forum.biblepay.org/index.php?topic=16.msg151#msg151

I am going to re-setup a masternode today and make sure every step is correct and clear :)


  • klondike
  • Full Member

    • 189


    • -10
    • October 10, 2017, 09:00:24 am
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #157 on: November 12, 2017, 12:11:19 pm »
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

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  =WORK

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

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
rpcport=9998  biblepay aka admin doesnt know that this rpcport have to/must be add in this config  >:(
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

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:

NOW MY MASTERNODE WORKING OR?




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





« Last Edit: November 12, 2017, 02:06:31 pm by klondike »


  • Rob Andrews
  • Administrator

    • 2165


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

testnet=1
rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256

Saved it, closed and restarted testnet wallet  =WORK

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

rpcuser=hokuspokus
rpcpassword=hokuspokus123
rpcallowip=127.0.0.1
rpcport=9998  biblepay aka admin doesnt know that this rpcport have to/must be add in this config  >:(
listen=1
server=1
daemon=1
logtimestamps=1
externalip=IP:40001
maxconnections=256
masternode=1
masternodeprivkey=93W87RB7sVxu72souCWdHGpTWYFFF84oyRe81hzZcHEzWGdogkR

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:

NOW MY MASTERNODE WORKING OR?




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

« Last Edit: November 12, 2017, 05:59:12 pm by admin »


  • togoshigekata
  • Sr. Member

    • 466


    • 25
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #159 on: November 12, 2017, 08:53:41 pm »
I updated my Sanctuary/Masternode and Home Wallets to v1.0.5.6
and updated Watchman to 1.0.0.1b

Im getting WATCHDOG_EXPIRED status

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

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

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 116, in import_gobject_from_biblepayd
    object_hex = biblepaylib.SHIM_deserialise_from_biblepayd(object_hex)
  File "lib/biblepaylib.py", line 204, in SHIM_deserialise_from_biblepayd
    obj = deserialise(biblepayd_hex)
  File "lib/biblepaylib.py", line 229, in deserialise
    obj = simplejson.loads(json, use_decimal=True)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/__init__.py"                                 , line 533, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  line 370, in decode
    obj, end = self.raw_decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  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)


  • tiras
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #160 on: November 12, 2017, 10:57:56 pm »
my node is  stuck in "pre-enabled" status.
not sure if it's relevant but it's happening after i upgraded to "1.0.5.6"

"78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "PRE_ENABLED"



  • klondike
  • Full Member

    • 189


    • -10
    • October 10, 2017, 09:00:24 am
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #161 on: November 13, 2017, 01:24:07 am »
i got same problem like TOGOSHIGEKATA

Im getting WATCHDOG_EXPIRED status

and no coins going to my controller wallet

this all tutorials is bad!!! nobody from my neighborhoods cant setup masternode and 3 guys is IT senior admins: all have same problems like me:
watchdog still expired, coins  in controller wallet no raise and when we tried to start masternode from controller always we see this



i believe that masternode wont be start if exists still this bugs

and this guide need next university diplom for me
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.   :o
-from settings? where,in controller wallet?
-go to send money?
-click COIN CONTROL
-unlock all your locked funds by toggling lock?  :o


where is problem by tutorial with RUN MASTERNODE from controller wallet by command MASTERNODE START-ALIAS NICK

important question is: when i sending 500k from controller wallet to masternode wallet: classic way? send 500k and thats all?

BIBLEPAY in wiki can you fix this
7) Use the following command to check status:
masternode status

correct commands for masternode

 ./biblepay-cli -testnet mnsync status
./biblepay-cli masternode list
./biblepay-cli masternode list-conf
./biblepay-cli masternode start-alias
./biblepay-cli masternode help
./biblepay-cli masternode status
« Last Edit: November 13, 2017, 05:55:05 am by klondike »


  • Rob Andrews
  • Administrator

    • 2165


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #162 on: November 13, 2017, 07:50:34 am »
my node is  stuck in "pre-enabled" status.
not sure if it's relevant but it's happening after i upgraded to "1.0.5.6"

"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.
« Last Edit: November 13, 2017, 07:52:35 am by admin »


  • Rob Andrews
  • Administrator

    • 2165


    • 29
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #163 on: November 13, 2017, 08:03:58 am »
I updated my Sanctuary/Masternode and Home Wallets to v1.0.5.6
and updated Watchman to 1.0.0.1b

Im getting WATCHDOG_EXPIRED status

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

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

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 87, in sync
    (go, subobj) = self.import_gobject_from_biblepayd(biblepayd, item)
  File "lib/models.py", line 116, in import_gobject_from_biblepayd
    object_hex = biblepaylib.SHIM_deserialise_from_biblepayd(object_hex)
  File "lib/biblepaylib.py", line 204, in SHIM_deserialise_from_biblepayd
    obj = deserialise(biblepayd_hex)
  File "lib/biblepaylib.py", line 229, in deserialise
    obj = simplejson.loads(json, use_decimal=True)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/__init__.py"                                 , line 533, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  line 370, in decode
    obj, end = self.raw_decode(s)
  File "/home/ubuntu/.biblepaycore/watchman/venv/local/lib/python2.7/site-packages/simplejson/decoder.py",                                  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.



  • klondike
  • Full Member

    • 189


    • -10
    • October 10, 2017, 09:00:24 am
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #164 on: November 13, 2017, 08:33:51 am »
im installed my watchman with tutorial: its step by step of course....
then delete # in testnet and add # in mainnet
then setup crontab -e with this * * * * * cd /.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1

watchman ran and dont know if working ...

btw: im stuck on 38150 blocks testnet wallet .... how can i fixit?


BIBLEPAY aka ADMIN=   DO VIDEO TUTORIAL FOR ALL !!!!!!!! AND BTW: BITCOINTALK FORUM  is DEAD FOR BBP ... and it looks that BBP ending when doesnt exists no forum  ;D ;D ;D