Bible Pay

Read 105392 times

  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #375 on: November 26, 2017, 06:43:50 PM »
Hey Rob, I was wondering if you saw that message.

I would need to check the logs again but I have been receiving masternode rewards for 1 day if not 2 while biblepayd crashed/wasn't running.

Oh OK cool, I havent had any nagging crashes, but I can investigate if you can provide the last page of the debug log before the crash.

On the payments, if you could please check to see if the masternode status is 'Enabled' on a node other than your masternode - and that your masternode is actually in sync.  If the masternode is in sync, it should be able to vote for itself for payments if its status is 'enabled' on everyone elses client.  Of course it has to have watchman running though.  If you want to give your IP I can tell you right now what the status is on this end?

Great on testnet BX, thats cool.

Yeah, I forgot to answer you on the Ecommerce post a while back when Thanksgiving hit.  Right now, the Mouse API only supports US deliveries.  But whats nice is we have the capaibility to deliver through Walmart and AMazon to the EU!  But first Id like to see how many orders we receive in the US to ensure its worth expanding to the EU (because its more work and more to support).  If we sell quite a few items per month Ill expand the API to include more countries each month.




Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #376 on: November 26, 2017, 06:52:43 PM »
Oh OK cool, I havent had any nagging crashes, but I can investigate if you can provide the last page of the debug log before the crash.

On the payments, if you could please check to see if the masternode status is 'Enabled' on a node other than your masternode - and that your masternode is actually in sync.  If the masternode is in sync, it should be able to vote for itself for payments if its status is 'enabled' on everyone elses client.  Of course it has to have watchman running though.  If you want to give your IP I can tell you right now what the status is on this end?

Great on testnet BX, thats cool.

Yeah, I forgot to answer you on the Ecommerce post a while back when Thanksgiving hit.  Right now, the Mouse API only supports US deliveries.  But whats nice is we have the capaibility to deliver through Walmart and AMazon to the EU!  But first Id like to see how many orders we receive in the US to ensure its worth expanding to the EU (because its more work and more to support).  If we sell quite a few items per month Ill expand the API to include more countries each month.

There wasn't really anything in the log except this:
2017-11-23 10:58:07 ProcessNewBlock : ACCEPTED
2017-11-23 10:59:35 ERROR: AcceptBlockHeader: block is marked invalid
2017-11-23 10:59:35 ERROR: invalid header received d202afcba304c82b59ead0c82bbb545c65d5206f4318fc072ae6aa1f9fa83234

Is there a way to get more things in the debug.log (logging levels)? If so, I will just run it with the most logging possible.

My masternode is enabled right now as I restarted biblepayd when it crashed and restarted it (208.68.37.149 ). What I am going to do now is kill biblepayd manually now and see if it still stays enabled and/or if I still keep receiving reward.

For the ecommerce post, I thought so too. Amazon is set to launch in Australia soon so maybe deliveries here will be possible too!


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #377 on: November 26, 2017, 07:13:18 PM »
Tested ecommerce again!

Facepalm... I had one config key misspelled... hahaha

I have a new error now:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
BAD USERID

I believe these are the relevant lines in the code, I couldnt find USERID though:

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L2036

https://github.com/biblepay/biblepay/blob/9f4868bd447b2346bd1ddd5f04207cec27127a9c/src/rpcblockchain.cpp#L1292


Hi Togo,

Ok, I tracked down the "BAD USERID" error and I see whats happening- in the abstraction layer where AWS stores the order, there was an issue with having blank Email address, so I fixed that issue and it is deployed again, and, I also tested this on biblepay-cli vs QT and it actually works in both CLI and biblpayd and biblepay-qt, so its OK if you want to test it again on the -cli version.

EDIT: I also added more verbose error messages so if any field in the config is not stored you will get an error for that field - in the next version.



« Last Edit: November 26, 2017, 07:17:55 PM by admin »


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #378 on: November 26, 2017, 07:21:02 PM »
There wasn't really anything in the log except this:
2017-11-23 10:58:07 ProcessNewBlock : ACCEPTED
2017-11-23 10:59:35 ERROR: AcceptBlockHeader: block is marked invalid
2017-11-23 10:59:35 ERROR: invalid header received d202afcba304c82b59ead0c82bbb545c65d5206f4318fc072ae6aa1f9fa83234

