diff --git a/docs/business/_category_.json b/docs/business/_category_.json index 5b98b5e..0eae509 100644 --- a/docs/business/_category_.json +++ b/docs/business/_category_.json @@ -1,6 +1,6 @@ { "label": "Business", - "position": 1, + "position": 2, "link": { "type": "generated-index", "description": "Documentation for RANDAO's Business" diff --git a/docs/business/customer/_category_.json b/docs/business/customer/_category_.json index 6fb0d91..b0d3617 100644 --- a/docs/business/customer/_category_.json +++ b/docs/business/customer/_category_.json @@ -1,5 +1,5 @@ { - "label": "Customer", + "label": "Customers", "position": 1, "link": { "type": "generated-index", diff --git a/docs/business/customer/start-here.mdx b/docs/business/customer/start-here.mdx deleted file mode 100644 index 03b1da1..0000000 --- a/docs/business/customer/start-here.mdx +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: Start Here -sidebar_position: 1 ---- \ No newline at end of file diff --git a/docs/business/revenue/_category_.json b/docs/business/revenue/_category_.json new file mode 100644 index 0000000..162a770 --- /dev/null +++ b/docs/business/revenue/_category_.json @@ -0,0 +1,8 @@ +{ + "label": "Revenue", + "position": 1, + "link": { + "type": "generated-index", + "description": "Documentation on RANDAO's revenue" + } +} \ No newline at end of file diff --git a/docs/business/revenue/revenue-model-credit.mdx b/docs/business/revenue/revenue-model-credit.mdx new file mode 100644 index 0000000..2fedcb2 --- /dev/null +++ b/docs/business/revenue/revenue-model-credit.mdx @@ -0,0 +1,43 @@ +--- +title: RANDAO Revenue Model - Credit +sidebar_position: 2 +--- +Credit +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. \ No newline at end of file diff --git a/docs/business/revenue/revenue-model-subscription.mdx b/docs/business/revenue/revenue-model-subscription.mdx new file mode 100644 index 0000000..16f8d98 --- /dev/null +++ b/docs/business/revenue/revenue-model-subscription.mdx @@ -0,0 +1,58 @@ +--- +title: RANDAO Revenue Model - Subscription +sidebar_position: 3 +--- +Subscription + +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. diff --git a/docs/business/start-here.mdx b/docs/business/start-here.mdx deleted file mode 100644 index 03b1da1..0000000 --- a/docs/business/start-here.mdx +++ /dev/null @@ -1,4 +0,0 @@ ---- -title: Start Here -sidebar_position: 1 ---- \ No newline at end of file diff --git a/docs/developers/_category_.json b/docs/developers/_category_.json index 4b248e3..be61ed9 100644 --- a/docs/developers/_category_.json +++ b/docs/developers/_category_.json @@ -1,6 +1,6 @@ { "label": "Developers", - "position": 2, + "position": 3, "link": { "type": "generated-index", "description": "Documentation for developers integrating with RANDAO" diff --git a/docs/miners/_category_.json b/docs/miners/_category_.json index 20bbfee..43cc861 100644 --- a/docs/miners/_category_.json +++ b/docs/miners/_category_.json @@ -1,6 +1,6 @@ { "label": "Miners", - "position": 3, + "position": 4, "link": { "type": "generated-index", "description": "Documentation for RANDAO miners and node operators" diff --git a/docs/start-here.mdx b/docs/start-here.mdx index 5c9af1a..8862b37 100644 --- a/docs/start-here.mdx +++ b/docs/start-here.mdx @@ -1,5 +1,5 @@ --- -title: RANDAO Start Here +title: Start Here sidebar_position: 1 --- diff --git a/static/img/docs/business/revenue/credit.gif b/static/img/docs/business/revenue/credit.gif new file mode 100644 index 0000000..7ee8395 Binary files /dev/null and b/static/img/docs/business/revenue/credit.gif differ diff --git a/static/img/docs/business/revenue/subscription.gif b/static/img/docs/business/revenue/subscription.gif new file mode 100644 index 0000000..4ad7f42 Binary files /dev/null and b/static/img/docs/business/revenue/subscription.gif differ