core-rs-albatross VS polkadot

The official avenue for information on Nimiq is always through nimiq.com - however if you're curious on learning more or just getting your hands on some NIM to try out the wallet, stop by the stream and say that you've come from Reddit. I'll keep an eye on chat and send you some to play around with.

yeah thats weird, appears link is broken. Did you try to go to nimiq.com, click on create account on top right, and then select ledger and try from there?

Some time ago one of the team members shared that they will be more transparant again in terms of the development of Nimiq 2.0. This means, among other things, that new issues/bugs raised by Team Nimiq will be public on Github again so everybody can track the progress and jump in if they want. It seems like they started doing this once most team members got together in Germany for a new hackathon. Most issues are created for the core-rs-albatross repo which gives the impression that most (or maybe all devs) are focusing on Nimiq 2.0. https://github.com/nimiq/core-rs-albatross/issues.

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