Is there a way to get more things in the debug.log (logging levels)? If so, I will just run it with the most logging possible.

My masternode is enabled right now as I restarted biblepayd when it crashed and restarted it (208.68.37.149 ). What I am going to do now is kill biblepayd manually now and see if it still stays enabled and/or if I still keep receiving reward.

For the ecommerce post, I thought so too. Amazon is set to launch in Australia soon so maybe deliveries here will be possible too!

Yeah, you can set 'debugmaster=true' if you want, but its going to create Huge debug files.  Those messages are primarily for masternode debugging but I suppose there could be one that is revealing.  Im thinking I am possibly part of the problem here because I didnt upgrade 2 of my 3 nodes to the 1062 version (thats the one where we fixed the biblehash issue) so I might have sent you a bad header.  But still, thats supposed to d-dos ME and not make you crash.   (Edit:  I just upgraded my other 2 nodes).  Building windows now for the controllers.


If you want to run it with that switch, and "possibly" run valgrind again in testnet mode, if you get a crash, I believe valgrind might show the source stack trace of where it died and if you get that I can see what caused it to segfault right there?

Yeah, that would be cool if we could actually create some e-commerce volume through biblepay purchases.  Im interested in seeing 4-5 btc of trading volume due to this, then we could go and get on more exchanges and get a biblepay debit card started if that all came about.



  • togoshigekata
  • Sr. Member

    • 493


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #379 on: November 26, 2017, 07:36:57 PM »
Awesome! Ok I tried again:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
Address Valiation Failed (US Addresses Only)

Hmm I put my address into UPS address validation and it looks good,
only difference is they add the the dash and 4 extra zip code digits at the end
EDIT: Tried dash and extra 4 zip digits, same error hmmm
« Last Edit: November 26, 2017, 07:48:15 PM by togoshigekata »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #380 on: November 26, 2017, 07:55:52 PM »
Yeah, you can set 'debugmaster=true' if you want, but its going to create Huge debug files.  Those messages are primarily for masternode debugging but I suppose there could be one that is revealing.  Im thinking I am possibly part of the problem here because I didnt upgrade 2 of my 3 nodes to the 1062 version (thats the one where we fixed the biblehash issue) so I might have sent you a bad header.  But still, thats supposed to d-dos ME and not make you crash.   (Edit:  I just upgraded my other 2 nodes).  Building windows now for the controllers.


If you want to run it with that switch, and "possibly" run valgrind again in testnet mode, if you get a crash, I believe valgrind might show the source stack trace of where it died and if you get that I can see what caused it to segfault right there?

Yeah, that would be cool if we could actually create some e-commerce volume through biblepay purchases.  Im interested in seeing 4-5 btc of trading volume due to this, then we could go and get on more exchanges and get a biblepay debit card started if that all came about.

Alright I will do that and and come back to you if I see anything.


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #381 on: November 26, 2017, 08:46:18 PM »
Awesome! Ok I tried again:

Code: [Select]
./biblepay-cli exec buyproduct 0718083296
error code: -1
error message:
Address Valiation Failed (US Addresses Only)

Hmm I put my address into UPS address validation and it looks good,
only difference is they add the the dash and 4 extra zip code digits at the end
EDIT: Tried dash and extra 4 zip digits, same error hmmm

Ok cool, yeah there is a lot to this, I had to make the Mouse API send messages through SmartyStreets to get it prevalidate the address because the AWS Api will not do that piece of it.  I sent you a pm with a possible solution.

Thanks,
Rob


  • togoshigekata
  • Sr. Member

    • 493


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #382 on: November 26, 2017, 09:01:13 PM »
Code: [Select]
./biblepay-cli getwalletinfo
{
  "balance": 629975.95447854,
}

./biblepay-cli exec listproducts
{
    "Price": 12230,
}

./biblepay-cli exec buyproduct 0718083296
{
  "Command": "buyproduct",
  "OrderID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "TXID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "Status": "SUCCESS"
}

[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "balance": 617745.95441494,
}

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "",
    "Status3": "",
    "Details": ""
  }
}

Success!

Looks like for key delivery_address2 it did not like the # I had in the value
For example I had delivery_address=Apt #12345
Removing the Hashtag worked!
Thanks Rob! :)
(Im off to bed for now!)

