Author

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 733. (Read 243376 times)

full member
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
BiblePay just got listed at https://masternodes.online/ (and it's first on the list right now), how come? Did someone pay for this or the site owner listed it for free?

http://forum.biblepay.org/index.php?topic=57.0

Looks like 616west jumped on it! awesome!

Yes, the owners contacted me and asked if we were ready.  I asked for a price quote, and they shot me a better number, so I jumped on it from my own funds.

When I get my allotted payment for the proposal, we'll have to deal with the sticky issue of what to do with the excess.  My thoughts have been this.  If the cost had gone up, I would have paid the extra from my own funds (if possible) and then asked to be reimbursed in the next cycle.  Since the cost has gone down (due to the increase in value in the last few days), I should have a good amount of extra.  My thought is since I would expect to be reimbursed, this excess belongs to the community and should be sent to the Orphan Fund address.  

No, in my opinion we dont have to worry about that.  I think a proposal is a proposal.  I dont expect Togo to give his money back if we rise and I dont expect him to be reimbursed more if we drop.

Imagine payroll for the circus at biblepay where every 2 weeks we re-pay the "remains" from the prior payroll cycle.


EDIT: I think we should put a disclaimer on the system to not put proposals in unless you have the wherewithal to take the appropriate risk.

full member
Activity: 1260
Merit: 115
616westwarmoth had fantastic advice on Backing up your Wallet: https://www.reddit.com/r/BiblePay/comments/7lksp4/backup_walletdat/
please everyone encrypt and backup your wallets, and dont forget the encryption password!

"jaapgvk 3 points 6 hours ago
I'm not sure, but since BBP is partly based on bitcoin, there is a way in which the bitcoin qt-wallet works that doesn't give you 100% certainty that only making a wallet.dat backup once is enough on the long run.

See this explanation:
Preventing and Recovering from Change Address Disasters.
Incorrect use of Bitcoin change addresses account for many cases of loss or theft of funds. Here are some disaster scenarios and ways to avoid them.

1. Backup Failure Alice uses Bitcoin-Qt. Understanding the importance of backups, she created an encrypted wallet backup long ago and stored it in a safe place. After making dozens of transactions with Bitcoin-Qt, Alice’s hard drive crashed.
Alice bought a new hard drive and then re-installed Bitcoin-Qt on it. She then restored her wallet backup. To her horror, Alice discovered the restored wallet was empty.

Explanation: Alice generated enough change addresses to overflow the original pool of 100. On the 100th spending transaction, Bitcoin-Qt moved Alice’s change (which happend to be her entire balance) into an address not in the backup. Restoring the backup only restored empty addresses.

Recovery: Even if a hard drive can’t boot an operating system, individual files can still be recovered. Using data recovery tools, Alice may be able to salvage the Bitcoin-Qt wallet from the faulty hard drive, and with it her lost funds.
Prevention:

Count the number of manually-created addresses and spending transactions since your last backup. If this number is greater than about 80, back up again. Weekly backups might be enough for most users. Set a very high value (e.g., 10,000) for the -keypool option, either as a command line parameter, or in the bitcoin.conf file. Switch to a deterministic wallet.

https://bitzuma.com/posts/five-ways-to-lose-money-with-bitcoin-change-addresses/"

===

jaavpgvk also has fantastic advice! Ive heard about this 100 thing but wasnt sure,
Could your provide any details on this 100 transaction functionality Rob?

Can anyone teach me more about this keypool thing?
Im worried about my private keys rotating/being reset and my backups of my wallet.dat in other locations becoming worthless.
Especially now that I am receiving daily payments from my Sanctuary.
newbie
Activity: 4
Merit: 0
Hello,

I'm having some issues with the miner at this moment and i'm at whit's end.

It was working just fine this afternoon ( when i started). Suddenly i can see that the wallet is still mining and my balance is unchanged. My worker is having recorded Hashps in the pool as well as in the mininginfo. After a couple of minutes, it stops adding coins to my balance. If i create a new worker it works again for a couple of minutes and then the same thing happens, i get no errors nor any signs what could be wrong. Please help me out here.

Thank you.
member
Activity: 98
Merit: 11
This is interesting. I have created the first Hindu Coin, and am Currently doing the ICO on Facebook and other Social Media, rather than on Bitcointalk. And I will be announcing Temple Coin on January 20th.


But I am interested in this.

I want to help people understand Ancient Books better. I have been a Certified/Ordained Hindu Minister since I was 17 (and Hindu since I was 14), but even as a Hindu, I have a deep understanding of the Bible.

I first read the Bible when I was 14 years old (which is why I left the Religion; everyone should go read that whole Book, and compare it to similar Books), and I read it from front to back. I know where everyone is in the Bible, you can find David is Saul for example, there are also other Books of the Bible in the Catholic: Apocrypha, and the Gnostic: Nag Hamadi Scriptures; and if you want to read the Regular Bible in great Detail, go to "BlueLetterBible.com" it creates a link for every single word in the Bible, allowing you to do all kinds of searches and look at what they are saying in multiple languages. It is similar to how "Red Letter Bibles" underline Jesus' words in Red, this is the Bible with Links.

Now, the following is a Quote, first a Quote that is not Benjamin Franklin, but is actually a Quote in his writings where he is Quoting someone else, and then right after that are his words.

“In old Time it was no disrespect for Men and Women to be call’d by their own Names: Adam, was never called Master Adam; we never read of Noah Esquire, Lot Knight and Baronet, nor the Right Honourable Abraham, Viscount Mesopotamia, Baron of Carran; no, they were plain Men, honest Country Grasiers, that took Care of their Families and their Flocks. Moses was a great Prophet, and Aaron a Priest of the Lord; but we never read of the Reverend Moses, nor the Right Reverend Father in God, Aaron, by Divine Providence, Lord Arch-Bishop of Israel: Thou never sawest Madam Rebecca in the Bible, my Lady Rachel, nor Mary, tho’ a Princess of the Blood after the Death of Joseph, call’d the Princess Dowager of Nazareth; no, plain Rebecca, Rachel, Mary, or the Widow Mary, or the like: It was no Incivility then to mention their naked Names as they were expressed.”

If common civility, and a generous Deportment among Mankind, be not put out of Countenance by the profound Reasoning of this Author, we hope they will continue to treat one another handsomely to the end of the World. We will not pretend an Answer to these Arguments against modern Decency and Titles of Honour; yet one of our Club will undertake to prove, that tho’ Abraham was not styl’d Right Honourable, yet he had the Title of Lord given him by his Wife Sarah, which he thinks entitles her to the Honour of My Lady Sarah; and Rachel being married into the same Family, he concludes she may deserve the Title of My Lady Rachel. But this is but the Opinion of one Man; it was never put to Vote in the Society.
member
Activity: 98
Merit: 10
BiblePay - 1.0.7.5
Leisure Upgrade


- Competetive mining feature:
  The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
  this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
  IF you run out of mining nonces, and only increments to 2 satoshi again if you run out.  However, when the block changes,
  the amount is reset to 0 again.  Alex and I have tested this and it appears to give a 5% mining edge.  Therefore I wanted
  to release this as quickly as possible for general consumption.  Since it gives a mining edge, I made the feature ON by default.
  To turn it off add the key: competetivemining=false to your biblepay.conf file.

- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).



Do we have to change the conf file? Or is it just an option?

Default is enabled. You can turn it off by adding competetivemining=false in biblepay.conf (if you were talking about that).
jr. member
Activity: 89
Merit: 7

And now I'm getting the same error again.
I deleted it many times, trying to resync , delete watchman database, and still have this problem, and my node is PRE_ENABLED on my node, and other nodes listed it as WATCHDOG_EXPIRED

also I see many WATCHDOG_EXPIRED (about 24)

Just tested mine. No problem found.

