Render Network
Independent Render review. Hollywood studios, OctaneRender demand, and OTOY's central control. RENDER tokenomics, BME burns, and the freedom trade-off.
Hollywood rendering demand with paying studio customers. But permissioned network, proprietary core, and OTOY controls everything.
- + Hollywood customers and production traction: Beeple, Apple Vision Pro, Stability AI
- + BME burn mechanism with 1M cumulative burn milestone and monthly burns up 488% within 2025
- + Strong exchange coverage: Binance, Coinbase, Kraken, OKX, with venue breadth second only to NEAR in our corpus
- − Permissioned operator model: on-boarding queue gated off-chain, no public criteria, opposite of Akash
- − OTOY controls proprietary rendering engine, takes a 5% job fee, Foundation board representation
- − Top ten Solana wallets hold nearly half the SPL supply; 50% insider allocation from OTOY treasury and partner escrow
Render Network scores an F (32/100), reflecting a fundamentally proprietary computing platform with a token layer. OTOY Inc. controls the core rendering engine, node client, job routing infrastructure, and the Foundation that gates node operator access.
While functional governance exists via RNPs, active participation is extremely low (~0.5% of supply), and ~50% of token supply is insider-controlled. The network delivers real utility (69M+ frames, growing AI compute, impressive partnerships) and has the highest market cap in its category, but from a decentralisation and sovereignty perspective it scores poorly. The open-source transparency score (2/15) is the most damaging dimension: the vast majority of the system runs on closed-source OTOY software with no public code, no reproducible builds, and no independent audit possible.
The key tension: Render is arguably the best GPU rendering marketplace product, but a poor example of decentralised infrastructure.
Infrastructure decentralisation6/20 Editorial
Permissioned node onboarding: operators must apply and be approved by Foundation. All core infrastructure is proprietary OTOY software (node client, job routing, rendering engine, allocation algorithm, reputation system). Node operators apply and are approved, so participation as a GPU provider is gated rather than open; we have taken the approval and removal powers from Render's own onboarding documentation and not tested them. 15,931 registered node operators on the Foundation dashboard (7 Oct 2026), but Foundation mediates all access. Rendering and compute are entirely off-chain and not verifiable by external parties. Solana used only for token settlement (itself having centralisation vectors: validator count declined to ~800 in 2025, 78% use Jito-Solana client). Some merit: geographically distributed GPU providers, growing toward 2.4M TFLOPS via RNP-021 (H100/H200, AMD MI300X). But the permissioned model and proprietary software stack place this firmly in the 'permissioned' range.
“To join the network as a node operator, complete the Render Network Interest Form and you will be added to the on-boarding queue.” source →
No on-chain artefact exists. Both of Render's non-token Solana programmes were enumerated exhaustively (45 accounts): 32 per-epoch emission receipts, 1 emission schedule, 1 emission distributor, 4 mint circuit breakers, 5 account circuit breakers, 3 Anchor IDL accounts. Zero operator or node-registry accounts. Network::NodeOperators exists only as an emission-distribution bucket, not as a set of operators. Every account owned by either programme classified by Anchor discriminator against the programmes' own on-chain IDLs. An operator registry would have to be one of them.
Editorial The docs describe an interest form feeding an on-boarding queue handled by the Render Network Team, with no published approval criteria and no stated removal power. No on-chain operator registry exists to check it against, so admission happens inside systems no third party can audit.
Governance decentralisation8/20 Verified
RNP system exists and is functional: 22 proposals submitted, 8 implemented, multiple governance votes. Community voting via Nation.io with 15% quorum requirement met (18% participation in RNP-022). However: actual active voting is extremely low -- only ~0.5% of supply voted for/against in RNP-022 (91.3M abstained vs 2.6M voted). RNPs are primarily authored by the Render Foundation, not community members. Foundation controls proposal filtering and implementation pipeline. OTOY Treasury (23.3%) gives insiders significant voting weight. No evidence of proposals contradicting Foundation wishes being passed. Token voting exists but Foundation heavily influences direction.
“Upon approval, RNPs shall be incorporated into the Render Network's development roadmap and implemented by core Render Network contributors.” source →
The vote is real and the execution layer is a multisig with no timelock. The two programs holding RENDER's mint and freeze authority are both upgradeable and both name the same upgrade authority (7CVt936gVDXfKeXdRs5xcWVkrEaYGMTV3HA2K7j4Bqa7), which is a Squads multisig vault: System-Program-owned and dataless, but OFF-CURVE, so no single private key controls it (Solscan: 'Squad Vault "render"', #Squad Vault; history is vaultTransactionExecute). There is no on-chain delay between a decision and a change. Render's own framing is consistent with this: they say core contributors implement, not that execution is trustless. What is absent is any disclosure of who holds the multisig, its threshold, or the controls around it, so the gap is between a documented community vote and an undocumented execution key set. npm run watch:control-surface program probe: program -> programData -> upgrade authority -> account-shape classification by ed25519 curve membership. Multisig identification attributed to Solscan's label. Ingestion only, verdict human-set.
Verified Render describes execution as work done by core contributors, and that is what the chain shows: the programs holding RENDER's mint and freeze authority change only through a Squads multisig, with no timelock between a vote and a change. Who holds the multisig and at what threshold is not disclosed. Governance stays at 8/20, which already reflects heavy Foundation influence.
Token distribution fairness6/15 Established
OTOY Treasury (23.3%) plus Partner Escrow (26.6%) is about half of supply, against 18.29% sold publicly and privately. Our September 2026 Solana read puts the top ten wallets at 48.53% of SPL supply, 22.05% of it in two multisig vaults, which is heavy but less than the 91% figure we previously carried.
The top ten RENDER holders on Solana hold under half the SPL supply, with more than a fifth of supply in two multisig vaults. The top ten hold 48.53% of the Solana SPL supply, the lowest of the four measured, with 22.05% in two off-curve Squads-style vaults (16.89% and 5.16%) and 2.01% held by a PDA of the circuit-breaker programme that also gates minting. The rest is keypair wallets, one of which is Binance's Solana hot wallet at 4.54%. That last point is the basis caveat made concrete: on the EVM path exchange custody is excluded from the rated figure and here it cannot be identified automatically, so it is counted. Resolved each of the largest token accounts to its owner, then classified the owner on-chain rather than by label: System-owned and on-curve is a keypair wallet, System-owned and off-curve is a PDA with no private key (in practice a Squads-style vault), and a known pool program is neutral infrastructure. The rated figure is the RAW top-10 share. This is NOT the EVM ex-infra basis: exchange custody cannot be identified without labels and is therefore included, which is visible here rather than assumed.
Established Consistent with a token that migrated across chains and holds a large treasury. The two vaults are multisig-controlled rather than single-key, which the curve test establishes. Exchange custody cannot be identified on Solana without labels, so it is counted in the raw figure.
Censorship resistance5/15 Established
Foundation controls node onboarding (can deny or revoke access). Proprietary node client means Foundation could push software updates that censor. Job allocation algorithm is opaque -- Foundation could theoretically deprioritise certain users or content types. No documented content-neutral policy. However: once jobs are on the network, rendering is distributed across multiple nodes. Solana settlement provides some censorship resistance for token transfers. No documented instances of censorship to date. The permissioned nature and proprietary software create meaningful censorship capability even if not currently exercised.
The RENDER mint carries a live freeze authority, and both programs behind its freeze and mint authorities are upgradeable by one Squads multisig with no timelock. The RENDER SPL mint has freezeAuthority set to a PDA of program distZXJ5FYrPhjBhB5P2BQ9B2AsPzJ4TcUSz6hKssP1 and mintAuthority set to a PDA of program circiqFCstNzaFBji1udQ6txgQBrn29pVSYHNJQo3wZ, so the token carries a live freeze lever. Both programs are upgradeable (BPFLoaderUpgradeable, upgrade authority present, not frozen) and both name the same upgrade authority, 7CVt936gVDXfKeXdRs5xcWVkrEaYGMTV3HA2K7j4Bqa7. That authority is a Squads multisig vault: System-Program-owned with no data, but off-curve, so no private key can exist for it; Solscan labels it 'Squad Vault "render"' and its history is vaultTransactionExecute calls. Replacing either program needs the multisig's threshold, with no timelock. This is the only one of the four assessed Solana natives (NOS/GRASS/AI16Z/RENDER) with a live freeze authority. Four-hop read: mint -> authority PDA -> owning program -> programData upgrade authority -> authority account shape. Shape now tested by ed25519 CURVE MEMBERSHIP, not owner+size: a Squads vault is System-owned and dataless exactly like a wallet, and only the off-curve test separates them. Automated by npm run watch:control-surface; multisig label attributed to Solscan.
Established A token-layer lever, separate from the network-layer censorship score. The multisig's signer set and threshold controls are not published. Both programs are on the control-surface watch list.
Data sovereignty6/15
Creators upload rendering assets to the network for processing on node operator hardware. Encrypted transport claimed but not independently verifiable (proprietary infrastructure). Rendered outputs returned to creators who retain ownership. No documented data retention policy for job payloads on node operator machines. Token holdings are self-custodial on Solana (strong). No data export tools documented for network interaction history. IP rights collaboration with Stability AI/Endeavor focuses on provenance (positive signal). Users control some data, but rendering data passes through opaque proprietary infrastructure with no independent verification of privacy guarantees.
Open source transparency2/15 Established
The overwhelming majority of the Render Network's codebase is closed source and proprietary to OTOY Inc. Proprietary: OctaneRender engine (commercial, EUR 23.95/month), node client software, job routing/allocation algorithm, reputation system, network backend, Dispersed AI compute platform. Open: governance proposals (RNPs on GitHub, Markdown only), basic legacy token contracts (ERC-20, 15 commits, last updated 2021), one C4D plugin release binary. Total GitHub presence: 9 repos across 2 orgs with minimal actual code. Primary active repo (RNPs) contains only governance proposals. No reproducible builds, no public code review, no independent audit of core systems possible. If OTOY ceased operations, the network would likely become non-functional. Blender Cycles integration (open-source engine) is a positive signal, but the Render Network integration layer itself is not open. This is fundamentally a proprietary commercial platform with a token layer.
Render's public GitHub holds governance proposals and plugins; the core rendering engine, OTOY's Octane, is proprietary and cannot be audited. Re-read 2026-09-18 through the GitHub API: 4 non-fork public repositories in github.com/rendernetwork (4 public in total, 0 of them forks), 4 with no licence file and 2 not pushed in 180 days. Largely CLOSED. The github.com/rendernetwork org has only 4 public repositories, and they are governance/tooling (RNPs = Render Network Proposals, a Cinema4D plugin, an advent ToS), not the rendering engine. The core render engine is OTOY's proprietary Octane software, which is not public. So the value-producing code cannot be independently audited. Direct GitHub org/repo enumeration. Ingestion only, verdict human-set.
Established Only governance proposals and plugins are public; the renderer that does the paid work is closed.
Overall returns potential is moderate at 69/100. Strongest dimension: liquidity & access (12/15). Weakest: supply dynamics (12/20).
Token utility14/20
Settlement currency for rendering and AI compute. RNP-019 (May 2025) introduced availability and job-based rewards for compute node operators, but no holder staking. Holders earn nothing by simply holding. Limited governance role.
Value accrual15/20
BME burns 95% of job payments. Hollywood customers. 1M cumulative RENDER burned by Dec 2025. Monthly burns up from ~20K (Jan 2025) to ~121K (Sep 2025). But still net inflationary.
Supply dynamics12/20 Verified· 5 checks
644M cap but OTOY treasury 23.3% unvested. Top ten Solana wallets hold under half the SPL supply, over a fifth in two multisig vaults. Alameda history.
RENDER is minted by a program under Burn-Mint Equilibrium, so supply is emission-driven rather than a fixed cap. The canonical Solana RENDER SPL mint (rndrizKT3MK1iimdxRdWabcF7Zg7AR5T4nud4EkHBof, 8 decimals) read 484,352,722.34 RENDER on-chain on 2026-08-12. Its mintAuthority is set to a program-controlled PDA (owner program circiqFCstNzaFBji1udQ6txgQBrn29pVSYHNJQo3wZ), so new RENDER is minted programmatically and supply follows emissions rather than a fixed cap. Manual SPL reads via the coldstart Solana source + mint-authority owner-classification. Ingestion only, verdict human-set.
Established The Solana leg is the canonical home of a token still migrating from Ethereum. The cross-chain total is measured in the total_supply row and the deployed emission schedule in emission_perpetuity.
Most RENDER supply now sits on the canonical Solana SPL mint, read live on each refresh. 484,343,683 RENDER on the canonical Solana SPL mint. Live getTokenSupply read scaled from base units, refreshed into meta.primary_data; also an input to the computed cross_chain_total_supply anchor.
Established Recorded as its own row because the per-chain split decides which explorer a reader should trust. The Ethereum ERC-20 and the Wormhole bridge lock are the other two legs of the computed total, and judging only the sum would hide a divergence in one leg.
“Perpetual Emissions: Under the Burn-and-Mint Equilibrium, outflows must continue in some capacity indefinitely in order to reward network activity. The schedule must be designed such that there is no end to emissions” source →
The DEPLOYED EmissionScheduleV0 on Render's emission_distributor programme carries six steps and the last sets emissions to 0 per epoch from 2028-12-01, stepping down through 380,284/epoch (from 2026-12-01) and 335,544/epoch (from 2027-12-01) first. As deployed, emissions end. Programme identified from its on-chain Anchor IDL (emission_distributor v0.1.0), account matched by Anchor discriminator, layout self-checked by requiring the rndrMint field to equal the RENDER mint before trusting any later offset.
Check pending A design requirement, graded against the deployed EmissionScheduleV0. The deployed schedule sets emissions to zero from 2028-12-01, about five years after the first epoch on 2023-11-19. RNP-001 itself splits emissions into a five-year Launch period and an indefinite Growth period whose schedule is left to later governance, so what is deployed covers the Launch period only and no Growth schedule has been set yet. The check is whether one is deployed before 2028-12-01; the schedule authority, the same Squads vault recorded on token_admin_surface, can call updateEmissionScheduleV0 to set it.
“In RNP-006 the community passed an Emissions Schedule for Year 1 allocating 9,126,804 RENDER to aid the network.” source →
The schedule figures reconcile exactly against the deployed contract: 12 epochs x 760,567 = 9.13M for Year 1 and 12 x 492,132 = 5.91M for Year 2, at a 30-day epoch. The receipts also show a second burn-rewards mint alongside the schedule (190,141.75/epoch to epoch 14, then 60,000/epoch), so total issuance is ~6.72M a year, and 23,248,298.50 RENDER has been minted across 32 epochs since 2023-11-19. Summed totalMinted + totalBurnRewardsMinted across every receipt account, matched by Anchor discriminator. Receipts are per-epoch and exhaustive, so this is a direct sum rather than a supply-delta inference.
Verified The page states schedule allocations, and those match the contract. The burn-rewards leg is a separate reward mint that the page does not describe; total issuance is tracked here by emissions_minted_all_time. Of the 107.4M governance-approved BME inflation pool, 23.25M has been minted.
The only on-chain bound on RENDER minting is a circuit breaker whose daily ceiling sits far above actual issuance, and the multisig it bounds can reconfigure it. The only on-chain bound on the mint authority is a windowed circuit breaker: MintWindowedCircuitBreakerV0 for the RENDER mint carries an Absolute threshold of 24,000,000 RENDER per 86,400-second window. Actual issuance is 552,132 RENDER per 30-day epoch (492,132 schedule + 60,000 burn rewards), about 6.72M a year, so the daily ceiling is roughly 43x a whole epoch and 3.6x a whole year of issuance. Its authority is the same Squads vault (7CVt936gVDXfKeXdRs5xcWVkrEaYGMTV3HA2K7j4Bqa7) that can upgrade the owning programme, so the breaker can also be reconfigured. Read the breaker account config (window, threshold type, threshold, authority) alongside the emission receipts that give the run rate, so the ceiling and what it bounds are measured in the same run. Ingestion only, verdict human-set.
Established The emission schedule is a policy the multisig follows; the breaker is the only enforced bound. Nothing here shows the authority has minted outside the schedule. Complements emission_run_rate and token_admin_surface.
Revenue sustainability16/25 Established
Foundation reports 81M frames rendered (Sep 2026 dashboard). OctaneRender moat. But AI compute pivot late vs Akash/io.net. BME still net inflationary.
Burns paying for rendering work are a small fraction of RENDER issuance: emissions outrun job-payment burns by roughly thirteen times. Measured in tokens, the BME wallet has burned 1,854,004.87 RENDER across 75,418 events from 2024-01-08 to 2026-09-21, against 23,800,430.5 RENDER minted across 33 epochs from 2023-11-19 to 2026-08-23. Emissions therefore outrun job-payment burns by roughly thirteen times over comparable windows, and the entire 32-month burn stream is about 3.4 epochs of current issuance at 552,132 RENDER an epoch. Every burn on the mint totals 122.6M RENDER, but 120,767,365.58 of that is a single unattributed address burning in nine chunks between 14 July and 28 August 2024, which is not job payments, and a third stream from a different address began on 2026-07-01. DeFiLlama's render-network-bme adapter reports $3,039,417.82 all-time by reading SPL burns from the one BME wallet, valuing each day's burn at that day's price and dividing by 0.95 to model the off-chain 5% OTOY fee. The adapter was read rather than inferred from its output, which is how the 0.95 divisor and the single-wallet scope became visible. The burn side is then measured in tokens, grouped by burning owner rather than summed, because an unscoped total is dominated by one address that has nothing to do with job payments. The Dune run is polled to a terminal state before its rows are read, since a query read early returns zero rows and reads exactly like a real answer. Mint and burn windows are stated because they differ by seven weeks, during which burns were 12.3 RENDER and immaterial. Ingestion only, verdict human-set.
Established The DeFiLlama figure is a price-weighted dollar sum and cannot be compared with a token count of mints; quote the token ratio, not the dollar total. Revenue Sustainability sits at 16/25 and is held for the October review against an emission rate that outruns burns by an order of magnitude. The 120.8M unattributed burn is recorded as a separate metric and attributed to nothing here.
Liquidity & access12/15 Established
Binance, Coinbase, Kraken, OKX. Strong daily volume. Solana SPL liquidity.
RENDER trades on a wide set of venues, including Binance, Coinbase, Kraken and OKX, with Solana DEX depth on Raydium, Orca and Meteora. All four confirm and the breadth is far wider than the claim: 140 tickers on 88 venues, second only to NEAR in our corpus, with Solana depth on Raydium CLMM, Orca and Meteora as stated. Reported 24h volume is $38.19M at a 4.42% 7-day median turnover. The book is not led by the majors: BitDelta tops it at 21.5% and Binance is second at 12.3%. Paginated the CoinGecko ticker set and summed 24h volume per venue; turnover from the trailing 7-day median of volume over market cap.
Established BitDelta leads the book at about a fifth of reported volume, ahead of Binance. It is the same venue that carries most IoTeX volume and a sixth of Fetch.
Not financial advice. Scores are opinions, not recommendations. Crypto is high-risk – you could lose everything you invest. Full disclaimer.
Embed this rating
The badge updates automatically when the score changes.
On this page
Hollywood-fed Burn-and-Mint with a 5% OTOY service fee
GPU rendering marketplace on Solana with real Hollywood and VFX demand. Creators submit jobs via OctaneRender or the Dispersed AI compute subnet; Foundation-approved (permissioned) operators run the work; the BME splits payment 95/5 — 95% of USD-equivalent buys RENDER and burns it, 5% is OTOY's hardcoded service fee; operators receive newly minted RENDER from the emission pool.
What it does
Render is a GPUGPUGraphics Processing Unit. Originally designed to render video game graphics, GPUs turned out to be exceptionally good at the massively parallel math that AI models need. Modern AI training and inference runs almost entirely on GPUs.Like a factory with 10,000 workers doing the same simple task in parallel, versus a CPU which is more like 10 workers each doing different complex tasks. AI training involves doing simple math a million times per second on a million numbers, which is exactly what the GPU factory is designed for.GPU in the glossary → rendering marketplace built on Solana. Creators and studios submit rendering or AI compute jobs through the Render Portal or integrated tools (OctaneRender, Blender Cycles, Redshift). Jobs get encrypted, hashed and matched to node operators based on OctaneBench scores and reputation. Output is validated through “Proof of Render” (automated quality checks plus manual creator confirmation). Payment sits in on-chain escrow until the creator approves the output.
Context that matters: Render is built by OTOY Inc., a Los Angeles-based company founded by Jules Urbach in 2008. OTOY created OctaneRender, a widely used GPU rendering engine with native integrations into Blender and Cinema 4D. The Render Network is OTOY’s distributed compute layer. The Render Network Foundation, spun out in January 2023 and registered in the Cayman Islands, handles governance. Urbach’s COO sits on the Foundation board.
The Foundation’s dashboard shows 15,940 registered node operators, while the same page counts 5,600 total nodes since inception, which suggests the operator figure counts registrations rather than concurrent active nodes. It is explicitly permissioned. Render’s own documentation routes would-be operators through an interest form into an on-boarding queue, and says the Render Network Team follows up “when your node is ready to be added”, which sets out no criteria and no timeline. That gate leaves no trace on-chain either: neither of Render’s two deployed Solana programmes holds an operator registry of any kind, so who joined the queue, who cleared it and who did not are all facts that exist only inside OTOY’s systems. This is the opposite of how Akash operates, where anyone with qualifying hardware joins without permission and the validator set is a public read.
RNP-019, passed in May 2025, established a dedicated GPU compute subnet for AI and general-purpose workloads, separate from the existing rendering infrastructure. It introduced availability rewards (2 RENDER per weekly epochEpochA fixed-length period in a Proof of Stake blockchain during which the validator set is stable and rewards are calculated. Epochs are the natural unit for staking rewards and network state changes.Like a payroll period at a job. Within the period, your role is fixed and your pay is calculated based on hours worked. At the end, the period closes, paychecks are issued, and a new period begins with potentially different conditions.Epoch in the glossary → per node, prorated by uptime) and job-based rewards (baseline 10 RENDER per epoch for an RTX 4090 at full utilisation, scaled by hardware spec and hours worked). Consumer-grade GPUs like the RTX 4090/5090 can participate. This subnet was officially branded Dispersed at Solana Breakpoint in December 2025, launching with 600-plus AI models at $1.75/hour. RNP-021 subsequently proposed extending the subnet to enterprise-grade GPUs (NVIDIA H200, H100, AMD MI300 series). Adoption metrics for Dispersed are not yet available.
In April 2026, RNP-023 received full approval. The first governance round passed at 98.86%, and the second round was confirmed during the Foundation Updates session at RenderCon 2026 on 17 April 2026. The proposal integrates Salad Network as an exclusive Dispersed subnet provider, contributing roughly 60,000 distributed consumer GPUs in exchange for RENDER-settled job revenue feeding the BME burn. The Foundation cited approximately $4.3M projected first-year revenue from the Salad integration. The June 2026 Foundation report (published 8 July 2026) states the Salad integration milestones are live, adding roughly 60,000 consumer GPUs with on-chain RENDER settlement feeding the BME burn. We’re still holding off on score impact: the report describes rising burns qualitatively, but a clean Salad-attributable on-chain burn figure isolated from baseline network activity is not yet published. RenderCon 2026 ran 16-17 April in Los Angeles.
The team is roughly 99 people. Advisory board includes J.J. Abrams, Ari Emanuel (Endeavor/WME CEO), Beeple and Brendan Eich (Brave founder). The Hollywood connections are substantive.
The product in practice
Grounded in our Render review, the render-vs-akash comparison, and community sentiment on OTOY’s user forums. We haven’t rendered on the network ourselves, so the hands-on notes are attributed and, where flagged, not recent.
Who it’s for. Motion designers, VFX and 3D artists working in the Octane pipeline, Cinema 4D, Blender, Houdini and Redshift, who want to burst-render heavy scenes without owning a farm. Render is OTOY’s distributed layer for its own OctaneRender engine, so it fits people already in that toolchain more than newcomers. The newer Dispersed subnet extends it to general AI and compute jobs, though that audience is only just being courted.
What it’s like to use. You submit a scene through the Render Portal or a native integration like the Cinema 4D Wizard, estimate the cost from your local OctaneBench score, and pay from on-chain escrow that releases only when you approve the output. The guardrails help: redundant nodes validate frames, and three failed re-renders auto-terminate the job and open a support ticket. The friction is documented too, and on OTOY’s own user forums artists have reported cost estimates undershooting the actual burn, occasional wrong or spurious frames that rendered fine locally, and jobs stalling mid-process, though those threads skew to earlier years and route to private support rather than resolving in the open. Node operators describe low and spiky utilisation, treat it as monetising idle hardware rather than income, and are paid only after the creator approves, with network rewards minted per 30-day epoch on-chain and no guarantee of how much work a node receives.
Permissioned by design. Unlike Akash, Render operators must be approved by the Foundation, and jobs are matched on OctaneBench score and reputation. That curation is a deliberate choice aimed at render quality and enterprise trust, and it sits at the opposite end of the decentralisation trade from a permissionless marketplace. It is why Render scores lowest on Freedom of the compute set while scoring highest on Returns.
Demand, honestly. The rendering business is the track record: the Render Foundation’s own dashboard reports 81,018,221 frames rendered all-time (read September 2026), and BME burns rose 279% year on year over January to September 2025, the latest like-for-like comparison we hold. Frames are counted off-chain, so that total has no independent or on-chain check. USD revenue is not publicly disclosed, so we don’t publish a figure or a multiple for it, and the named studios, from NASA visuals to Coachella stages, are Foundation-surfaced case studies rather than independently confirmed contracts. Dispersed, the AI-compute bet launched in December 2025, had no adoption figures disclosed at launch, so that half of the story is still a claim.
The vision. Render wants to be both the render farm and a general GPU-compute layer, using OTOY’s Octane install base and Hollywood relationships as the wedge. The bet is that the pipeline advantage in rendering carries into AI compute through Dispersed and the planned Salad and enterprise-GPU integrations. Whether it lands shows up in one place we can watch: the burn rate from paid jobs rather than emissions.
Value proposition
OctaneRender moat
Hollywood and VFX adoption: Beeple, Apple Vision Pro, Stability AI. 81M cumulative frames per the Foundation (September 2026).
Burn-and-Mint Equilibrium
95% of job payments converted to RENDER and burned. 1M cumulative burn milestone reached December 2025.
Permissioned by OTOY
OTOY controls proprietary engine, takes a 5% job fee, Foundation board and operator approval.
Render’s moat is OctaneRender. If you are a 3D artist or VFX studio already using OctaneRender, the Render Network is a natural extension: submit your OctaneRender jobs to distributed GPUs instead of buying your own render farm or paying AWS rates, often at a lower price than centralised cloud rendering.
The production credits check out. Beeple, Apple Vision Pro integration, Stability AI partnership. These are not speculative use cases. The Render Foundation reports more than 81 million cumulative frames on its own dashboard (September 2026). Paying studios drive the rendering demand.
Here is the counter-narrative. Render is, functionally, OTOY’s service with a tokenTokenA digital unit of value or access rights tracked on a blockchain. Tokens can represent ownership in a project, a right to use a service, a share of future revenue, or simply a tradable asset with no underlying claim.Like a physical poker chip a casino issues. The chip itself has no value. What makes it worth something is what it lets you do at the casino, what the casino has promised, and how much other people will pay you for it.Token in the glossary →. OTOY controls the core rendering engine (proprietary, closed source). OTOY receives a 5% service fee on jobs, set out in RNP-019 as compensation for network operations and taken from job credits off-chain, so it never shows up in the on-chain burn. The Foundation’s governance operates within boundaries that OTOY defines. The permissioned operator modelModelA trained neural network that takes inputs (text, images, audio) and produces outputs (more text, classifications, generated content). In DeAI the model is the thing that actually does the work.Like a very experienced apprentice who has spent years watching thousands of masters make furniture. They can't explain how they know when a joint is right, but they can make a chair that looks and functions like a Chippendale. The training is invisible. The output is what matters.Model in the glossary → means the Foundation, not the market, decides who provides compute.
For the sovereignty thesis, that’s a problem. Paying demand, a shipping product, named customers, but the decentralisation layer is thin. The token enables a distributed GPU supply side, which is useful. But the supply side is the only meaningfully decentralised component. Everything else, the rendering engine, the job orchestration, the operator approval, the AI compute layer, is controlled by OTOY or the Foundation it created.
Tokenomics
RENDER (originally RNDR on Ethereum, migrated to Solana SPL via Wormhole in November 2023) launched through an ICOICOInitial Coin Offering. A token sale where a project sells tokens directly to the public, usually before any product exists. ICOs dominated 2017-2018 funding and are now mostly replaced by airdrops, IDOs, or fair launches.Like a company selling shares to the public before going public, except with no SEC oversight, no audited financials, and often no product at all. The 2017 ICO boom showed why those guardrails exist in traditional finance.ICO in the glossary → in October 2017 at $0.25 per token. The ICO had a $134 million hard cap but raised only $1.16 million publicly. A private sale in January 2018 raised roughly $4 million. A $30 million strategic round in December 2021, led by Multicoin Capital with participation from Alameda Research, Solana Foundation and Sfermion, significantly changed the investor profile.
Distribution tells the story:
- Escrow for partners: 26.6% (three tranches, cliffCliffA waiting period at the start of a token vesting schedule during which no tokens unlock at all. After the cliff ends, tokens begin releasing according to the vesting schedule.Like a probationary period at a new job. You don't get your stock options on day one. You wait 12 months to prove you'll stick around, then everything starts unlocking normally.Cliff in the glossary → vestingVestingA schedule that locks up tokens allocated to insiders, investors, and team members, releasing them gradually over months or years. Vesting prevents insiders from dumping on public buyers immediately after launch.Like a new employee's stock options at a startup. You don't get all the shares on day one. They unlock over four years so you stick around and do the work rather than cashing out and leaving.Vesting in the glossary → extending to 2051)
- OTOY treasury: 23.3% (company-controlled, no vesting)
- Public and private sale: 18.29%
- BMEBurn-Mint EquilibriumA tokenomics model where network fees burn tokens while new tokens are minted and paid to suppliers. The system tries to balance burns and mints so circulating supply stays roughly stable when usage scales.Like a business that spends a dollar of revenue for every dollar of wages it pays. Money flows in and out at the same rate, so the total cash in the company stays flat. The rate of flow tells you how big the business is.Burn-Mint Equilibrium in the glossary → inflationInflationThe annual rate at which new tokens are created and added to the circulating supply. Most networks use inflation to pay validators, stakers, and infrastructure providers from freshly minted tokens rather than real revenue.Like a landlord who raises the rent every year. If your salary goes up at the same rate, you break even. If it doesn't, you get poorer without noticing, because the number on your payslip hasn't changed but the ground under it has shifted.Inflation in the glossary → pool: 16.67% (governance-approved expansion)
- Reserve: 8.61%
- Subsequent distribution: 6.52%
Combined insider allocation is approximately 50% (OTOY Treasury plus Partner Escrow alone). This is one of the most insider-heavy distributions in the DeAIDeAIDecentralised AI. An umbrella term for blockchain-based projects that build AI infrastructure (compute, data, inference, models, agents) without a single central provider controlling the system.Like the difference between streaming a movie from Netflix and sharing it via BitTorrent. Netflix is fast and polished but one company controls what you can watch and what you pay. BitTorrent is messier but no single operator can shut you out.DeAI in the glossary → space. On our September 2026 read of the Solana mint, the top ten wallets hold 48.53% of SPL supply, including 22.05% in two off-curve Squads multisig vaults. Binance’s Solana hot wallet accounts for 4.54% of supply within that top ten, and exchange custody can’t be separated out automatically on Solana, so it’s counted. The OTOY treasury alone (23.3%) represents company-controlled supply with no vesting schedule.
Burn-and-Mint Equilibrium (BME)
The Burn-and-Mint Equilibrium (BME) works like this: 95% of USD-equivalent job payments get converted to RENDER and burned. 5% goes to OTOY as a service fee. Node operators receive newly minted RENDER from the emission pool. Year one emissionsEmissionsNew tokens created and distributed by a blockchain protocol over time as rewards to validators, stakers, or miners. Emissions fund network security and participation at the cost of diluting existing holders.Like a company that pays employees partly in newly printed shares. Every year the total number of shares goes up, which means existing shareholders own a slightly smaller slice of the same company unless the company grows faster than the printing.Emissions in the glossary →: 9.13 million RENDER. Year two: 5.91 million (35% reduction).
Those two figures come from Render’s proposals, and the deployed contract confirms them exactly: the emission programme on Solana pays a fixed amount per 30-day epoch, and twelve epochs of its first and third steps give 9.13 million and 5.91 million. Two things the proposals do not say are visible only on-chain. The schedule carries a second mint alongside it, a burn-rewards leg currently running 60,000 RENDER an epoch, so actual issuance is 6.7 million RENDER a year rather than the 5.91 million of the schedule alone. And 23.8 million RENDER has been minted across 33 epochs since November 2023, every one of them recorded on-chain as its own receipt.
The deployed schedule ends. Its last step sets emissions to zero from 1 December 2028, stepping down through two lower rates first. Render’s own RNP-001 says that “outflows must continue in some capacity indefinitely” and that “the schedule must be designed such that there is no end to emissions”, and we previously took that document as settling how the supply behaves. A proposal is a primary source about what a team intends, and the contract is the thing that pays.
The same proposal splits emissions into a five-year Launch period and an open-ended Growth period left to later governance, and the zero step lands at the close of year five. What is deployed covers the Launch period only, and no Growth schedule has been set yet.
It matters for the 644 million cap as well. The governance-approved inflation pool is 107.4 million RENDER, and the schedule as deployed will spend roughly a third of it before it stops.
The honest qualifier is who can change it. The schedule authority is the same Squads multisig that upgrades both programmes and holds the manual-mint authority, and it can rewrite the schedule with one transaction. So this is the currently-deployed state rather than a promise, and a reader should treat “emissions end in 2028” as what the chain says today and “perpetual emissions” as what the proposal intends. One of the two has to give.
The maths is moving in the right direction. Burns reached 1 million cumulative RENDER in December 2025, a milestone that took roughly three years under BME. Monthly burns accelerated from approximately 20,000 RENDER in January 2025 to 121,000 RENDER by September 2025 (a 488% increase within the year), with January-to-September 2025 totalling 530,171 RENDER burned (up 279% year-over-year). But monthly emissions still outpace monthly burns by a significant margin. BME remains net inflationary: on our on-chain count, emissions have outrun job-payment burns by roughly thirteen times over comparable windows since late 2023. Render has not publicly disclosed revenue figures, so a price-to-revenue ratio cannot be calculated. Any comparison to Akash, which does disclose revenue, would require comparable disclosure from Render first.
No native staking
There’s no native stakingStakingLocking up a cryptocurrency to help secure a blockchain network, usually in exchange for rewards. The locked tokens act as a security deposit that can be taken away if the staker misbehaves.Like putting down a large rental deposit for an apartment. You get the money back if you behave, you earn interest while it's locked, and the landlord takes it if you trash the place.Staking in the glossary → for RENDER holders. Simply holding the token earns nothing. RNP-019 introduced availability and job-based rewards for compute node operators on the Dispersed subnet, but these are operator compensation for providing GPU capacity, not holder staking. The proposal explicitly states “no staking is mandated initially.” Earnings up to $100 are held as an implicit deposit before disbursement, which functions as a stability measure rather than a staking mechanism. The token’s primary function for holders, beyond rendering settlement, remains speculation.
The Alameda connection
The Alameda connection deserves attention. Alameda Research participated in the $30 million round. NCRI research documented coordinated Twitter bot manipulation that pumped RNDR price by 11-30% on four separate occasions. Roughly half of all Twitter posts about RNDR during those manipulation windows were inauthentic. After FTX collapsed, 972,073 RNDR tokens were transferred from the bankruptcy estate to exchanges.
RENDER is down more than 85% from its March 2024 all-time high. Listed on Binance, Coinbase, Kraken, OKX, Bybit and others. The Binance listing gives Render significantly more liquidityLiquidityHow easily a token can be bought or sold without moving the price. High liquidity means you can enter or exit large positions quickly at the quoted price. Low liquidity means even small trades can swing the market.Like the difference between selling a house and selling a share of Apple stock. The house might be worth more on paper, but finding a buyer at that price takes weeks. The Apple share converts to cash in one click.Liquidity in the glossary → than Akash, which matters for retail discovery. See live data above for current pricing.
How to participate
Provide GPUs (if approved). Apply to become a node operatorValidatorA computer that runs the full blockchain protocol, verifies transactions, and proposes new blocks. Validators are the workers that keep a Proof of Stake network running, and they earn rewards for doing the work correctly.Like a notary public who witnesses and stamps legal documents. Validators witness transactions, check they follow the rules, and stamp them into the permanent record. A notary who commits fraud loses their license. Validators work the same way, except the license is staked tokens that get slashed on misbehaviour.Validator in the glossary →. The Foundation reviews applications. For the traditional rendering network, minimum hardware is NVIDIA GPU with CUDA 10.1+, 6GB+ VRAM (8GB+ preferred), 32GB+ RAM, 100GB disk, 100/75 Mbps internet, with rewards weighted by compute (25%), bandwidth (35%), GPU model (20%) and uptime (20%). Since RNP-019 (May 2025), the Dispersed compute subnet also accepts consumer-grade GPUs (RTX 4090/5090) for AI and general compute, with availability rewards (2 RENDER per weekly epoch, prorated by uptime) and job-based rewards scaled by hardware spec and utilisation. The permissioned approval process remains the main barrier for both subnets.
Create and render. Submit rendering jobs through OctaneRender, Blender Cycles or the Render Portal. Pay in RENDER or Render Credits (stablecoin-equivalent), often at a lower price than centralised alternatives. This is the primary use case and the reason the network exists.
Governance. Participate in Render Network Proposals (RNPs) through Nation.io. Four-phase process: Draft, Initial Vote (72 hours, no quorum), Final Vote (6 days, 15% quorum of total supply), Implementation. Token-weighted. Be aware that concentrated holdings, including the OTOY treasury, heavily influence outcomes. Active participation is negligible: in RNP-022, only 0.5% of supply actively voted for or against (91.3 million tokens abstained out of 93.9 million participating). RNPs have run past twenty, with RNP-023 approved in April 2026.
Note: no holder staking, but operator rewards exist. Unlike most DePINDePINDecentralised Physical Infrastructure Networks. Protocols that use token incentives to coordinate real-world physical infrastructure like GPU compute, wireless networks, storage, mapping sensors, or bandwidth.Like crowd-sourced ride-sharing but for physical hardware. Uber incentivises drivers with dollars. DePIN incentivises hardware operators with tokens. The network grows because individuals choose to contribute capacity in exchange for rewards.DePIN in the glossary → tokens, RENDER offers no staking mechanism for passive holders. Simply holding the token earns nothing. However, RNP-019 (May 2025) created a structured rewards framework for compute node operators: availability rewards (2 RENDER per weekly epoch, prorated by uptime) and job-based rewards scaled by hardware and utilisation. This gives GPU providers a concrete earning model, but it requires active participation as an approved operator, rather than token ownership alone. The distinction matters: Render now has a participation-based earning path, though that path is not staking in any conventional sense.
Honest assessment
What works
The rendering demand keeps growing. The Foundation’s dashboard counts more than 81 million frames rendered (September 2026). Enterprise and Hollywood-grade adoption, including Beeple and Apple Vision Pro integration. The network crossed 1 million cumulative RENDER burned in December 2025, with monthly burns accelerating 488% within the year (from ~20K in January to ~121K by September). That is a concrete organic demand signal, even if still small relative to emissions.
RNP-019 (May 2025) expanded the network into AI and general compute with a structured operator rewards system, and the Dispersed subnet launched in December 2025. OctaneRender integration provides a concrete moat. The Solana migration completed successfully, exchange coverage is strong, and the advisory board has legitimate industry credibility.
What doesn’t work
The decentralisation narrative falls apart on inspection. Render is a permissioned network controlled by OTOY through multiple vectors: proprietary rendering engine, a 5% job fee, Foundation board representation, operator approval, closed-source orchestration layer. That Foundation is a governance facade. Core rendering software, job orchestration, node operator client and Solana smart contracts are all closed source. Nine public GitHub repositories contain near-zero operational code, only governance proposals and legacy token utilities. Six contributors total. Calling this open source overstates the openness by an order of magnitude. The stack is proprietary, with a thin shell of open governance around it.
The risk
Jules Urbach is an extreme key person risk. Single founder controlling both OTOY (the company) and Render (the token network) with no visible succession plan. Concentrated holdings (the top ten Solana wallets hold nearly half the SPL supply, two multisig vaults over a fifth) mean governance is effectively controlled by a small number of large holders, and active voting participation of just 0.5% of supply means outcomes are easily influenced. No verifiable audit of current Solana infrastructure exists. The only confirmed audit (OpenZeppelin, September 2017) covered deprecated Ethereum crowdsale contracts. The Alameda investment and documented bot manipulation add a credibility stain that does not wash off easily.
The AI compute pivot remains late despite RNP-019 laying the groundwork in May 2025. Akash launched GPU compute in September 2023 and has a multi-year head start with a permissionless model. io.net entered the space with a similar timeline. Render’s Dispersed subnet launched in December 2025 with a permissioned approach and faces established competition. The RNP-019 operator rewards (availability + job-based) give GPU providers a clearer earning model than before, but the network still lacks the permissionless onboarding that competitors offer.
Solana single-chain dependency means its seven separate outage incidents (with a declining validator count and 78% client homogeneity via Jito-Solana) can halt settlement. There’s no fallback chain.
My position
I hold RENDER. I bought it for the BME thesis and the OctaneRender moat: Hollywood rendering customers create verifiable demand that most DeAI projects can’t match. The permissioned network model and proprietary core are serious concerns, and they’re why the Freedom Score sits at 32/100. Render is a good product. Whether it’s decentralised infrastructure in any meaningful sense is a different question, and the honest answer is no. But the returns thesis is separable from the sovereignty thesis.
Freedom Score: 33/100
Render scores 33/100 (F grade). Full methodology at Freedom Score Methodology.
Infrastructure decentralisation (6/20): 15,940 registered node operators on the Foundation’s dashboard, but the network is explicitly permissioned: Render’s docs route applicants through an interest form into an on-boarding queue held by the Render Network Team, with no published criteria. Checked on-chain August 2026: neither deployed Solana programme carries an operator registry, so the admitted set is unauditable and the claim can only ever be Render’s own. All core infrastructure is proprietary OTOY software: node client, job routing, allocation algorithm, reputation system. Rendering is off-chain and not verifiable by external parties. Compare with Akash’s permissionless model where anyone with hardware joins without approval.
Governance decentralisation (8/20): More than twenty Render Network Proposals with voting on Nation.io. 15% quorum requirement met (18% participation in RNP-022). But actual active voting is negligible: only ~0.5% of supply voted for/against in RNP-022 (91.3M tokens abstained vs 2.6M voted). RNPs are primarily authored by the Foundation. OTOY Treasury (23.3%) gives insiders significant voting weight. No evidence of proposals contradicting Foundation wishes being passed.
Token distribution fairness (6/15): OTOY Treasury (23.3%) plus Partner Escrow (26.6%) equals ~50% insider-controlled supply. Public and private sale combined only 18.29%. The top ten Solana wallets hold 48.53% of SPL supply, including 22.05% in two multisig vaults (September 2026 read). The $30 million 2021 round from Multicoin and Alameda further increased institutional concentration. ICO was small ($1.16 million) but the overwhelming insider allocation dominates the picture.
Censorship resistance (5/15): Permissioned operator model means the Foundation can approve or deny GPU providers. Proprietary node client means Foundation could push updates that censor. Job allocation algorithm is opaque. No documented content-neutral policy. Solana dependency adds chain-level risk (7 outage incidents, declining validator count, 78% client homogeneity).
Data sovereignty (6/15): Creators upload rendering assets to the network for processing on node operator hardware. Encrypted transport claimed but not independently verifiable (proprietary). Token holdings are self-custodial on Solana. But the Foundation knows all participants (permissioned) and rendering data passes through opaque proprietary infrastructure with no independent verification of privacy guarantees.
Open source and transparency (2/15): The overwhelming majority of the codebase is proprietary to OTOY Inc.: OctaneRender engine (commercial, EUR 23.95/month), node client, job routing, allocation algorithm, reputation system, network backend. Public GitHub repos contain only governance proposals (Markdown), legacy token contracts (last updated 2021), and one plugin binary. 9 total repos across two orgs. 6 contributors. No reproducible builds. No independent code review possible. If OTOY ceased operations, the network would likely become non-functional.
Path to improvement
Three changes would materially increase Render’s score:
- Open-source the orchestration layer. The rendering engine itself has legitimate IP protection arguments. But the job orchestration, node operator client and Solana programmes could be open-sourced without compromising OctaneRender’s proprietary position. This would be the single biggest signal that Render takes decentralisation seriously rather than using it as marketing language.
- Move to permissionless operator onboarding. The permissioned model is the clearest centralisation vector. Akash proves that permissionless compute marketplaces work. The Foundation’s approval process serves OTOY’s quality control interests, not decentralisation. A reputation and staking-based operator model would distribute control away from the Foundation.
- Commission a current security audit. The only verified audit covers deprecated 2017 Ethereum contracts. The current Solana infrastructure, including BME emission contracts, escrow mechanisms and the SPL token programme, has no publicly verifiable audit. For a network handling enterprise production workloads at this scale, this is a significant gap.
Returns Score: 69/100
RENDER scores 69/100 (C grade). Full methodology at Returns Score Methodology.
Token utility (14/20): RENDER is the settlement currency for rendering jobs and, increasingly, AI compute through the Dispersed subnet. Creators pay in RENDER or Render Credits for GPU rendering, and node operators receive newly minted RENDER as compensation. RNP-019 (May 2025) expanded the token’s role by introducing structured availability and job-based rewards for compute node operators, giving RENDER a clearer function in the AI compute layer. However, the utility remains operator-facing. There is no holder staking mechanism, no governance weight tied to holdings, and no additional demand sink beyond job settlement and operator rewards. Simply holding RENDER still earns nothing.
Value accrual (15/20): The Burn-and-Mint Equilibrium converts 95% of USD-equivalent job payments to RENDER and burns it, with OTOY taking a 5% service fee under RNP-019. Hollywood customers (Beeple, Apple Vision Pro integration, Stability AI) drive burnBurnPermanently removing tokens from circulation by sending them to an address that no one controls. Burns reduce total supply, which (all else equal) makes each remaining token worth more of the network's value.Like a company buying back its own shares and shredding them. The company's total value stays the same, but each remaining share now represents a slightly bigger slice of that value.Burn in the glossary → demand. The network crossed 1 million cumulative RENDER burned in December 2025, with monthly burns accelerating from ~20,000 (January 2025) to ~121,000 (September 2025), a 488% increase within the year, and 279% year-over-year. The mechanism directly ties network usage to token scarcity. The caveat: monthly emissions still outpace monthly burns at current usage levels. BME remains net inflationary: on our on-chain count, emissions have outrun job-payment burns by roughly thirteen times over comparable windows, so the burn growth has yet to close the gap.
Supply dynamics (12/20): RENDER has a cap of 644 million tokens (536.9 million original plus 107.4 million governance-approved BME inflation pool). The structural concern is concentration: the OTOY treasury holds 23.3% with no vesting schedule, partner escrow accounts for 26.6% with cliff vesting extending to 2051, and the top ten Solana walletsWalletSoftware that stores the private keys needed to control tokens on a blockchain. A wallet does not actually hold any tokens. The tokens live on the chain. The wallet holds the keys that prove you own them.Like the key to a safe deposit box. The key doesn't contain your valuables. The valuables sit in the bank's vault. The key is what proves you're allowed to open the box and take them.Wallet in the glossary → hold nearly half the SPL supply, with over a fifth of supply in two multisig vaults. The Alameda connection (documented bot manipulation that pumped prices 11-30% on four occasions) adds a credibility stain to the distribution history. Whale concentration of this magnitude means a small number of actors can move the market at will.
Revenue sustainability (16/25): Render has demonstrated actual product-market fit. The Render Foundation reports more than 81 million cumulative frames (September 2026 dashboard reading), a self-reported off-chain count. The OctaneRender integration provides a structural moat; studios already using OctaneRender have a natural path to the distributed rendering network. Enterprise and Hollywood-grade customers create demand that isn’t speculative or crypto-native. The AI compute pivot through Dispersed is late relative to Akash and io.net, but the existing rendering revenue base provides a foundation that pure-play AI compute networks lack.
Liquidity and access (12/15): RENDER is listed on Binance, Coinbase, Kraken, OKX, Bybit and other major exchanges, with strong daily volume. The Binance listing in particular gives Render significantly deeper liquidity than most DeAI competitors. You can trade meaningful positions without excessive slippageSlippageThe difference between the expected price of a trade and the price you actually get when the trade executes. Slippage usually goes against the trader and gets worse with bigger trades or thinner markets.Like trying to buy 1000 bananas at the corner shop. The first few are at the marked price, but by the time you've bought them all you've moved the price up because there are no more bananas left at the original level. The shop has to restock at higher cost.Slippage in the glossary →. The Solana migration completed cleanly, and SPL token liquidity on decentralised venues supplements the centralised exchange coverage. This is a well-distributed token from a trading accessibility standpoint, even if the holder concentration is extreme.
Path to improvement
Three changes would materially increase Render’s returns score:
- Introduce holder staking with fee distribution. RNP-019 introduced operator rewards for GPU providers, but RENDER holders still earn nothing by holding. A staking system that distributes a portion of rendering fees or BME proceeds to token stakers would create a demand sink, reduce circulating supplyCirculating SupplyThe number of tokens currently in circulation and tradeable on the open market. Differs from total supply (which includes locked or unvested tokens) and max supply (the upper limit, if there is one).Like the number of cars on the road today versus the number ever produced. Some are in showrooms, some in junkyards, some still at the factory. Only the ones on the road count toward what people are actually driving.Circulating Supply in the glossary → and give holders an economic reason to stay beyond price speculation.
- Close the burn-to-emission gap. The 1 million cumulative burn milestone (December 2025) is encouraging, but monthly emissions still outpace monthly burns. Growing rendering and AI compute volume, including through the Dispersed subnet, to narrow this gap is the most direct path to making the deflationary narrative match reality.
- Publish the OTOY treasury vesting schedule. The 23.3% treasury allocation with no published vesting creates uncertainty for holders. A transparent, time-locked vesting schedule (ideally enforced on-chain) would reduce the overhang risk and signal alignment between OTOY’s interests and token holders.
Score change log
| Date | Score | Change | Reason |
|---|---|---|---|
| 2026-10-07 | Data | N/A | Node-operator count now bound to the Foundation dashboard (15,931 on 7 Oct, was 15,670 from March), refreshed weekly. Scores unchanged. |
| 2026-10-04 | Data | N/A | Node payouts were described as roughly weekly; on-chain emission receipts run 30-day epochs, so corrected. The ‘burns rising’ line is now anchored to the January to September 2025 comparison. Scores unchanged. |
| 2026-09-24 | Score | Freedom 32 to 33; Returns 72 to 69 (B to C) | Value Accrual 18 to 15: emissions outrun job-payment burns about thirteen times and the 5% fee is off-chain. Token Distribution 5 to 6: top ten hold 48.5%, not the 91% we carried. |
| 2026-09-24 | Data | N/A | The 5% job fee is OTOY’s per RNP-019 (Render Foundation and Render Labs, implemented), taken from job credits off-chain; “hardcoded” dropped, and the research JSON’s “to the Foundation” corrected. Scores unchanged. |
| 2026-09-24 | Data | N/A | ”91% held by ~902 addresses” and an unsourced 20.5M accumulation figure replaced with our Solana holder read (top ten 48.53%, 22.05% in two multisig vaults); “gap is narrowing” replaced with the ~13x emissions-to-burn finding; ATH, RNP count, an unsourced 50-80% saving and two superlatives softened. Scores unchanged. |
| 2026-09-24 | Data | N/A | Reconciled three stale frame counts (63M, 69M, and 22M or ~35% in 2025) to one dated reading: 81,018,221 per the Render Foundation’s own dashboard, attributed as self-reported. Scores unchanged. |
| 2026-09-23 | Data | N/A | Integrity records re-cut: 4 claims now quote Render’s own pages verbatim and 9 are our own measurements. Scores unchanged. |
| 2026-08-19 | Data | N/A | Correction. Dropped a hardcoded Akash revenue multiple used as a comparison; the point of the sentence is that Render discloses no revenue, which does not need the peer figure. No score change. |
| 2026-08-17 | Data | N/A | Emission index built from the deployed Solana programmes (both identified from their own on-chain Anchor IDLs). The deployed schedule sets emissions to zero from 1 December 2028, contradicting the RNP-001 “perpetual emissions” row below, which took a design document as evidence about behaviour. Score held, flagged for September. |
| 2026-08-17 | Data | N/A | Two further on-chain reads. Actual issuance is ~6.72M RENDER a year, not the 5.91M the RNP headline implies, because a burn-rewards leg mints alongside the schedule; 23.25M has been minted across 32 epochs. No operator registry exists on either programme, so Foundation approval is unauditable and the prose now says so. |
| 2026-08-13 | Data | N/A | SUPERSEDED 2026-08-17, see above. Render’s own RNP-001 states “Perpetual Emissions… The schedule must be designed such that there is no end to emissions”, so the supply should be read as disinflationary rather than fixed. Recorded in the verdict; no score change. |
| 2026-08-12 | Data | N/A | WS3 Solana on-chain reconciliation (1->4 verdicts). Canonical Solana leg 484M (a component of the 533M cross-chain total); supply minted by the BME program, not fixed (established). Freeze authority SET = accounts can be frozen (established). Open-source mostly closed, core renderer is proprietary OTOY (established). Scores unchanged. |
| 2026-07-06 | Editorial | N/A | Added a “The product in practice” section (per specs/product-comparison-framework.md) from our review and OTOY-forum sentiment; revenue is undisclosed so no USD figure is asserted (frame throughput and BME burn growth instead). No score change. |
| 2026-06-13 | Data | N/A | Refreshed recorded total supply from 533.47M to the cross-chain economic total ~567.66M: Solana SPL 483.54M (on-chain getTokenSupply, mint rndriz...HBof, now a standing anchor) plus ~84.12M RNDR still un-migrated on Ethereum. The prior 533.47M was the legacy Ethereum ERC-20 frozen total, which counts tokens locked in the Wormhole bridge but misses the ~34.16M net BME emissions minted to operators on Solana; CoinGecko still uses that basis. Equivalently: surviving original 533.50M + net Solana BME emissions 34.16M. Circulating 518.74M (CoinGecko cross-chain estimate) is unchanged and now consistent (80.5% of the 644M cap). Integrity supply reconciliation set to established with the cross-chain decomposition. Supply-dynamics narrative and scores unchanged. |
| 2026-05-18 | Data | N/A | Revenue disclosure status re-verified against primary sources during remediation of a Render P/Revenue fabrication discovered in the companion tokenomics article (/tokenomics/render-vs-akash-vs-ionet/). Sources checked: Render Foundation’s March 2026 Annual Financial Overview (discloses emissions only, not USD revenue), Messari State of DePIN 2025 (sector trades at 10-25x revenue; named leaders are Helium and GEODNET, not Render). The “revenue not publicly disclosed, P/Revenue cannot be calculated” position in the BME section of this article is confirmed by primary source. Scores unchanged. |
| 2026-08-03 | Editorial | N/A | Salad subnet now live per the June 2026 Foundation report (published 8 July 2026): ~60K consumer GPUs, RENDER-settled, feeding BME. Body updated from “approved” to “live”. Revenue Sustainability +1 still HELD: no Salad-attributable on-chain burn figure isolated from baseline is published yet. |
| 2026-05-03 | Data | N/A | RNP-023 second-round result confirmed: full approval at RenderCon 2026 on 17 April 2026 per Render Foundation Updates session and multiple secondary sources. Editorial body updated from “second round in progress” to “received full approval”. Score impact still deferred until on-chain burn-rate uplift from Salad-routed jobs appears in the Foundation’s monthly report. |
| 2026-05-02 | Editorial | N/A | Added RNP-023 second governance round on Salad subnet integration (~60K consumer GPUs, ~$4.3M projected first-year revenue, RENDER settlement, feeds BME burn). RenderCon 2026 noted. Score impact deferred until second-round result and on-chain burn uplift verified. |
| 2026-04-06 | Data | N/A | Quarterly review. Qualified “no staking” language to reflect RNP-019 operator rewards. 1M burn milestone already reflected. Verified against primary sources. Scores unchanged. |
| 2026-03-12 | Returns | 70 → 72 | Frontmatter synced to editorial body. Dimension scores unchanged. |
| 2025-03-06 | Both | N/A | Initial publish. Freedom 45/100, Returns 70/100. |
Team overview
Born in France, raised in LA. Created one of the first CD-ROM games (Hell Cab) at age 18. Founded OTOY Inc. in 2008. Over 25 years in computer graphics. Built OctaneRender, the world's first GPU-accelerated unbiased renderer. Visionary in holographic media and cloud rendering.
@julesurbach on XCo-founded OTOY with Jules Urbach. Technical leadership of OctaneRender development.
| Round | Amount | Date | Lead |
|---|---|---|---|
| Public Sale (ICO) | $1.2M | 2017-10-05 | -- |
| Private Sale | $4.0M | 2018-01 | -- |
| Venture Round (Token) | $30.0M | 2021-12-21 | Multicoin Capital |
Source: OYM Research · Last updated 2026-10-12
Technical snapshot
Render Network is a two-layer architecture. The off-chain layer (proprietary, OTOY-owned) handles all core functionality: OctaneRender GPU rendering engine, node client software, job routing and allocation, multi-tier pricing (Tier 1 trusted partners, Tier 2 high-quality, Tier 3 economy), reputation scoring, and encrypted job payload transport. Supported engines: OctaneRender (primary), Blender Cycles (via RNP-014), Cinema 4D/Redshift. The Dispersed platform (launched December 2025 at Breakpoint) extends into AI compute for inference and training. The on-chain layer (Solana) handles RENDER token burn-mint-transfer via BME, governance voting via Nation.io, and proof-of-render job completion logging. Job workflow: creator uploads project -> files divided into units -> allocated to node operators by pricing tier and reputation -> operators render frames -> proof published -> creator validates -> tokens released from escrow. BME: 95% of payment tokens burned, node operators receive newly minted tokens.
Commit Activity
Community
Audits
Scope: RNDR ERC-20 token and crowdsale contracts (Ethereum). Initial allocation: 25% crowdsale, 65% foundation escrow, 10% founders.
1 low-severity issue found (misuse of FinalizableCrowdsale library). Fixed.
View reportSource: OYM Research · Last updated 2026-10-12
Tokenomics deep dive
Token utility
- Payment for rendering and AI compute jobs (burned via BME on completion)
- Node operator rewards (newly minted via BME emission schedule)
- Governance voting on RNPs via Nation.io
- Access to network compute resources (job submission requires RENDER)
- Bounty platform rewards for developers and artists
Supply
| Max supply | Total supply | Circulating | Circ. % |
|---|---|---|---|
| 644,245,094 | 567,664,271 | 518,743,261 | 80.5% |
Allocation
Method: ICO (October 2017) at $0.25 per token. Private sale (January-May 2018) at $0.25 with bonuses. Venture round ($30M, December 2021) led by Multicoin Capital with Alameda Research, Solana Foundation, others. TGE: October 6, 2020 at listing price $0.0533. Original mint: 536,870,912 RNDR (2^29). OTOY Treasury (23.3%) + Partner Escrows (26.6%) = ~50% of total supply controlled by insiders/Foundation. Not a fair launch.
| Category | % | Vesting | Cliff |
|---|---|---|---|
| Escrow for Partners | 26.6% | Cliff vesting, various tranches | Various |
| OTOY Treasury | 23.3% | Foundation/OTOY controlled | None documented |
| Public & Private Token Sale | 18.29% | ICO unlocked at TGE; private sale with bonuses and schedules | None for ICO |
| Inflation (BME emissions) | 16.67% | Declining annual emissions via governance-approved BME schedule | None |
| RNDR Reserve | 8.61% | Foundation controlled | None documented |
| Escrow for Subsequent Distribution | 6.52% | Foundation controlled, phased release | Various |
Emissions
Vesting timeline
RNP-022 Year 3 emission distribution
Public & Private Token Sale cliff
BME is well-designed in theory but currently net inflationary: monthly emissions (~500K RENDER) outpace monthly burns (~50K RENDER) by ~10x. Burns are growing (279% YoY) but remain an order of magnitude below emissions. The system is designed to become deflationary at scale, but that threshold is not reached. OTOY Treasury (23.3%) + Partner Escrows (26.6%) = ~50% insider-controlled supply. 91% of supply held by ~902 addresses. No native staking means holders cannot earn yield from the protocol directly. The ~82% decline from ATH ($13.59 March 2024 to ~$1.35) reflects both broader market conditions and the inflationary pressure. CoinMarketCap rank #66 -- significantly higher market cap than Akash despite similar utility category.
Source: OYM Research · Last updated 2026-10-12
RENDER Supply Simulator
Scenario Parameters
Circulating Supply Projection
Monthly Emissions vs Burns
Supply projections only. Token price held constant at $2.0100 (snapshot 12 Oct 2026). BME (RNP-001): 95% of RENDER spent on jobs burned. Currently net inflationary. This is not financial advice.
Participation at a glance
Provide GPU computing power for rendering and AI compute jobs. PERMISSIONED: must complete Render Network Interest Form and be approved by Foundation. This is a CRITICAL differentiator from permissionless networks like Akash. Multi-tier pricing: Tier 1 (trusted partners), Tier 2 (high-quality), Tier 3 (economy). Reputation scoring affects job allocation.
Submit rendering or AI compute jobs as a creator/enterprise. Upload projects via OctaneRender, Blender Cycles, or Cinema 4D/Redshift. Jobs priced in USD, paid in RENDER (burned via BME). 50-80% cheaper than centralised cloud rendering. Dispersed platform (Dec 2025) for AI compute workloads.
Vote on Render Network Proposals (RNPs) via Nation.io using RENDER tokens. 4-phase process: Draft > Initial Vote (72h, simple majority, no quorum) > Final Vote (6 days, 50% majority + 15% quorum) > Implementation. Emergency provisions raise quorum to 20%. 22 RNPs submitted to date. Actual active participation is very low: RNP-022 had 2.6M votes for/against out of 93.9M participating tokens (91.3M abstained), meaning ~0.5% of supply actively voted.
Build on the network via Bounty Platform (launched July 2025) or submit RNPs. Bounty rewards paid in RENDER tokens.
Developer resources
Source: OYM Research · Last updated 2026-10-12
Usage and traction
Data from: Render Foundation stats dashboard (stats.renderfoundation.com, server-rendered nodeStats), read 2026-10-07; node count refreshed weekly via src/data/usage-live.json. Earlier context: CoinLaw, Foundation monthly reports. (2026-10-07) . Cards dated separately are live readings (Render Foundation dashboard (self-reported)).
Research note, 2026-10-07: 69.1M total frames rendered is impressive for a GPU marketplace. ~35% of all-time frames rendered in 2025, with monthly throughput of ~1.5M frames. 2025 RENDER burned (Jan-Sep): 530,171 tokens, up 279% from 139,924 in same period 2024 -- shows growing utilisation. Peak network utilisation: 85% during high-demand epochs. GPU marketplace grew 87% YoY per Foundation report. However: 15,931 'node operators' on the dashboard (7 Oct 2026; 15,670 in March) vs 5,600 'since inception' suggests dashboard counts registered rather than active nodes. Actual concurrent active node count unclear. No public revenue figures make it difficult to assess economic sustainability. The network delivers real rendering output (Hollywood, Beeple, enterprise clients) but the proprietary nature means utilisation claims cannot be independently verified.
Source: OYM Research · Last updated 2026-10-12
Community
Governance
Render Network Proposals (RNPs). 4-phase voting on Nation.io (Solana-compatible, migrated from Snapshot). Draft > Initial Vote (72h, simple majority, no quorum) > Final Vote (6 days, 50% majority, 15% quorum of total supply) > Implementation. Emergency provisions raise quorum to 20%. RNPs primarily authored by Foundation, not community. Foundation controls proposal filtering and implementation. No evidence of proposals contradicting Foundation wishes being passed. View →
Sentiment
Community is split between artist/creator users (positive, value the product for rendering) and crypto/DeFi participants (concerned about price decline, insider concentration, limited staking). Hollywood and enterprise partnerships generate genuine excitement. Node operators report inconsistent earnings and low utilisation. Governance participation is very low in active terms. The Dispersed AI compute launch (Dec 2025) is viewed as the key growth catalyst. Community generally respects Jules Urbach's vision but is frustrated by the proprietary nature of the core platform and lack of transparency around node economics.
Source: OYM Research · Last updated 2026-10-12
Sources consulted (32)
Read next
Project review
Akash Network
Independent review of Akash Network: AKT tokenomics, the BME burn, self-reported vs verified revenue, named customers, and the Cosmos migration risk.
Project review
Golem Network
Golem Network review. The original decentralised compute network (2016). Permissionless P2P marketplace, 82% ICO distribution, zero protocol revenue. Freedom Score and honest assessment.
Project review
io.net
Independent io.net review: IO tokenomics, the on-chain IDE burn, revenue below the marketing claims, and why its GPU count overstates the network.