Quote from: bible_pay on January 03, 2018, 04:20:09 PM

Quote from: tiras on January 03, 2018, 04:15:35 PM

./biblepay-cli gobject list all triggers

returns only 1 object for me : "4a1f347cd49a97d36f105b1908d33a3ed3cfb5d11485000d2908313f4c2d9490":

so I'm assuming my node if fine ATM , isn't it ?

Yes sir, your node is acting correctly. Your good on your end.

EDIT: btw, the single and correct gobject for our budget is : 4a1f347cd49a97d36f105b1908d33a3ed3cfb5d11485000d2908313f4c2d9490

We are working on merging the appropriate commits for security and preventing this type of gobject failure in the future also. Im interviewing blockchain devs in my inbox, so hopefully we will have a dedicated security programmer soon.

Regarding the pool, I got a message from Hong Kong mining saying they are going to push a lot of hash power soon against the pool, I told them hit us with whatever they have. Tiras, if it turns out the pool becomes overloaded and MinersofMen gives up we may need your help again. I will monitor the situation closely.

We also received a request for a BiblePay interview in a magazine, I sent the magazine to Togo, good luck Togo.

this is great news Rob, thanks for the update and I'm ready to plug in if needed