Architecture

Protocol Economy

Utility, compute and closed-loop design. $SYN coordinates access around a product that already meters its own cost in cycles.

This page describes settlement, incentives and supply. It is not a purchase interface. Figures are the current architecture and can be updated independently of the rest of the site.

Hard cap
250,000,000

$SYN

Issuance
Fixed

no core inflation

Settlement
4

Cycles · ICP · $SYN · USDC

Mandate

Why $SYN exists

A coordination asset for a product that already has a unit of compute, a unit of settlement, and a measured cost of running agents.

Product first

The token coordinates access and incentives around autonomous trading intelligence and transparent on-chain telemetry. Utility is a property of the product, not of issuance.

Cycles stay native

Cycles are the compute fuel of the Internet Computer. $SYN complements that unit. It does not replace it, and it does not hide cycle burn.

Closed-loop accrual

Real protocol activity generates treasury inflows. Those inflows can support the network. Perpetual inflationary emissions are not the primary engine.

Access, compute coordination and network authority are functions of using Syntho. They are not a substitute for telemetry, risk limits or cycle runway. If the product is idle, $SYN has nothing to coordinate.

Settlement

Payment architecture

Operators may settle in Cycles, ICP, $SYN or USDC. Every path maps to the same two constraints: what the operator may run, and what the replica must burn.

Cycles

Native compute

Internet Computer fuel

Cycles are what the replica burns to execute canisters. Agent inference, telemetry and orchestration settle in cycles at the protocol layer, regardless of how an operator pays at the product edge.

Maps to Execution · telemetry · orchestration

ICP

Protocol settlement

Native ledger settlement

ICP is accepted as protocol-native settlement and can be converted into cycles for canister operation. It does not replace cycle accounting; it funds it.

Maps to Settlement → cycle conversion → compute runway

$SYN

Coordination

Access and incentive layer

$SYN coordinates who may run which agents, at what allocation limits, and on what compute terms. It complements cycles. It does not pay the replica.

Maps to Access · limits · discount · priority · authority

USDC

External settlement

Stable-value settlement

Accepted so operators can settle access and compute without holding ICP. Converted at the protocol edge into the same access map and cycle provisioning as other assets.

Maps to Settlement → access / cycle provisioning

Mapping

Agent access and allocation limits are product permissions. Compute is cycle burn inside canisters. Settlement assets fund those two surfaces at the edge; they do not rewrite how the Internet Computer meters execution. $SYN can discount or prioritize the edge terms. It cannot replace cycles.

Staged utility

Utility of $SYN

Permissions and terms, applied in order. Each stage is a product control. None of them mint supply.

01

Access

Unlock additional agents and higher allocation limits. Capacity is a product constraint, not an emissions schedule.

Agents · allocation envelope

02

Compute discount

Settlement in $SYN reduces the cycles billed for equivalent compute. The replica still burns cycles; the discount is applied at the product edge.

Cycles cost · product edge

03

Priority

Preferential orchestration and multi-agent slots when capacity is scarce. Ordering is explicit and inspectable, not discretionary.

Orchestration · multi-agent slots

04

Staking & authority

Committed $SYN improves an operator's risk parameters and network authority — wider envelopes only where the mandate and telemetry already support them.

Risk parameters · authority

05

Future governance

A later path for setting strategy-marketplace parameters. Not active in this version. Governance is scoped to product rules, not to monetary policy.

Marketplace parameters · later

Closed loop

Value accrual

Protocol activity → treasury inflows → network support. The loop is inert if the product does not generate real activity.

  1. 01

    Protocol activity

    Agents run. Operators pay for access, allocation and compute in accepted settlement assets. Without this step the rest of the loop does not exist.

  2. 02

    Treasury inflows

    A defined share of settlement lands in the protocol treasury. Inflows are a function of usage, not of new supply.

  3. 03

    Network support

    Treasury provisions cycles, sustains canisters and supports operators. The default path is earned inflow — not perpetual inflationary emissions.

Network support means provisioning cycles, keeping canisters solvent and sustaining operators who are already producing telemetry. It is not a commitment to perpetual issuance. If activity falls, inflows fall with it.

Supply

Supply architecture

250,000,000 $SYN. Fixed cap. Inflationary emissions are not the core mechanism of network support.

Hard cap

250,000,000

$SYN

Core contributor tokens unlock on a 12-month cliff and vest over 36 months. Other buckets are purpose-bound. None of them are an emissions engine.

  • Treasury & Protocol

    40%

    100,000,000 $SYN

    Protocol-owned inventory, cycle provisioning and operating reserves tied to measured network activity.

  • Early Access

    12%

    30,000,000 $SYN

    Operators admitted while the product was in closed access. Aligned to usage of the platform, not to a distribution event.

  • Core Contributors

    18%

    45,000,000 $SYN

    Team and long-horizon builders responsible for the canister stack, research and operations.

    12-month cliff · 36-month vest

  • Ecosystem

    18%

    45,000,000 $SYN

    Integrations, agent-builder programs and protocol tooling, released against delivered work.

  • Reserve

    12%

    30,000,000 $SYN

    Contingency held outside the operating treasury. Not an emissions schedule.

Read the product, then the architecture.

Allocation limits, cycle burn and risk telemetry are already published. This page only describes how settlement and $SYN sit next to that stack.