Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/business/_category_.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"label": "Business",
"position": 1,
"position": 2,
"link": {
"type": "generated-index",
"description": "Documentation for RANDAO's Business"
Expand Down
2 changes: 1 addition & 1 deletion docs/business/customer/_category_.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"label": "Customer",
"label": "Customers",
"position": 1,
"link": {
"type": "generated-index",
Expand Down
4 changes: 0 additions & 4 deletions docs/business/customer/start-here.mdx

This file was deleted.

8 changes: 8 additions & 0 deletions docs/business/revenue/_category_.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
{
"label": "Revenue",
"position": 1,
"link": {
"type": "generated-index",
"description": "Documentation on RANDAO's revenue"
}
}
43 changes: 43 additions & 0 deletions docs/business/revenue/revenue-model-credit.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
title: RANDAO Revenue Model - Credit
sidebar_position: 2
---
<img src="/img/docs/business/revenue/credit.gif" alt="Credit" style={{height: '100%', width: 'auto', objectFit: 'contain'}} />
One of the earliest ways we validated demand at RANDAO was straightforward:

DApps pay each time they request verifiable randomness.

It’s similar to cloud pricing:
- Clear usage
- Easy billing
- Immediate value

This model works especially well for:
- GameFi mechanics
- NFT minting events

But like most early infrastructure models, it has tradeoffs:
- Usage can be spiky
- Stickiness depends on integration depth
- Pricing pressure exists as alternatives emerge

That’s okay.

Early models aren’t about perfection.
They’re about learning where value truly concentrates.

## The Bigger Picture: Randomness as Infrastructure

The long-term opportunity isn’t just selling randomness calls.

It’s making **randomness native** to blockchains the same way:
- Compute
- Storage
- And consensus are native today

When randomness becomes infrastructure-level:
- Builders stop reinventing fragile solutions
- Security improves by default
- Entire new design spaces open up

That’s the direction we’re building toward.
58 changes: 58 additions & 0 deletions docs/business/revenue/revenue-model-subscription.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
title: RANDAO Revenue Model - Subscription
sidebar_position: 3
---
<img src="/img/docs/business/revenue/subscription.gif" alt="Subscription" style={{height: '100%', width: 'auto', objectFit: 'contain'}} />

RANDAO subscriptions are designed to make randomness frictionless and ubiquitous.

Early infrastructure made developers pay per use:
- Per oracle call
- Per API request
- Per random number

That works — until it doesn’t.

It creates friction.
It punishes experimentation.
It turns core infrastructure into a tax.

We’re now seeing a shift toward **protocol-funded infrastructure**:
- Chains pay once
- Every app inherits the capability
- Builders focus on products, not plumbing

Randomness is following the same path as:
- Oracles
- Data availability
- Compute

From optional add-on → **native capability**.

## Why This Matters for Executives and Protocol Designers

If you’re designing a Layer 1 or Layer 2, ask yourself:

What should every application on my chain get for free?

If the answer includes:
- Fair games
- Secure mints
- Trust-minimized lotteries
- Reliable simulations

Then **blockchain RNG** isn’t optional.

It’s infrastructure.

And infrastructure decisions compound.

## Where This Is Going

In the next few years, we’ll stop asking:
“How does this dApp get randomness?”

And start asking:
“Why doesn’t this chain provide it by default?”

That’s the moment randomness stops being a feature — and becomes a foundation.
4 changes: 0 additions & 4 deletions docs/business/start-here.mdx

This file was deleted.

2 changes: 1 addition & 1 deletion docs/developers/_category_.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"label": "Developers",
"position": 2,
"position": 3,
"link": {
"type": "generated-index",
"description": "Documentation for developers integrating with RANDAO"
Expand Down
2 changes: 1 addition & 1 deletion docs/miners/_category_.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"label": "Miners",
"position": 3,
"position": 4,
"link": {
"type": "generated-index",
"description": "Documentation for RANDAO miners and node operators"
Expand Down
2 changes: 1 addition & 1 deletion docs/start-here.mdx
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: RANDAO Start Here
title: Start Here
sidebar_position: 1
---

Expand Down
Binary file added static/img/docs/business/revenue/credit.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/img/docs/business/revenue/subscription.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.