Mo Najafi

Thanks for the report, we will reflect that on the new release.

@SmartAppsX thank you for the report. @diegodelrieu @kiruthikraaj v1.1.1 is just released, please use that. That has the fix.

Hello there, thanks for your report. As far as I understood, you are using message fabricators not anchor-earn itself. But, using the anchor-earn `withdraw` function will always lead to a...

If you use anchor-earn for only fabricators, I recommend using `anchor.js`. If you want to have your own `customSigner` or `customBroadcaster`, anchor-earn supports that. Besides that, fabricators have nothing to...

yes exactly like that. My point was, `fabricateMarketRedeemStable` withdraws the amount you specified in `aUST` denom; if you need to get it in `UST` denom, you have to calculate it...

Thanks for the report, We will reflect that on the document. May I close this issue?

@ALPAC-4 Would you mind having a look at this?

@dosullivansoftware thank you for the report, we will put it in our queue to fix the issue. At the same time, I would be more than happy to see a...

Thank you for your reply, I will try to use your suggestions :)

The same phenomena happened again at 2020.04.01 at 11:45 A.M. Here is the log: ```#14484478 2020-04-01 05:30:54.911188417 UTC P2P Worker #2 WARN netapi block-propagation cannot message Global 34.87.122.166:3485: "SendError(..)" #14484478...