ASHER.

01

The stack

Each layer depends on the one above it. The data layer comes first because everything else is a consumer of it — an indicator, a backtest and an order are all claims about a series, and they are only as good as that series.

1. DataLIVE

   AsherCore

   Market data and information infrastructure.

   Normalized market data across crypto, equities and foreign exchange, served from its own store with streaming, news and market intelligence on the same contract.

2. IntelligenceLIVE

   AsherLabs

   Trading intelligence, charting, strategy and automation.

   Charting, indicators, AsherScript, strategy construction, backtesting, automation, creator tooling and AI-assisted trading workflows, built on the normalized series AsherCore provides.

3. ExecutionLIVE

   Hyperliquid

   Initial connected execution infrastructure.

   The venue AsherLabs reaches today. Execution is connected rather than internalized: the account is the user’s, at the venue, and the workflow is what reaches it.

4. Execution — futureFUTURE

   Asher Protocol

   Future native and decentralized execution and protocol infrastructure.

   A direction, not a deployment. Where it becomes technically mature, economically sensible and legally appropriate, the ecosystem may introduce deeper proprietary or decentralized infrastructure under this name. None of it exists today.

5. OperationsLIVE

   AsherSupport

   Support, knowledge, scheduling and operational infrastructure.

   Ticketing across email, a branded portal and an embeddable widget into one queue, a knowledge surface, and scheduling with availability rules and booking — operating across the ecosystem rather than beneath one product.

6. EconomyNOT DEPLOYED

   ASHER

   The economic and coordination layer.

   The layer that connects participants, creators, users and future protocol functions. ASHER is not a sixth product; it is how the ecosystem coordinates access, incentives and participation across the products that exist.

AsherSupport operates across the ecosystem rather than beneath one product, and ASHER is the economic and coordination layer connecting participants, creators, users and future protocol functions — not a sixth product.

02

AsherCore — market data and information infrastructure

One normalized API across crypto, equities and foreign exchange, served from AsherCore's own store rather than by proxying a venue on every request. Normalization happens once, at the bottom, so that everything above it can assume one shape.

Normalized multi-asset data

Crypto, equities and foreign exchange returned in one shape, from one API. An indicator written once measures the same thing on every asset class, because normalization happens at the data layer rather than in each consumer.

Candles and historical data

Historical series across intraday and higher timeframes with cursor pagination, so a backtest and a chart read the same bars rather than two approximations of them.

Live prices and quotes

Current prices and mid quotes across the instrument catalog, for pricing a position, a watchlist or a screen.

Streaming

Prices pushed over a stream rather than polled, so a client is told when something changed instead of asking repeatedly whether it has.

Funding data

Funding rates for perpetual instruments, including comparison across venues — the carrying cost of a position, which a spot series cannot express.

Order books

Depth for an instrument: what size rests where, rather than a single last-traded print.

Screeners

Filtering across the instrument catalog, so a universe can be narrowed by criteria instead of inspected one symbol at a time.

Market information

The instrument catalog, venue coverage and market-hours information that tell a consumer what exists, where it trades and whether that market is open.

Asher Wire

Original briefs with source attribution preserved, carrying a machine-readable bias score per story, with a net signal per asset and the story count behind it. Coverage, expressed as data — not a recommendation to trade.

News and signals

Per-symbol news tone derived from that scored coverage, readable both as a human feed and as a value a strategy can consume.

Economic calendar

Scheduled releases with impact rating, forecast, previous and actual — the events that move a market, available before they do.

03

AsherLabs — the intelligence layer

Where a market is read, an idea becomes an explicit strategy, and that strategy can be tested, automated, published and monetized — on the normalized series AsherCore provides.

Advanced charting

A working chart surface rather than a screenshot: crypto, equities and FX on the same canvas, because they arrive from the data layer in the same shape.

AsherScript

The scripting layer for expressing indicators and strategy logic explicitly — rules you can read back months later instead of a decision you remember making.

Indicators

Analysis applied to the normalized series, so a measure computed on one asset class means the same thing on another.

Strategies and backtesting

Turning an idea into stated rules, conditions and parameters, and testing them against the same historical bars the chart draws.

AI-assisted workflows

Assistance inside the workflow — shaping an idea, explaining what a strategy does, surfacing what changed. Assistance to the person doing the work, not an oracle.

Strategy automation