ok I try to debug this..
1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 have problem with data:
Code:
    "DataString": "[[\"trigger\",{\"event_block_height\":24600,\"payment_addresses\":\"BC99kkb2mvz6SRdAVYRsgKaoWeuYavYLUT|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BGdV31j9w9yM5CrCnsUsUyFZkwhAsDyDP3|BAqBZkMieZfES9LkVgcMmMPv3E68tZt9G8|BKPGxUJvi82hi7RA3gmPUT8a9tASjtrsMF|BP8BCkDc411a25KjsD2k9tRCWKLjGQFCGz|BAqBZkMieZfES9LkVgcMmMPv3E68tZt9G8|BB57LvFhNhYAeD8JSHTnQTmiKRYx4DkxG7|BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW\",\"payment_amounts\":\"250.0000|135000.0000|23171.0000|47203.0000|517000.0000|89320.0000|2894609.0000|867333.0000|16692.0000|312500.0000|125000.0000|186493.0000|400000.0000|42272.0000\",\"proposal_hashes\":\"8aee1d9574677f7c5030571d6244769ff17e9c1c91d3c36bcdfc883a817dc0d7|e6ff30af51064a281752a6b5fdc03bd9d2fa457af89e1a0021a93661a726c96e|664f6ebfb9de9c448f986dd266db259bf89d5b6ca1ca82af7d37eee4212a3f98|13d938defec6e110ef0df251654c544d5dc9c57cf015a1ea8bb60538899b5643|46e3ee892800b272a8fa44cf4eda13506c73c297c1bc4773a0b718e7f200b4d3|9b9b0c95d2390dcf8f6bdb3f30bb02a3bf8b8e2c83bf3ccf154cd337345e8835|23f3af5b2b93d57bb5319d6c01ec98c9b2f5ca40628311c5054841295360c679|5ec1b8496385159ae913b6341719ebab199c680305a02d87a3a69dc7b84a0563|3629e6cce8a71ade8fcd9a83e9566efce479f0a3562314aa71ae5446497e07cc|da0c60fd9de6aac40b1425aca56c200f4b0665f3196c060fe443c00061dbd4ab|fbdde6d5297525ea2f9732df0858068b1a76f953a7f3d68873c298bf5d6afd20|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|ab354293e413459c42d52a1511d5351a7a900c2c97cd4c81b6bbf261a196d0c2|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1\",\"type\":2,}]]",
at end is ...\"type\":2,}]]"
this "comma" breaking python json decoder.

ok ... I add replace to this string to fix json, but also I have many errors like this:
Code:
2018-01-02 21:53:06 	Invalid Proposal name [First Prod Proposal] (does not match regex), returning False
2018-01-02 21:53:06 No proposals, cannot create an empty superblock.
2018-01-02 21:53:06 No superblock created, sorry. Returning.
this is normal ?
I today try to run first time masternode, and everythings looks ok
Code:
biblepay-cli masternode status
{
  "vin": "CTxIn(COutPoint(f96df9063af005b942f5cb62844d0360567930d145bde7430c740b8a6c221fe3, 1), scriptSig=)",
  "service": "137.74.0.113:40000",
  "payee": "BBauqhusvhQJcjBZHgrC6r1eN5xc4DHqy7",
  "status": "Masternode successfully started"
}


I don't know how to make watchman working :/
newbie
Activity: 17
Merit: 0
BiblePay - 1.0.7.5
Leisure Upgrade


- Competetive mining feature:
  The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
  this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
  IF you run out of mining nonces, and only increments to 2 satoshi again if you run out.  However, when the block changes,
  the amount is reset to 0 again.  Alex and I have tested this and it appears to give a 5% mining edge.  Therefore I wanted
  to release this as quickly as possible for general consumption.  Since it gives a mining edge, I made the feature ON by default.
  To turn it off add the key: competetivemining=false to your biblepay.conf file.

- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).



Do we have to change the conf file? Or is it just an option?

