ledger-kusama VS polkadot

You can't do transactions and there is no signature option Txn not supported https://github.com/Zondax/ledger-kusama - There's been an update for about a week now. Kusama (KSM)Version 22.9420.0 - Needs updating

Does anyone know if we can update it manually outside of the ledger live app to one of the releases on https://github.com/Zondax/ledger-kusama/releases/tag/v8.9130.0?

You might want to check this thread on Zondax - Ledger Kusama: https://github.com/Zondax/ledger-kusama/issues/122

This seems to be a fairly common issue. If anyone is getting this error with their ledger nano, Txn version not supported, please provide information on the issue opened in Github: https://github.com/Zondax/ledger-kusama/issues/122

Assuming you are referring to the Kusama app that runs on the Ledger, it is developed by Zondax, not "the Kusama community". https://github.com/zondax/ledger-kusama

This is a known issue, unfortunately looks like ledger is ‘still working on it’. https://github.com/Zondax/ledger-kusama/issues/104

Ledger-kusama app is still working on a fix to the recent problems with the runtime upgrade on Kusama, you can follow the latest convo on the open issue on GitHub here https://github.com/Zondax/ledger-kusama/issues/104

Currently there is an issue on the Kusama-ledger app that was caused by a recent network update. The team at Zondax is working with the Ledger team to solve the issue. You can follow any updates here https://github.com/Zondax/ledger-kusama/issues/104

Hi mate, I ran into the same issue just now and have submitted an issue to them here: https://github.com/Zondax/ledger-kusama/issues/104

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