Image created using idoegram
This post is not financial advice
I wanted ot do a quick transparency post. As I described in detail in This post. I pre funded this account with more than enough funds to get through the pre sale and to set this account up string regardless of how the presale went.
The total "debt" in PIXYDUST tokens I owe myself is 6188
That number is actually 6088 now as I sent 100 PIXYDUST to my main account @cryptounicorn420. I will send another 100 tokens to my other accounts probably 20 each or something like that. I have not done that yet as of this post so I have not deducted that number.
This will leave me with about 70 PIXYDUST if I do not mint any new tokens. I am in no rush to pay myself back. I could if I wanted to mint a few thousand tokens and it would not negatively affect the ratio because all tokens are backed before mint. I will not be minting new tokens for probably at least two more weeks.
The tip bot is funded with 125 PIXYDUST and a little over 102 HSBIDAO.That account is also in the LP and is ganing HSBIDAO divs daily. Once the bot launches (in know it's delayed far too long. I'm not happy about it either) I will watch it slowly and I will build it up so that the daily divs pay for the bot calls on average. I am not sure how long it will take to get there but I already have a good head start.
I know I keep apologizing but I am really sorry and if I am being honest frustrated the bot is taking so long. It should not have taken this long and all I can do is apologize and let you know we are working on it. I swear. There is apparently a minor database issue (in both bots) this issue won't affect the UNICOIN bot but my husband doesn't want to install the new bot before fixing it.
At this point I am kind of pressuring him to launch it anyway and we will fix it later as it's already almost a month behind at this point and I absolutely can't stand being "late' for things. It drives me mad. Yes I am one of those people who is usuallly ten minutes early just so I am not late.
The issue is not a big deal but long term would need to be fixed)from my understanding it's something in the code that should have been written for the database but wasn't so there is a work around but not the ideal solution). There is a away to work around it as obviously the UNICOIN bot has the same issue and it works well. Husband is a perfectionist . I am not. I am a "if it works well enough then launch and we will fix the issues over time" kind of person. But I get it. He is going to be releasing the code in public and he doesn't want to release code that is not up to his standards.
Also the surgery mayhem had us both distracted especially with it being rescheduled and all that. It's been a rough 6 months here. We are working on it and I basically gave him an absolute deadline that if the problem can't be fixed by the beginning of the weekend to just launch the "band aid "version and we will fix it later. Not launching the bot is holding things up and y'all deserve better.