-
-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master Payment Processor Payment processor died [$5] #100
Comments
@ivugeocoin i am also waiting to setup pool. can you please able to provide windows compile.? |
More than likely its the coin thats the problem. It isn't returning the correct value like it should for the value that the payment processor needs to detect the number of satoshi inside a coin |
OMG, this is so usefull answer ... so you want to tell me that uNOMP is not working with litecoin ?! ... beacause IEC is direct clone of latest LTC source ... AND are you able to atleast give me expected return ... i've tried to debug paymentprocessor.js, but i dont know which it is expecting |
And i will tell you .. it's 99% not coin issue beacause before 4 months when i firstly set upped NOMP pool it worked perfectly (same with uNOMP) |
I have the same, a few monthes ago it worked and now the eror (Error detecting number of satoshis in a coin) |
Hi, i have an error when i will try to start unomp with ivugeocoin:
--- Did you help close this issue? Go claim the **[$5 bounty](https://www.bountysource.com/issues/33045006-master-payment-processor-payment-processor-died?utm_campaign=plugin&utm_content=tracker%2F12403606&utm_medium=issues&utm_source=github)** on [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F12403606&utm_medium=issues&utm_source=github).Payments ivugeoevolutioncoin Error detecting number of satoshis in a coin, cannot do payment processing. Tried parsing: {"result":0.00000000,"error":null,"id":1460914451290}
Its throwing this, but i think that result is ok, where else can be error ?
The text was updated successfully, but these errors were encountered: