I have a ton of UPSs and never had any "fire-related" issues. But on the other hand I've also had a lot of UPS that fail, so sometimes it is the UPS itself that causes a problem, even when there

The updated plan sounds much better, you've got my vote.

HAF was designed to automatically handle micro-forks. It actually has two modes:1) in the default mode, it tracks all changes up in your app's tables up to the last irreversible block, so it can revert

Out of curiosity, which app are you referring to?

I'm a bit curious why you think the Terminator scenario is off the table? At first glance, I can see several reasons to think we are at great risk. The most disturbing point to me is that unlike most of

He's asked us to support a new signature type (BLS) which allows for a more compact multisig. It's not strictly needed for VSC, IMO, although it would be helpful for VSC when creating multisigs for managing

I've got no plans to tinker with the reward options, but it isn't that hard to exchange Hive for HBD on the internal market.

Actually, it's more feasible than you might think. I have a friend in Blacksburg who's lived his whole life without a car (he's about 10 years older than me). He's held a regular job in the entire time

"Behind the scenes", I approached mcfarhat last week and asked if he would be interested in taking over management of the UI for the block explorer (and later the backend too, once their group

Giving Sun even credit for this is in fact too much credit: as far as I can tell, it was done by some independent dev, who can see the upcoming wall that Steem is driving towards and is trying to slow

Well, it is of course a night and day comparison if we look at code from 4 years ago. For some reason (I can't remember why), I took a look at state of Steemit code a couple of days ago to see how long

There is some code like that, but it is a bit different than the change we just made. That code charges extra for particular resources when it detects they are being used a lot. And in that case the actual

These are some early posts on the rating system I was talking about: and

I can't guarantee it yet, but I'll likely be there for the game. As to making the final table, that's an even harder question to answer :-)

Yes, your assumption is correct, blocks are strictly processed in order during sync, the P2P code ensures this. If it's easy to test, let me know what you find out: I guess work with @gandalf so that the

It might be the state undo logic slowing down blockchain processing in a sequential manner (this computation is probably skipped for replay+validate). But I doubt there is a way to disable it to check

Signatures are checked ahead of time in separate threads, and sufficient number of threads are default allocated. Whenever you see block processing at 100%, then the bottleneck is the single-core speed

I wasn't responsible for designing Hive's "influence based on staking power", so I don't particularly feel compelled to defend it. It has some obvious weaknesses, but in the end I'm quite certain