# Consensus rewards whitepaper concern **URL:** \ **Category:** General\ **Created:** [January 30, 2024, 9:10pm UTC](https://forum.algorand.co/t/consensus-rewards-whitepaper-concern/11259 "2024-01-30T21:10:05Z")\ **Posts on this page:** 1\ **Showing post:** 53
**Author:** ![JohnWoods](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/johnwoods/32/2361_2.png) [@JohnWoods](https://forum.algorand.co/u/JohnWoods)\ **Post date:** [February 5, 2024, 12:03pm UTC](https://forum.algorand.co/t/consensus-rewards-whitepaper-concern/11259/53 "2024-02-05T12:03:23Z")
> [@oysterpack](#): > > - 1-click nodes should be rolled out before incentivized consensus participation. The 1-click node should have built-in automated workflows for: > - consensus participation > - node updates > - telemetry - monitoring and alerting > - fault recovery > - 1-click node software package distributions should be created for all major platforms: Windows, Mac, Linux, and Kubernetes for cloud deployment > - There should be a global consensus participation dashboard to monitor the network’s health. > - 1-click node deployment versions should be identifiable on the dashboard > - Documentation and training materials should be created. A node runner manual is required. > - Define measurable exit criteria to enter the next phase. > - The program should run on testnet before mainnet A lot of this sounds great, the problem is the practicality. The core team on this is single digit numbers. There is only so much money for engineering. We can do this perfectly but then it won’t release this year. One has to balance pragmatically. We’re shooting for, nodes that are easy enough to use, a defi based solution and a P2P pooling option. --- _[View the full topic](https://forum.algorand.co/t/consensus-rewards-whitepaper-concern/11259)._