"secret" performance feature is still planned, but not sure if it will be done before the holidays, but it will be part of HF. Just found another reason for it recently that makes it even more

Sounds in the right ballpark, but it could be somewhat more since blocks are getting filled with more operations and transactions lately. Should be pretty easy to measure by periodically logging the database

Yes, of course :-) For the most part I was trying to stick to units of GB to make values easier to compare, but I guess that led to a mistake ultimately.

Scaling is relegated to work hours. Dream time reserved for discovering new paradigms.

I think the most likely thing will be that we allow an insta-powerdown for a fee, as suggested by @theycallmedan in a post he wrote a while back (see his post for more details on the idea). But I'm not

There's a reason it wasn't pegged well in the past: it was only pegged in one direction. That is no longer true, and from my perspective, the peg works really well now. The farthest it has moved from the

Yeah, I think my last couple of posts have been increasingly technical in nature, and have primarily been aimed at developers who may want to try some HAF in their applications. Part of the issue is the

When I saw the new feature, I had the same thought that it would be nice to also show VP there, maybe with an additional circle, for example.

I see your point, but it seems like anyone can just stake a small amount of Hive, so why would they want to pay transaction fees? And even if they have 0 HP they can still do some small amount of operations.

Yes, it was while looking into your report about high traffic that I saw this strange behavior in the RC code. I've never looked into this code before, but my initial feeling is that the code isn't behaving

AFAIK no one else has tested operation on WSL2. I wouldn't expect any problem though, unless it is related to IO virtualization, resulting in a slow down of some sort. You may want to check what nodes

I am convinced that there may be a performance bottleneck somewhere in the P2P system of the Hive blockchain software. The peer to peer network is behaving fine, no bottlenecks there, it could handle much

Shortly after we started Hive development, we reviewed the state of the SMT code, and at that point we decided it was better to create more efficient and flexible 2nd layer tokens that support smart contracts

I think the biggest deal will be release of HAF. Strictly speaking, it's not part of the hardfork, however, and will be released before the hardfork.

No, not HMTs, as that potential feature has been discussed many times, so nothing too secret about the idea. This is an improvement that hasn't been suggested before. But before I propose it for inclusion

I'm not sure yet on the next HF date. Hopefully we can stick to the original timeframe of around December/January, but I have one "secret-for-now/yet-to-be-announced" feature that I really want

Yes, there's several diagrams in the new HAF documentation to show data flow and algorithms. I would guestimate we have at least six devs who have a lot of experience with hived (and other sibling chains

I agree, I think there's no point in trying to increase demand until the system allows for significant expansion of supply without breaking peg. I also think that such an interest rate increase should

Thx for the confirmation.

Ah, but that's on emre's node, not ours. On ours, it doesn't happen till later. I can only guess that maybe he updated to the experimental code earlier than we did (or possibly it is a different issue