It's basically a task to fill out a roadmap for the work to be done by our team this year (which will be a public roadmap, of course). The time vault idea is definitely interesting. I'll give it some thought

No, rocksdb is currently only used by account_history_rocksdb (which is deprecated in favor of sql_serializer). But despite the deprecation, account_history_rocksdb will probably be used for a long time

Sorry to hear about your loss. Losing a pet is always tough, and the fact that other people are grieving for lost family members doesn't mean your grief isn't real and reasonable.

Yes, fixed now.

Any transaction to a previously assigned address will be in a "blocked" state until we receive KYC info.

Last I saw, I think there were over 100 developers working on hive-related projects, so we're under 20% of the total I guess. I don't think it is that difficult to run a hive node. Mainly it just requires

I don't use Coinbase, but I always heard it wasn't listed there. But I'm not sure how you're distinguishing lists from trading. Are you saying they will "custody" hive, but not allow buying/selling

I'll probably post one in a few weeks.

It is possible, AFAIK. BitShares (the first graphene-based blockchain) had a prototype ability for anonymous transactions, but it wasn't used much. Since that time, I think more sophisticated methods have

It's always been one of those things of the type: if hive will get listed, then we will add it.

Yes, we've just started working on our roadmap for this year, but I'll release more details once it's solidified some.

It's too early to say much about these apps yet, since the ideas so far are mostly just my own, and I haven't discussed with other developers much yet. As far as the smart contract engine goes, it's basically

Most of the work on condenser is done by @quochuy right now but our team does make changes occasionally. I've actually tasked one of our devs that we moved to the hive project to review the current state

What's broken on hive.blog? Please ping @quochuy here with details.

We haven't started thinking about HF28 features yet: there's a lot of things we can do without a hardfork being required and we're working on those features now.

It's run by @guiltyparties so contact him.

That's not actually correct. The bug is just causing non-top 20 witnesses to frequently be scheduled more than once after they get scheduled. So the same overall rewards are being handed out to non-top

I'm not sure what you mean: I've always said it made more sense to implement smart contracts on layer 2 instead of layer 1.

Seems so, looks like witnesses are onboard, supermajority is running v1.26.0:

I'm actually back from the Polish trip now, and I'm just catching up on all the work that built up while I was gone (one of those items was writing this report)...