« Last Edit: November 26, 2017, 09:12:38 PM by togoshigekata »


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #383 on: November 26, 2017, 09:15:49 PM »
Code: [Select]
./biblepay-cli getwalletinfo
{
  "balance": 629975.95447854,
}

./biblepay-cli exec listproducts
{
    "Price": 12230,
}

./biblepay-cli exec buyproduct 0718083296
{
  "Command": "buyproduct",
  "OrderID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "TXID": "ef91049ee3f2560c4abc15261fdc09640af20d98e20dcc2187b5f3e6eadb0b4e",
  "Status": "SUCCESS"
}

[email protected]:~/biblepay/src$ ./biblepay-cli getwalletinfo
{
  "balance": 617745.95441494,
}

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "",
    "Status3": "",
    "Details": ""
  }
}

Success!

Looks like for key delivery_address2 it did not like the # I had in the value
For example I had delivery_address=Apt #12345
Removing the Hashtag worked!
Thanks Rob! :)
(Im off to bed for now!)

Oh wow, thats great!  Sweet.

It looks like it went through.  Ill check on the tracking status in the morning and see if the message is going through.  Technically you are supposed to be able to do the list orderstatus and see the tracking.  Lets check that in the morning.

« Last Edit: November 26, 2017, 09:32:24 PM by admin »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #384 on: November 27, 2017, 04:05:18 AM »
Alright so I killed biblepayd for about 3 hours now, I checked it is actually not running on the node and it is not. However, I am still receiving  rewards for it. I checked from another node and it is also still showing as enabled. Is that normal?


  • klondike
  • Full Member

    • 157


    • -10
    • October 10, 2017, 09:00:24 AM
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #385 on: November 27, 2017, 06:26:49 AM »
i have answer how it working :
any  MN script/algo checking how many MN exists in chain, you can check it in masternode winners+masternode winner and rewarding is fall time

205 block mined in 1day=exists 100 masternodes= 205/100=every MN get 2,05 rewards from block and exists any proporcional dividing.On DASH masternode is rewarding proporcional few blocks forward
in debug win you can check it


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #386 on: November 27, 2017, 06:39:12 AM »
@Klondike

I'm more talking about the fact that I have a non-functioning masternode (since biblepayd isn't running anymore on it) still (active?) and receiving rewards.


  • klondike
  • Full Member

    • 157


    • -10
    • October 10, 2017, 09:00:24 AM
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #387 on: November 27, 2017, 06:39:59 AM »
In prod, the HPS is faster, but allows the multi-instance exploit.  In Testnet, f8000 is enabled, and offers no gain when running dual instances.
Please do a getmininginfo in Testnet to see your HPS, and compare to Alex's 13,500 HPS.  Im getting 4K HPS on my windows dev machine.

(In f8000)

EDIT: Pool mining should be disabled in testnet for this test; just to ensure the thing isnt trying to reconnect to the pool every 60 secs.
yes, true, im tested in tesnet ryzen and get HSP=13000 cpuproclimit=20  ;)

Alex how do you know,that your MN is offline? im asked Rob same things like you,w/response from him,but laterz my MN didnt receiving rewards, you getting how long rewards? by me your controller or VPS machine mining :P

yesterday im offed my MN and receiving rewards stoped


« Last Edit: November 27, 2017, 06:47:52 AM by klondike »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #388 on: November 27, 2017, 06:43:50 AM »
yes, true, im tested in tesnet ryzen and get HSP=13000 cpuproclimit=20  ;)

Alex how do you know,that your MN is offline? im asked Rob same things like you,w/response from him,but laterz my MN didnt receiving rewards, you getting how long rewards? by me your controller or VPS machine mining :P

I killed biblepayd myself on that masternode for testing purposes and I'm still receive rewards for it.

Edit: Killed it at 1am CT time and at the time I'm writing this (6.46am CT), I am still receiving rewards for it.
« Last Edit: November 27, 2017, 06:46:24 AM by Alex »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #389 on: November 27, 2017, 06:55:33 AM »
and checked your falltime in debug win masternode winners?  may your wallet is still between proporcional winners
or
you mining with controller :D

Nah it's masternode reward for that specific node. Hopefully Rob can shed some light on that.