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!