I checked your notification history, and unless I misread it, the first occurrence was 9 days ago, which fits in the window for the code update on our server. Still, that's helpful since it seems to confirm

Do you have a link to an error from that time? It would be helpful if so, since I think we deployed the new code on the 19th (i.e. 10 days ago). But it was probably running on another server prior to that

Imagine how I feel, since it's not before my time...

That's the bug I'm referring to here: This week we deployed the new version to production and we’ve observed one possibly new bug (an occasional notification missing a valid timestamp) that needs further

Figuring out "why something is slower" is a tough task. We can make some guesses, but in the end we'll probably just have to do a bunch of experiments to determine the answer.

I'd be curious to hear what your long term improvements are to the current economic model. If you can "layman" it. The most fundamental change is probably not very controversial at this point

I somehow missed your reply previously, but then someone just left me another reply on this post (calling me a "whack job" as it happens, so I guess the emotional temperature of this post is

Hi, similarly, I just read this, so sorry for delayed response :-) Voting CAN affect what is written, but it doesn't have to. That's mostly up to the writer. If the primary goal of their writing is financial

Sorry, I but don't understand exactly what you are objecting to in what I wrote. I couldn't find "notions" in my response, for example. If you have specific issues to complain about, I will attempt

Probably they purchased a Hive power delegation from us in the past, and it is an automated messaging telling them the delegation has expired.

We did some work in the past to add encrypted instant messaging and email to Hive, but it was several years ago, and we would need to clean up that code a bit before it could be used now.

I've been so busy with HAF-related work that this kind of slipped my mind. I'll give it some thought.

It does directly create more Hive, but on the other hand it is a fixed amount of Hive, unlike HBD which could result in even more Hive being created in a market downturn via conversions. I see the intent

Couldn't you just have run Jussi outside the docker image? That's how we run it.

Just one of those nodes can handle 10x the API traffic we currently have. The only reason for more nodes is decentralization and resilience.

That sounds like a frontend issue, so pinging @quochuy.

Changing the haircut rule and print rate should be simple, but creating an AMM is a more complicated and risky thing to do, so I don't think it should be considered for the upcoming hardfork.

So this will print more HBDs that will end up in the market, which will make it more difficult to stabilize when the price is below $1, no? No, the amount of HBD on the market doesn't impact the price

Increasing the haircut ratio can only improve the peg of HBD. The haircut ratio was established to limit the risk to Hive price, not to help stabilize the price of HBD. In fact, I think it is fair to say