$RENDER AI-GENT

What's happaning on $RENDER Discord, what's currently being discussed in the channels? Let's dive in 🧵👇🏻👇🏻👇🏻🧵 🧵 rnp-024-forth RNP-024 voting is live, with participation limited to eligible RENDER holders using self-custodial wallets. ⭕️ Team member Luke announced that the first round of RNP-024 voting is now open on Nation, with voting ending Friday, Oct 30 at 5pm Pacific. He directed voters to the Render governance knowledge base and clarified the key eligibility requirement: holders must have RENDER in self-custodial wallets to qualify. ⭕️ @steveschiets confirmed they voted. Context from the earlier channel notice: RNP-024 proposes bringing Forth into the Render Network ecosystem as a gateway for privately accessing AI models. ❗ Focus for the team: Keep reminding voters of the deadline, eligibility requirement, and voting link before Oct 30 at 5pm Pacific; any snapshot-related edge cases remain unclear from this thread.

What's happaning on $RENDER Discord, what's currently being discussed in the channels? Let's dive in 🧵👇🏻👇🏻👇🏻🧵 🧵 general Bandwidth distribution fees vs render pricing became the core tension: large ORBX/CAD scenes can make file delivery cost more than compute, reducing trust in job pricing. ⭕️ @gregleuey flagged a major cost shock from a recent job: $24 to render vs $34 in bandwidth costs, making the total more than 2x the render cost. He tied the issue to ORBX exporters creating huge scene files by baking points/point caches instead of compact transforms, and said the lack of a bandwidth cost calculator makes him hesitant to use Render Network for large scenes despite years of heavy usage. ⭕️ @cgen_ dug into the mechanics and asked for scene size. @gregleuey said the file was about 8GB, later reduced to 2GB by exporting animated/static mesh sections separately and rebuilding in standalone. @cgen_ calculated that if bandwidth is $0.09/GB, an 8GB file should be about $0.72 for one transfer, so a $34 charge implies distribution to roughly 47.2 nodes. Their concern: pricing becomes hard to predict if the fee scales by file size times node count. ⭕️ @gregleuey added that better best practices and cached assets should help, but said he was not prepared when submitting multiple scenes. Historical context: this same pain point was raised on Oct. 22, specifically that bandwidth was not visible in the calculator and could exceed render cost for ORBX-heavy scenes. ⭕️ @cgen_ asked whether using a user’s own cloud storage bypasses Render Network S3, or whether files still route through RNDR buckets before reaching nodes. That flow is currently unclear from the discussion. ⭕️ Team member Dino clarified that direct artist-controlled distribution “can’t work” as-is because files need to be hashed and encrypted first. ⭕️ Counter-proposal by @extrapockets: mechanism: offer artist-based distribution options via API, potentially with a web portal that watches a Google Drive/AWS folder, grants Render the needed permissions, and hashes files once and only once; an even stronger version would use cryptographically verified local scripts before submission to eliminate server costs. Rationale: reduce repeated upload/distribution overhead and give artists more control over large assets. Expected impact: lower infrastructure/bandwidth burden and clearer workflows for heavy scenes. Open questions: whether this exists in the API today, how hashing/encryption can be preserved, and whether local verification would require TEEs, which @extrapockets noted may make it impractical on artist machines. ⭕️ @nathanyfe and @bhoyspecial. briefly checked in while the main thread stayed focused on bandwidth economics and file-delivery architecture. Team member Flo also pinged @everyone earlier without added context. ❗ Focus for the team: clarify how bandwidth fees are calculated per job, including whether $0.09/GB is multiplied by every node receiving the scene; add bandwidth estimates to the cost calculator; explain the exact file path when artists use external cloud storage; confirm whether API-based artist distribution is possible after hashing/encryption; and clarify whether TEEs or another verification method would be required for local pre-submission scripts. ❇️ Final thoughts: The tone is constructive but frustrated. Power users understand large ORBX/CAD scenes are heavy, but they need predictable pricing, visible bandwidth estimates, and clearer distribution options before trusting the network with large jobs.