Armed strategies that run on their own and act when their conditions are met, under the permission model described in the execution section.

Creator tooling

The surface for building indicators, strategies and trading systems intended for other people to use, rather than only for their author.

Creator publishing and monetization

Publishing that work into the ecosystem and earning from it. The architecture for distribution and monetization is part of the product design; specific commercial terms are set out where they are configured, not asserted here.

How much you do yourself

Three levels of involvement over the same account and the same venue. They differ in who decides and who presses the button — not in who holds the money.

• Terminal

  LIVE

  Full charting, backtesting and AsherScript. You make the calls and you place the orders.

• Copilot

  BETA

  You choose a strategy and a risk level; the position is managed for you while the decision to run it stays yours.

• Autopilot

  BETA

  You set a goal and a risk level, and armed strategies open and close positions on your own account. Hands-off by design.

Copilot and Autopilot are beta. They are labelled by verified status rather than by ambition, and they stay beta until a production surface and a populated catalog are both confirmed.

04

Execution architecture

What exists today, what may follow, and what is only a direction. The distinction is the point of this section.

1. Phase 1 · TodayLIVE

   Connected execution through Hyperliquid

   AsherLabs connects to Hyperliquid for execution. The user’s funds remain in the user’s own account at the venue. Nothing is deposited into an Asher-controlled account, and there is no managed account, no copy-trading, no vault and no performance carry.

2. Later phases · ProgressivePLANNED

   Deeper infrastructure

   The ecosystem may progressively introduce deeper proprietary and/or decentralized infrastructure — additional venues, additional routing, and more of the path owned rather than connected. Each step is a separate decision, taken on its own merits.

3. Future · DirectionFUTURE

   Asher Protocol

   Asher Protocol may provide native execution and protocol capabilities where that is technically mature, economically sensible and legally appropriate. It does not exist today, no part of it is deployed, and nothing in this document should be read as a commitment to build or ship it on any timeline.

05

AsherSupport — operational infrastructure

Support, knowledge, scheduling and operational infrastructure across the ecosystem.

Three intake channels — email, a branded portal and an embeddable widget — landing in one queue with the source tagged, a knowledge surface, and a scheduler built into the desk with event types, availability rules, buffers, minimum notice and a booking page. AsherSupport is infrastructure the ecosystem runs on rather than a feature of one product.

06

The creator economy

A loop, not a listing. Creators build on the same data every participant sees, publish into the ecosystem, and earn from work other people choose to use.

1. 1

   Create

   Build an indicator, a strategy or a complete trading system in AsherLabs, on the same normalized data every other participant sees.

2. 2

   Publish

   Make that work available to other participants through the ecosystem rather than through a screenshot and a direct message.

3. 3

   Monetize

   Earn from work that other people choose to use. The distribution and monetization architecture is part of the product design; terms are set where they are configured.

4. 4

   Grow

   Build an audience around work that can be inspected and evaluated, rather than around claims about it.

5. 5

   Automate

   Allow users who choose to do so to run that work under automation, within the permission model described above.

This document states no creator count, no revenue figure, no strategy performance and no adoption number. None has been measured, and an unmeasured number is worse than none because nobody reading it can correct it.

07

ASHER — the economic and coordination layer

What the token coordinates, and — just as importantly — what it is not.

ASHER is intended as the economic and coordination layer connecting participants, creators, users and future protocol functions. Every function below is a potential utility of that layer. None of them is live today: there is no deployed token contract, no staking, no treasury mechanism and no governance process.

Ecosystem access and tiering

Access to ecosystem capabilities and tiers of that access.

Trader benefits

Benefits available to participants who use the products to trade.

Creator benefits

Benefits available to participants who build and publish work.

Strategy and marketplace benefits

Benefits attaching to strategy distribution and the marketplace surface.

Staking or locking

Mechanisms by which participants may commit tokens for a period, where such mechanisms are introduced.

Incentives

Programs that direct incentives toward the activity the ecosystem wants to encourage.

Governance

Participation in decisions placed within the scope of token-holder input, where such scope is defined.

Future protocol functions

Functions that a future protocol layer may introduce, if and when one exists.

08

Supply and allocation

Maximum supply and the nine allocation buckets. These figures are rendered from the same configuration the application reads, so this table cannot drift from it.

Maximum supply is 1,000,000,000 ASHER.

