I added some thoughts about where we should potentially set the print rate in my comment to taskmaster below.

I think that increasing supply will likely lead to more trading activity and liquidity, especially on external markets. And that in turn should lead to a better peg to USD. Even more importantly, whenever

The APR rate for HBD is set by consensus voting of the top 20 witnesses, no code change is required. Currently most are voting for 10% rate.

No, I'm referring to the haircut ratio, it's not related to the APR%. Currently, whenever the supply of HBD (excluding HBD stored in @hive.fund) exceeds 10% of the virtual supply of Hive, the haircut rule

Yes, it should be possible to add a feature like that to hivemind, but I don't have anyone free to work on something like that right now. But @howo is looking at doing some work on hivemind, so maybe he

Our focus is on other projects right now, so I don't expect to add any new coins to our exchange in the near future.

This doesn't de-penalize that. When you vote and unvote, you don't get your vote power back. This was a different issue: once you vote on a post, unvote, then revote, your revote didn't give you any curation

There's this certain comment I made more than seven days ago that I'm trying to delete but was unable to no matter how many times try despite getting no response and no upvote/downvote dust or whatever.

It's not fixed yet, but probably the earliest would be in December.

Yes, the modular aspect will make server setup more flexible and it will also make it easier for devs working on different apps to cooperate more efficiently.

Yes, it is definitely a worthwhile change, I'm sure most people weren't aware of the associated loss. Note that this issue will persist until hardfork 26.

By programmer headcount, our Hive-focused team is actually larger than Steemit's was :-) We just don't have the marketing/comms guys, we leave that to other groups. But it is true that we're working on

I think people should always read the comments :-)

Hafah uses around 2TB of disk space, so it definitely uses more space than a hived account history node. But note that most of that is for the HAF tables that can also used for other HAF applications (such

Cost of hive accounts is already set by witness consensus.

Typically, we try to schedule them 6 months apart. Once we've got a better idea what features we will be including, we'll figure out a timeline that makes sense for the release. In any event, I expect

Yes, this week we added docs for TestTool (those docs are mostly for Hive core devs). I think there's probably already enough docs to use HAF, but we'll be adding more after we finish up testing the HAF

Yes, a lot of the details of these posts are aimed at other Hive programmers, so most readers are going to find it hard going. But to summarize it a bit, we're mostly testing/fixing/benchmarking the first

I hope with time that more of our core dev team will join in here and shares some details about what they do. The other issue could just be that they think people will find their work boring or hard to