Slide - Demand Side Token Design

Demand Side Token Design Rules[1]

1: Marp via Obsidian


Demand vs Supply

Which matters more to the success of a company?

Demand or Supply?

What has greater impact on value of stock?

Market expects greater demand or greater supply?

If this is the case, why do most token-based protocols build out supply?


Build it and they will come fallacy


What Generates Demand?

This is the Number 1 question for companies, not just protocols. So many approaches, but it's the secret to very successful companies (if you know, please see me privately to let me know)

But these are true for regular companies, not just protocols. Protocols need to leverage inherent advantages.


Why a blockchain-based protocol?


What characteristics of the service are only possible with blockchains?

New Product Features (e.g. Quality of Service)

Token-driven network services like IoT (Helium) or XNET enabled a product that solves network access as scale. Solves for end-users and, in some cases, network operators.

Token-driven supply addresses topology and CapEx constraints.

Immutability of Data or Quantity

The service needs a form of immutability of associated data or quantity around an asset.

Trust Minimization

The product or service delivers a service or product which doesn't introduce counter-party risk because of trust minimization.


The solution draws from traditional Product Management + blockchain characteristics


Can Token Design Incentivize Demand?

This becomes a very interesting design space!

Note: incentives are always secondary to product market fit


Incentives Design Space

Understanding Personas Matters


Cautionary Tales


Summary