Genesis

Founding participation in ASHER

Two published Genesis rounds offer 8.5% of the 1,000,000,000 ASHER maximum supply. Every figure on this page is derived from the published round parameters — the allocation arithmetic comes from each round's cap ratio, so a fully subscribed round lands on its cap to the token.

The rounds

Genesis I

Pending
USDC target
$1,000,000
ASHER offered
50,000,000 ASHER
Share of max supply
5%
Price per ASHER
$0.02

Exact.

Implied FDV
$20,000,000

This round's price applied to the 1,000,000,000 ASHER max supply. A valuation implied by the round, not a market price — ASHER has not been issued and does not trade.

Minimum contribution
TBD
Maximum contribution
TBD
Worked example
$100,000 = 5,000,000 ASHER

Exact, at 50 ASHER per 1 USDC. The equals sign is not a rounding: the allocation is derived from the round's cap ratio, so it is exact even for Genesis II, whose per-token decimal price is not.

Genesis II

Pending
USDC target
$1,000,000
ASHER offered
35,000,000 ASHER
Share of max supply
3.5%
Price per ASHER
≈$0.0285714Approximate

Approximate. The exact price is 35 ASHER per 1 USDC — as a per-token decimal it does not terminate, so the figure above is rounded for display only.

Implied FDV
≈$28,571,428

This round's price applied to the 1,000,000,000 ASHER max supply. A valuation implied by the round, not a market price — ASHER has not been issued and does not trade.

Minimum contribution
TBD
Maximum contribution
TBD
Worked example
$100,000 = 3,500,000 ASHER

Exact, at 35 ASHER per 1 USDC. The equals sign is not a rounding: the allocation is derived from the round's cap ratio, so it is exact even for Genesis II, whose per-token decimal price is not.

Later roundsThe platform supports additional configurable Genesis rounds. None has been supplied or approved, so none is published, none can be activated, and there is no date, size or price for one to state.

Vesting

10% of a Genesis allocation is available at the token generation event, and the remaining 90% vests over 24 months.

Working parameter — not a final termThis vesting treatment is the current working assumption, pending final token and legal documentation. It is not settled, it may change before any contract is deployed, and it must not be read as a committed schedule. No token generation event has been scheduled.

Contribution flow

  1. Connect wallet

    Now

    Checking for a wallet in this browser…

  2. Verify network

    Now

    Checking the network…

  3. Eligibility and compliance

    Not required

    No eligibility or compliance check is enabled for this round, so none is requested and no personal information is collected.

    If a check is required for a future round it will appear here as its own step before any contribution can be made.

  4. Select Genesis round

    Now
    Choose a Genesis round

    No Genesis round is open. You can select a round below to review its terms and see the exact allocation for an amount — selecting it does not reserve an allocation and does not create any obligation.

    Later roundsThe architecture supports additional configurable rounds. None has been supplied or approved, so none is published here. There is no date, size or price for a later round to state.

  5. Enter USDC contribution

    Waiting

  6. Exact ASHER allocation

    Waiting

  7. Price

    Waiting

  8. Vesting

    Waiting

  9. Terms and risk acknowledgment

    Waiting

  10. Approve USDC

    Unavailable

    USDC is an ERC-20 token, so the sale contract must be approved to move the amount you are contributing before the contribution itself can be sent. Approval is a separate transaction and does not transfer anything on its own.

    Amount to approve
    —
    Spender
    Genesis sale contract — not yet deployed

    Approval is disabledContributions are closed. The Genesis contracts have not been supplied, audited, deployed or approved, so there is nothing to approve USDC for and nothing to send a transaction to. This is not a temporary outage — the control is disabled deliberately and the request is refused again in the handler and at the contract boundary.

  11. Submit contribution

    Unavailable

    Submitting sends the contribution transaction to the Genesis sale contract. The contract recomputes the allocation from the round's cap ratio and enforces the round caps itself — the figures below are what this browser expects it to return, not a promise of what it will.

    Round
    —
    Contribution
    —
    Expected allocation
    —

    Submission is disabledContributions are closed. The Genesis contracts have not been supplied, audited, deployed or approved, so there is nothing to approve USDC for and nothing to send a transaction to. This is not a temporary outage — the control is disabled deliberately and the request is refused again in the handler and at the contract boundary.

  12. Confirm on-chain transaction

    Unavailable

    Once a contribution transaction is sent, its confirmation is tracked here: the transaction hash, the block it lands in, and a link to a block explorer for the configured chain. No transaction exists yet.

  13. Record and index transaction

    Unavailable

    A confirmed contribution is indexed against the participant record — wallet address, round, contribution, allocation, effective price, transaction hash, block number and status — and the participant dashboard reads from that record. The record is written by the backend from the on-chain event, not from anything this browser sends.

    Nothing to record. Contributions are closed.

  14. Update participant dashboard

    Unavailable

    Your participant dashboard reads from the indexed record: round, contribution, allocation, effective price, vesting position, Genesis credential and transaction history.

    Open the participant dashboard

What is authoritative, and what is notEvery figure in steps 5 to 8 is computed in your browser from the published round parameters, so that you can check it. The binding allocation, the round cap and the vesting position are whatever the approved contract and the backend record. Where the two ever disagree, the browser is wrong.