What this would mean for stakers (paging @coreapp users): ** no timelines for this are mentioned in the thread. Go participate in the discussion on Github. Informational rant incoming from your friendly local Product Support Manager 🤓 please read the quoted thread for more information. ** The staking process in Core would not change. When DYOR'ing (like the responsible users I know you are) - you will want to make sure the uptime for nodes you want to delegate to are in the 90-100% range, not 80-100%. How can you do this? Use the explorers to check on node performance, historical behavior, and make informed decisions. Some places you can do that outside of the Core web staking dashboard (non exhaustive, we have lots of great explorers in the eco!): - @avax explorer (subnets.avax.network) - @AvascanExplorer (avascan.info/) - @snowpeerio (snowpeer.io/) What happens if the node I delegated to doesn't reach the 90% uptime minimum proposed? Unfortunately, this means delegators and validators will not get their staking rewards. This is not a Core wallet decision, it is a network level requirement needing to be met (more information in the thread below). But when I delegated to this node, it met the uptime requirement. Why did it fall below the threshold after and cause me to not get a reward? Unfortunately, we can't answer this. This can happen at any time. If the node goes offline and falls below the threshold, the rewards won't be received by the stakers. With the decentralized nature of the Avalanche network, anyone can be a validator if they meet the minimum requirements, and we can't track them all down and tell them to fix their nodes. There are notification options available for validators (more information on that in the thread below) to help track their uptime. This is always why myself / my team recommend doing thorough research before staking. NFA as always, we want staking transactions to complete as successfully as you want them to. 🤝🏼