it's an option, but I would change it if I where you Smiley
jr. member
Activity: 89
Merit: 7

And now I'm getting the same error again.
I deleted it many times, trying to resync , delete watchman database, and still have this problem, and my node is PRE_ENABLED on my node, and other nodes listed it as WATCHDOG_EXPIRED

also I see many WATCHDOG_EXPIRED (about 24)

Just tested mine. No problem found.

ok I try to debug this..
1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 have problem with data:
Code:
    "DataString": "[[\"trigger\",{\"event_block_height\":24600,\"payment_addresses\":\"BC99kkb2mvz6SRdAVYRsgKaoWeuYavYLUT|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW|BGdV31j9w9yM5CrCnsUsUyFZkwhAsDyDP3|BAqBZkMieZfES9LkVgcMmMPv3E68tZt9G8|BKPGxUJvi82hi7RA3gmPUT8a9tASjtrsMF|BP8BCkDc411a25KjsD2k9tRCWKLjGQFCGz|BAqBZkMieZfES9LkVgcMmMPv3E68tZt9G8|BB57LvFhNhYAeD8JSHTnQTmiKRYx4DkxG7|BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM|BNKh6Z8tKaEToFyQzcffgsR9gssjeCMZLW\",\"payment_amounts\":\"250.0000|135000.0000|23171.0000|47203.0000|517000.0000|89320.0000|2894609.0000|867333.0000|16692.0000|312500.0000|125000.0000|186493.0000|400000.0000|42272.0000\",\"proposal_hashes\":\"8aee1d9574677f7c5030571d6244769ff17e9c1c91d3c36bcdfc883a817dc0d7|e6ff30af51064a281752a6b5fdc03bd9d2fa457af89e1a0021a93661a726c96e|664f6ebfb9de9c448f986dd266db259bf89d5b6ca1ca82af7d37eee4212a3f98|13d938defec6e110ef0df251654c544d5dc9c57cf015a1ea8bb60538899b5643|46e3ee892800b272a8fa44cf4eda13506c73c297c1bc4773a0b718e7f200b4d3|9b9b0c95d2390dcf8f6bdb3f30bb02a3bf8b8e2c83bf3ccf154cd337345e8835|23f3af5b2b93d57bb5319d6c01ec98c9b2f5ca40628311c5054841295360c679|5ec1b8496385159ae913b6341719ebab199c680305a02d87a3a69dc7b84a0563|3629e6cce8a71ade8fcd9a83e9566efce479f0a3562314aa71ae5446497e07cc|da0c60fd9de6aac40b1425aca56c200f4b0665f3196c060fe443c00061dbd4ab|fbdde6d5297525ea2f9732df0858068b1a76f953a7f3d68873c298bf5d6afd20|df3815d09091445c1ce839e7cd29f995abf117837d74525da866b51bbdb7bc16|ab354293e413459c42d52a1511d5351a7a900c2c97cd4c81b6bbf261a196d0c2|ed9ec4a65237b7d54f1766dffe39f1fb18cbc99783c3495fb927610f3c3620a1\",\"type\":2,}]]",
at end is ...\"type\":2,}]]"
this "comma" breaking python json decoder.
full member
Activity: 465
Merit: 100
my wallet isn't syncing can someone help me fix please
linux or windows? in win try rebuild

westwarmoth
question

why did rm gove+mn.dat?  Wink for what?

in windows is there a way to rebuild without reinstalling?
newbie
Activity: 86
Merit: 0

And now I'm getting the same error again.
I deleted it many times, trying to resync , delete watchman database, and still have this problem, and my node is PRE_ENABLED on my node, and other nodes listed it as WATCHDOG_EXPIRED

also I see many WATCHDOG_EXPIRED (about 24)

Just tested mine. No problem found.
full member
Activity: 364
Merit: 102
BiblePay - 1.0.7.5
Leisure Upgrade


