My Telegram account @dann96 has been compromised. Please don't engage with any odd message you could receive. Mi cuenta de Telegram @dann96 ha sido comprometida. No hagáis caso a ningún mensaje que podáis recibir. The new Telegram account is @danielmandragora from now on. La nueva cuenta de Telegram es @danielmandragora desde ahora. Thank you. Gracias. 🙏

My feedback on @Arcium's Staking Dashboard I've been digging into what seems to be lacking to help new users get familiarized and further understand the mechanics beyond a typical DPoS staking dashboard. - Separation by clusters to avoid confusion (total revenue generated every epoch; also details about programs deployed on them). - Displaying the amount of tasks being processed per epoch on clusters (breaking it down per program/s). - Clusters general performance per epoch. A basic formula to get a performance % would look like: 1) (finalized tasks / (finalized + failed + pending tasks)) * 100 2) or excluding pending tasks: (finalized tasks / (finalized + failed tasks)) * 100 - The performance of a specific node can't be calculated accurately, as the public data available of computing tasks transactions is tied to just one node of a cluster, we can't rely on such a metric to measure how a node is actually performing. There's an apparent issue surfacing from the above point: if we are completely blind when it comes to node performance, how can delegators prevent being slashed in anticipation? I've read about node score, and perhaps this could serve at least as an alert, but unfortunately it can't be extracted. By adding or addressing these, or at least some of them, most users in general wouldn't get lost while trying to figure out how staking works on Arcium and how it differs from other models. stake.arcium.com