Render Network Proposals (RNPs)

Please read through RNP-000 before constructing your first RNP. RNPs should be well thought out and discussed across the appropriate Render Network Community channels.

Index of Current RNPs

#	Title	Category	Status
000	Proposal Genesis	Process	Implemented
001	Burn-and-Mint Equilibrium	Core-Technical	Implemented
002	Layer 1 Network Expansion	Core-Technical	Implemented
003	Resource Acquisition and Allocation for Core Team and Grants	Ecosystem Fund Allocation	Implemented
004	Compute Clients	Core-Technical	Implemented
005	Beam Compute Client	Core-Technical	Approved
006	Solana Upgrade and Emission Schedule	Core	Implemented
007	FedML Compute Client	Core-Technical	Approved
008	Nosana Compute Client	Core-Technical	Approved
009	Prime Intellect Compute Client	Core-Technical	Approved
010	Exabits Compute Client	Core-Technical	Approved
011	Piwa — Creating Millions of 3D Training Assets	Core-Technical	Withdrawn
012	Render Network Wizard for Maxon Cinema 4D	Core-Technical	Implemented
013	Year 1 Emissions Rebalancing	Core	Implemented
014	Integration of Blender Cycles in the Render Network	Core	Approved+Roadmap
015	Availability Rewards	Core	Implemented
016	Integration of Arnold in the Render Network	Core	Approved+Roadmap
017	Integration of OctaneRender for Blender into the Render Network	Core	Approved+Roadmap
018	Year 2 of BME Emissions Allocations	Process	Implemented
019	Render Compute Network	Core	Implemented
020	Node Operator Forward Guidance Policy	Process	Defeated
021	Expansion of RNP-019 to include Enterprise Grade Compute	Network	Implemented
022	Year 3 of BME Emissions Allocations	Funding	Implemented
023	Proposal for the Salad Network to migrate to RENDER	Network	Approved+Roadmap

Guidelines for RNPs

1. Members should research previous proposals to ensure that their RNP has not already been submitted or does not conflict with a proposal up for vote.
2. RNPs that conflict with a proposal that is currently up for vote, will only be put up for vote after a significant time has elapsed from when the first proposal was voted on in order to avoid conflicts and wasted effort.
3. RNPs will be removed from consideration if they involve illegal activity, hate speech, pornographic material, or do not represent the mission or values of the Render Network.
4. Technically infeasible RNPs will be removed from consideration during the review period - i.e. a component of the review process is assessing whether RNPs are actionable.

Community Principles

• Equality: It is important that everyone feels like they have a voice no matter their background and however small or large they are. The network is working to bring high end 3D graphics and related digital experiences to anyone with a creative vision.
• Constructiveness: The network is more than the sum of its parts, and looks for positive contributions to building the future of decentralized GPU computing.
• Transparency: Decisions will be publicly communicated openly and communication channels will provide open, publicly accessible forums to debate the future of RNPs.

All RNP statuses can be viewed within Github, where they are classified as "Draft Submission", "In Render Team Review", "Open for RNP Vote", "Rejected", "Approved and on the Roadmap", “In Development” and “Implemented”.