cardano-sl VS polkadot

The daily developments were reduced by August but resumed vigorously in September. The whole of September was a busy month for developers as the daily submission rates for most coins were very high. At this time, ETH, DOT, and ADA were the leader as SOL followed closely behind. It was not till towards Mid-October that the daily developments reduced.

So, uh, the two things the blog post covers are actively awful practices. Let's look at Logging. Logging boils down to ServantLogConfig, which carries a function Text -> IO (). This is bad. Text is not a great type for logging, since it's relatively slow and encodings aren't guaranteed to be sensible (cf this bug where logging to a file was broken based on environment encoding). You want something like LogStr from fast-logger, or even a ByteString.Builder or Text.Builder even.

oops I want my Daedalus wallet (actually very surprising it's not there as Cardano uses Nix). Meanwhile this packaging request has been Open since 2017.

Otherwise you can use the following instructions for adding the caches to your local Nix install: https://github.com/input-output-hk/cardano-sl/blob/master/docs/nix.md#binary-cache

For what it's worth, coincheckup is tracking https://github.com/input-output-hk/cardano-sl which is the old repo from before they split up a lot of the infrastructure into their own repos.

Polkadot (6400 GitHub Stars) https://github.com/paritytech/polkadot

I don't think asynchronous backing has any direct effect on the number of parachains, no (I mean, there likely is an effect, but it's not the goal and my understanding is that any effect on that would be minimal, although I'm not involved in the deep engineering here). It increases throughput, correct, by decreasing the time between blocks by not needing to do a "roundtrip" to the relay chain to build new blocks. See https://github.com/paritytech/polkadot/issues/3779 for an overview.

"The 27 waiting day is unavoidable and a very important security measure to protect against certain attacks and vulnerabilities of PoS. I totally understand that it is annoying, but arguably it is for the benefit+security of the overall network, which includes you as well at the end of the day as DOT-holder." - from this GitHub discussion.

Ref: Kianenigma @ https://github.com/paritytech/polkadot/issues/2418

Polkadot 0.9.37 has been released with MEDIUM upgrade priority. https://github.com/paritytech/polkadot/releases/tag/v0.9.37

Specifically, it was this PR that changed it: https://github.com/paritytech/polkadot/pull/6230

Actually it looks like you can! It's just not recommended. This is from the official documentation: "Starting with runtime version v23 natively included in the client version 0.8.23, payouts can go to any custom address. If you'd like to redirect payments to an account that is neither the controller nor the stash account, set one up. Note that setting an exchange address as the recipient of the staking rewards is extremely unsafe.*

A particular validator sent out a LOT of dispute reports (i.e., saying that other validators did something incorrectly) last night (for reasons unknown). It looks like other nodes "choked" reading all of these disputes, and one subsystem died, stalling nodes but NOT killing the process. It's still being investigated, but you can look at the issue on Github to see it being discussed here: https://github.com/paritytech/polkadot/issues/6412