Generally correct, but the speedup notifications updates won't be visible to users: the speedup is in the time it takes to build the table data (it used to take around 1/2 second per block, loading the

I don't really agree that there's not a real memory usage reduction. The memory is in fact allocated by the software, and hence isn't available to other programs, regardless of whether it is actively storing

I'll ask about Hive Bridge, I'm not involved in that project directly, so don't know details. The healthchecker UI is embedded into the latest haf block explorer. You can see it by going to and clicking

We benchmarked the new stack on a AMD 9950X3D with two 4TB T700 nvme drives and 64GB of RAM. HAF itself, using a RAM disk temporarily for the state_file replays in 13.34h. Next, replaying the apps in parallel

There's not any way to know that right now, because viewing a post is purely a local action taken on each user's computer, and it isn't recorded in the blockchain. Theoretically, each app could measure

We are still working on it, but for a long time it was all in the theoretical design realm. More recently we started writing some actual code for it, but its not yet to a working prototype.

I think it was in my freshman year in college, my roommate got misplaced childhood, then we ended up picking up a bunch of their albums and EPs over the next couple of years. I even had a couple of their

Marillion is one of my absolute favorite bands, and Fish is my favorite lyricist (or obscure Scottish poet, as he would have it). Misplaced Childhood was definitely their best album, and it's the

"200 bites" is a lot of bites. Can you really eat that much cake?

No, we closed it down over a year ago, see here for more details:

The risk is if it goes over 30%: at that point the haircut mechanism cuts in to protect Hive's price from a death spiral, so HBD gets devalued whenever the debt ratio is over 30%. But in practice, you

Most L2 smart contract systems are centralized. But there's no particular reason they have to be, it's just "easier" to do so, just like its easier to write most any software in a centralized

We're working on L2 smart contracts, not L1 contracts, because I think L1 smart contracts offer a lot of risk and relatively little reward compared to L2 smart contracts. L2 contracts also offer more potential

Thanks for the report! Please create an issue for it on gitlab if you haven't already. I suppose at some point we should review all the new API calls for potential attack vectors like this one, that might

Normally we recommend it be run on a bare metal system, if possible, since everything is encapsulated in a docker. But IIRC you're using promox, and it should not be a problem to run everything in a VM

How would we even be able to release the software, without your rigorous testing?

No need to tag me, I have no plans to vote for the proposal. I didn't vote for the last one even, but I find it hard to believe this one will get enough support. But thanks for the work investigating this,

The best way to get replies is to ask questions that people want to answer. Then they will feel compelled to reply.

If everyone knew, they wouldn't be arcane: "understood by few; mysterious or secret."

Witness voting can be seen on several block explorers. Here's one here with marky's votes: Note that you will need to expand "witness voting" on the left-hand side.