Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.burst.trade/llms.txt

Use this file to discover all available pages before exploring further.

​
Utility framework

What utility should do

$BURST utility should connect directly to platform usage and platform performance.The strongest model reinforces actions users already value on Burst.

What utility should avoid

Forced friction weakens reach.Utility should not make core product access harder than it needs to be.
The better model is utility tied to real activity, real incentives, and real platform outcomes.

​
Core utility principles

Low-friction access

Core platform usage should stay open.Utility should add value without becoming a gate.

Platform alignment

Utility should track real product performance.If Burst grows, utility should become more relevant.

Meaningful incentives

Utility should improve behavior, not just speculation.The goal is better participation.

Stronger coordination

Utility should improve alignment across users, creators, and the wider ecosystem.

​
Utility paths

​
Rewards

$BURST can support reward systems tied to meaningful activity on the platform rather than passive holding alone. That can include:
  • user incentives,
  • participation campaigns,
  • ecosystem rewards,
  • and other systems that increase repeat usage.
The goal is simple. Reward behavior that helps Burst grow.

​
Access

Utility can also support access, coordination, and deeper participation. That may include features, programs, or experiences where token involvement improves alignment between the protocol and its most active users. Any access-based utility should create clear value without turning Burst into a gated system.

​
Design constraint

Requiring users to buy, hold, or stake a token just to use the product can reduce reach and limit adoption. That is why Burst utility should stay close to activity, retention, and ecosystem growth.

​
Utility test

If it does not improve real user behavior, it is weak utility.
If it does not increase stickiness, it is not durable.
If it does not improve alignment across the platform, it is not meaningful enough.

​
Bottom line

$BURST utility should be built around actions that matter inside Burst itself.