The buckets sum to exactly maximum supply and to exactly 100%. That is asserted by a test rather than checked by eye.

09

Genesis

Two configured rounds. Contributions are not open — see section 11.

Later rounds

Later Strategic Rounds holds 45,000,000 ASHER (4.5%). Pricing, dates, minimums, maximums and terms for those rounds are TBD and configurable. None has been supplied, and none is stated here.

10

Vesting

A working structure, and explicitly not yet committed terms.

The current working architecture is 10% at TGE, with the remaining 90% released over 24 months.

11

The Genesis credential

A non-transferable founding-participant credential.

Genesis participants receive a credential marking them as founding participants. It is non-transferable. It may carry recognition and potential non-financial ecosystem benefits, which may include:

• Early product access
• Private previews
• Creator beta access
• Community status
• Priority ecosystem opportunities

12

Current Genesis status

The state of the system as this document is served, read from the same configuration the application enforces.

13

Contribution architecture

The intended production flow, described conceptually. This is the architecture, not a statement that it is currently enabled.

1. 1

   The participant reviews the terms, the eligibility requirements and the risk disclosures.

2. 2

   The participant connects a supported wallet.

3. 3

   The application verifies the network, account and eligibility requirements that apply.

4. 4

   The participant selects a contribution amount.

5. 5

   The exact ASHER allocation and the applicable terms are shown before anything is committed.

6. 6

   The participant acknowledges the applicable terms.

7. 7

   The transaction is processed through approved, deployed contracts.

8. 8

   Contribution, allocation, vesting and claim information becomes available in the participant dashboard.

Steps seven and eight depend on approved, deployed contracts, which do not exist yet. Until they do, this flow describes intended production architecture and nothing more.

14

Security

Commitments and controls. Where something has not happened, this section says so rather than implying it has.

Seed phrases are never requested or stored

No part of this ecosystem will ever ask for a seed phrase or a private key, and no part of it stores one. Any message that does is not from us.

Narrowly scoped wallet permissions

Permissions granted to the application are scoped to what the function requires and no more. Trading authority and withdrawal authority are separate, and the former does not confer the latter.

Audited contracts before public contributions

Contracts are to be independently reviewed before they are used to accept public contributions. No audit has been performed yet, and no audit firm has been engaged or named. When one has, it will be stated here with its scope and its date.

Separation of production keys

Production signing material is held separately from development and test material, and is not shared across environments.

Multisignature and timelocked treasury controls

Treasury and privileged functions are intended to sit behind multisignature control and, where appropriate, timelocks — so that a single compromised key cannot move assets and a privileged change is visible before it takes effect.

Independent security review

Review by parties who did not build the thing being reviewed, as a standing practice rather than a one-time event.

Incident response

A defined path for handling a security incident, including how it is contained, who is told and when.

Authenticated publication of contract addresses

Official contract addresses will be published through authenticated official channels when they exist. Until then there are none, and any address presented as an ASHER contract today is fraudulent.

No audit has been performed and no audit firm has been engaged or named. See the security page for what is and is not claimed about this ecosystem.

15

Risk and disclosure

Factual and jurisdiction-neutral. This document makes no claim about how ASHER is characterized under any regulatory regime.

Nothing here is investment advice

This document describes an ecosystem and a token design. It is not advice, not an offer, and not a solicitation. It does not take account of any individual’s circumstances.

No regulatory characterization is claimed

Nothing in this document asserts that ASHER is or is not a security, a virtual asset, a commodity, or any other regulated instrument in any jurisdiction, nor that it falls outside any regulatory regime. Characterization depends on jurisdiction and on facts that may change, and it is not ours to declare. Participants are responsible for their own position, including obtaining their own advice.

Trading carries risk of loss

Trading, and leveraged trading in particular, can result in the loss of the capital committed to it. Automation does not remove that risk; it changes who presses the button, not what the market does.

No performance claims

This document states no past performance, no projected performance, no return, and no valuation of ASHER. Where a figure is not known it is marked as not supplied rather than estimated.

Working parameters may change

Parameters marked as working — vesting among them — are current design intent, not committed terms, and may change until they are approved and, where applicable, encoded in audited contracts.

Forward-looking statements

Statements about what the ecosystem may do, including Asher Protocol and every token function described as potential, are forward looking. They are not commitments, they carry no timeline, and they may not happen.