Diligence

Token design & economics

Current $STEER supply design, allocation, demand primitives, governance scope, and investor diligence boundaries

Current design

$STEER is designed as the control-plane asset for participant rights, economic accountability, runtime usage, and governance across Steer’s shared infrastructure. Enterprise customers can continue to contract and pay in stablecoins; token requirements apply to defined platform roles and activity.

Maximum supply
1.0B
Fixed design cap
Community allocation
62%
Distribution, ecosystem, incentives, treasury, and liquidity
Modeled launch float
14.4%
Excludes dedicated liquidity allocation
Demand model
3 primitives
Rights, bonds, and credits

This is the current economic design carried forward from Steer’s prior token materials. Final launch timing, legal treatment, program mechanics, and definitive vesting ledger remain subject to approved launch documents.

The current financing is structured as a SAFE with an accompanying token warrant. The warrant and its investor rights are controlled financing materials; they should not be inferred from the supply-design tables on this page.

Supply and allocation

AllocationShareIntended role
Community62%Public distribution, ecosystem programs, incentives, treasury, and liquidity
Team20%Current and future contributors, subject to vesting
Investors17%Pre-seed and seed / strategic participants, subject to vesting
Advisors1%Specialist support, subject to vesting
Total100%1,000,000,000 $STEER

The 62% community allocation is currently designed as follows:

Community programShare of total supplyIntended use
Public pool auction6.2%Public distribution and launch price discovery
Ecosystem22.8%Grants, ecosystem programs, and operator incentives
Incentives / points5.0%Product- and partner-aligned incentives
Treasury16.0%Audits, contingencies, and strategic initiatives
Liquidity12.0%Exchange liquidity and market-depth programs

The modeled contributor and investor structure uses a 12-month cliff followed by 36 months of vesting. The modeled initial float is 14.4% excluding dedicated liquidity, or 16.8% including it. Exact dates and daily emission amounts should be read from the final token-generation and vesting documents, not inferred from this summary.

Demand: rights, bonds, and credits

$STEER demand = locked rights + locked bonds + consumed credits.

PrimitiveWhat it doesActivity driver
RightsStake to qualify for roles, registries, or reserved capacityGoverned assets, operator count, and capacity utilization
BondsBack templates, mandates, listings, or service commitmentsProduct launches, service levels, and product lifetime
CreditsMeter policy evaluation and offchain executionTransaction frequency, policy intensity, and compute load

Token requirements are intended to attach to role qualification, capacity reservation, service accountability, and measured infrastructure use rather than to customer billing.

SubsystemToken touchpointActivity driver
Issuance StudioListing or activation bonds and capacity rights for product templates and mandatesTemplate throughput, product launches, and capacity-limited sleeves
Structured product controlsRisk-budget stake, exception bonds, and approved registry maintenanceRisk-program complexity, exception cadence, and curator or operator participation
Matador runtimeGoverned-notional stake and credits for policy evaluationManaged assets, transaction frequency, and policy intensity
Offchain computeOperator or delegator stake, service-level bonds, and routing creditsExecution load, uptime targets, automation depth, and operator capacity

The intended loop is that adoption increases locked rights, locked bonds, and consumed credits; those mechanics support operator capacity, reliability budgets, and ecosystem programs; stronger reliability can then support additional product adoption.

This structure ties token demand to observable platform activity. Stake thresholds, bond sizes, penalty conditions, credit pricing, and burn or routing treatment are launch parameters—not promises embedded in this page.

Governance boundary

Governance is intended to control shared platform rules:

  • registries, admission standards, and disclosure requirements;
  • risk bands, concentration limits, and exception pathways;
  • stake thresholds, credit pricing, capacity, and service tiers;
  • evidence standards for penalties and emergency controls; and
  • treasury-directed routing where activated by final launch policy.

$STEER does not represent company equity or a claim on product profit and loss, mandate cash flows, protocol revenue, or Steer’s operating cash flows.

This page describes mechanism design, not a legal characterization or offer. Product-by-product and jurisdictional legal analysis is available through Corporate & legal diligence.

Back to Documents →