polkadot-wiki VS polkadot

No worries! Going forward, the Polkadot Wiki is where you should always be able to find the source of truth for anything Polkadot-related. And if not, please file an issue on the Github repo and someone from the Tech Ed team will likely add it (or correct it) shortly. =)

As you can see from the links above, most questions are answerable via the Polkadot Wiki. But if one is not, please let us know! https://github.com/w3f/polkadot-wiki/issues

I've made an issue to add it to that Wiki page ( https://github.com/w3f/polkadot-wiki/issues/3453 ) - thanks for bringing this lapse to our attention.

Thank you for noticing this, I've filed an issue to update the wiki to make it clearer: https://github.com/w3f/polkadot-wiki/issues/3350

It's more like the Polkadot Wiki is over 300 pages (printed out) already, and we're not always sure what is confusing or what information people may not know. It's always a good idea if you have an issue with it to file an issue on the Github, as I just did to add some more information on this here: https://github.com/w3f/polkadot-wiki/issues/3235

I'm not familiar with subwallet. That page lists all Parity-developed or Treasury-funded wallets. If subwallet did receive Treasury funding, please submit a PR to add it (along with a link to the Treasury funding) - https://github.com/w3f/polkadot-wiki

Thanks for noticing this, the wiki is not clear. I have filed an issue. https://github.com/w3f/polkadot-wiki/issues/2764 If you let me know your Kusama address, I will send you some Billcoins as a thank you.

There have been several questions as to exactly how the ending block is chosen. This Github issue to add information to the wiki includes a detailed explanation from Robert Habermeier: https://github.com/w3f/polkadot-wiki/issues/2674

If you happen to go over the Wiki, any feedback as a "new user" would be great too (e.g. if you feel things are unclear or missing): https://github.com/w3f/polkadot-wiki/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