- Competetive mining feature:
  The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
  this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
  IF you run out of mining nonces, and only increments to 2 satoshi again if you run out.  However, when the block changes,
  the amount is reset to 0 again.  Alex and I have tested this and it appears to give a 5% mining edge.  Therefore I wanted
  to release this as quickly as possible for general consumption.  Since it gives a mining edge, I made the feature ON by default.
  To turn it off add the key: competetivemining=false to your biblepay.conf file.

- Pool SSL Support (change pool=http:// to pool=https:// and remove poolport=80 in biblepay.conf file to use SSL).



Do we have to change the conf file? Or is it just an option?
jr. member
Activity: 89
Merit: 7

And now I'm getting the same error again.
I deleted it many times, trying to resync , delete watchman database, and still have this problem, and my node is PRE_ENABLED on my node, and other nodes listed it as WATCHDOG_EXPIRED

also I see many WATCHDOG_EXPIRED (about 24)
newbie
Activity: 16
Merit: 0
That is really nice!! (That Biblepay is listed on masternode.online)
full member
Activity: 406
Merit: 101
1. In control wallet
gobject vote-many 3f22267e91222c6d761f8a83d781a0adfe833c3b42b790a0990abfb2a5923942 funding no
gobject vote-many 3f22267e91222c6d761f8a83d781a0adfe833c3b42b790a0990abfb2a5923942 delete yes
close wallet and delete mn*.dat, rm gov*.dat
2. In masternode, run
  biblepay-cli gobject list all triggers
 to check if it has just one trigger. If not, restart the masternode
3. Start the control wallet and unlock it, then
   masternode start-alias SANCTUARY_ALIAS
4. Check if it is synced in control wallet:
  mnsync status     ("AssetID": 999  means synced)
5. In control wallet, run:
  gobject list all triggers
  if you see two triggers, then do close wallet and delete mn*.dat, rm gov*.dat and wait a few minutes and start wallet
6. In masternode, run
   venv/bin/python bin/watchman.py
under the watchdog dir to check.

I had to delete the mn*.dat and gov*.dat at the Masternode as well as the Controlling wallet to get this to take.

And now I'm getting the same error again.
full member
Activity: 406
Merit: 101
BiblePay just got listed at https://masternodes.online/ (and it's first on the list right now), how come? Did someone pay for this or the site owner listed it for free?

http://forum.biblepay.org/index.php?topic=57.0

Looks like 616west jumped on it! awesome!

Yes, the owners contacted me and asked if we were ready.  I asked for a price quote, and they shot me a better number, so I jumped on it from my own funds.

When I get my allotted payment for the proposal, we'll have to deal with the sticky issue of what to do with the excess.  My thoughts have been this.  If the cost had gone up, I would have paid the extra from my own funds (if possible) and then asked to be reimbursed in the next cycle.  Since the cost has gone down (due to the increase in value in the last few days), I should have a good amount of extra.  My thought is since I would expect to be reimbursed, this excess belongs to the community and should be sent to the Orphan Fund address. 
full member
Activity: 1260
Merit: 115
BiblePay just got listed at https://masternodes.online/ (and it's first on the list right now), how come? Did someone pay for this or the site owner listed it for free?

http://forum.biblepay.org/index.php?topic=57.0

Looks like 616west jumped on it! awesome!
full member
Activity: 462
Merit: 103
BiblePay just got listed at https://masternodes.online/ (and it's first on the list right now), how come? Did someone pay for this or the site owner listed it for free?
newbie
Activity: 56
Merit: 0
When does the budget turn over into funding the various approved projects? Is it block number 24600?
full member
Activity: 770
Merit: 100
is this to 175 false?

BiblePay - 1.0.7.5
Leisure Upgrade


- Competetive mining feature:
The idea behind competetive mining, is for those with fast processors who mine so fast that they run out of nonces,
this feature automatically adds a tithe for the orphan foundation for a miniscule amount (IE 1 satoshi or .000001 bbp)
IF you run out of mining nonces, and only increments to 2 satoshi again if you run out. However, when the block changes,
the amount is reset to 0 again. Alex and I have tested this and it appears to give a 5% mining edge. Therefore I wanted
to release this as quickly as possible for general consumption. Since it gives a mining edge, I made the feature ON by default.
To turn it off add the key: competetivemining=false to your biblepay.conf file.
jr. member
Activity: 89
Merit: 7
1. In control wallet
gobject vote-many 3f22267e91222c6d761f8a83d781a0adfe833c3b42b790a0990abfb2a5923942 funding no
gobject vote-many 3f22267e91222c6d761f8a83d781a0adfe833c3b42b790a0990abfb2a5923942 delete yes
close wallet and delete mn*.dat, rm gov*.dat
2. In masternode, run
  biblepay-cli gobject list all triggers
 to check if it has just one trigger. If not, restart the masternode
3. Start the control wallet and unlock it, then
   masternode start-alias SANCTUARY_ALIAS
4. Check if it is synced in control wallet:
  mnsync status     ("AssetID": 999  means synced)
5. In control wallet, run:
  gobject list all triggers
  if you see two triggers, then do close wallet and delete mn*.dat, rm gov*.dat and wait a few minutes and start wallet
6. In masternode, run
   venv/bin/python bin/watchman.py
under the watchdog dir to check.

I had to delete the mn*.dat and gov*.dat at the Masternode as well as the Controlling wallet to get this to take.
I also deleted on both, dont see 3f222xxx object only 4a1f347cd49a97d36f105b1908d33a3ed3cfb5d11485000d2908313f4c2d9490 on both
but after few minutes I see 1996fe78ce9efd7a3b6deefbcd2e120b75f850909ad8f702062a517b1cb27ae1 and see same error:
Code:
$ WATCHMAN_DEBUG=1 ./venv/bin/python bin/watchman.py
2018-01-02 19:52:37 [info]: SCHEMA_VERSION (code) = [20170111-1]
2018-01-02 19:52:37 [info]: DB_SCHEMA_VERSION = [20170111-1]
2018-01-02 19:52:37 current_time = 1514922757
2018-01-02 19:52:37 next_run_time = 0
2018-01-02 19:52:37 Delay of [49] seconds for cron minute offset
2018-01-02 19:53:26 govobj updated = 1
2018-01-02 19:53:26 subobj updated = 1
2018-01-02 19:53:26 govobj updated = 1
2018-01-02 19:53:26 subobj updated = 1
2018-01-02 19:53:26 govobj updated = 1
2018-01-02 19:53:26 subobj updated = 1
2018-01-02 19:53:26 govobj updated = 1
2018-01-02 19:53:26 subobj updated = 1
2018-01-02 19:53:26 govobj updated = 1
2018-01-02 19:53:26 subobj updated = 1
2018-01-02 19:53:26 govobj updated = 1
2018-01-02 19:53:26 subobj updated = 1
2018-01-02 19:53:26 govobj updated = 1

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in
    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 117, 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 "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/__init__.py", line 533, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/decoder.py", line 370, in decode
    obj, end = self.raw_decode(s)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/decoder.py", line 400, in raw_decode
    return self.scan_once(s, idx=_w(s, idx).end())
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/scanner.py", line 127, in scan_once
    return _scan_once(string, idx)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/scanner.py", line 95, in _scan_once
    return parse_array((string, idx + 1), _scan_once)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/decoder.py", line 250, in JSONArray
    value, end = scan_once(s, end)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/scanner.py", line 95, in _scan_once
    return parse_array((string, idx + 1), _scan_once)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/decoder.py", line 250, in JSONArray
    value, end = scan_once(s, end)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/scanner.py", line 93, in _scan_once
    _scan_once, object_hook, object_pairs_hook, memo)
  File "xx/.biblepaycore/watchman/venv/lib/python3.4/site-packages/simplejson/decoder.py", line 226, in JSONObject
    s, end - 1)
simplejson.scanner.JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 1673 (char 1672)
Jump to: