Owner-only production canary · Version 0.2.0

Private 25-USDC Canary

Only the bound Owner wallet may provide a fresh ownership proof. The general Public Sale remains disabled.

Coordinator: portal-authenticated-s2

Immutable contract

Exact order

Buyer
5dPGgAZMjdVN1RHsdzw9Y5ueuXqsZNDK5UxmTRpVJQoJ
Payment
25.000000 USDC
Delivery
3,787.878787 LUMA immediately after final payment confirmation
Delivery hold
0 hours · the legacy 336-hour delay does not apply
Format
Legacy · one signer · no ALT
Instructions
Limit → price → TransferChecked → memo
Compute limit
40,000 · 02409c0000
Compute price
1,000 µLamports/CU · 03e803000000000000
USDC bytes
0c40787d010000000006
Maximum network fee
5,040 lamports
No v0 / ALTNo second signerNo extra instructionNo manual transfer
Signing remains disabled. Wallet connection and local Terms review are available. Payment and signing are paused until the bounded delivery worker is ready. Do not make a manual transfer.
  1. 1

    Connect Phantom

    Only the fully displayed wallet above is accepted.

    No wallet connected.

  2. 2

    Review and accept the exact checkout

    The domain-separated message proves wallet control and binds the exact Terms and every separate declaration. It is not a transaction and moves no funds.

    Terms version–
    Content-addressed URI–
    Terms SHA-256–
    Exact UTF-8 length–
    No verified Terms bytes available yet.

    The browser does not fetch the URI. It verifies the compiled UTF-8 bytes, length and SHA-256 locally before any acceptance control is enabled.

    Read the Terms before connecting. Each wallet message is valid for five minutes. If it expires, reconnect and select the statements again; no expired selection can be submitted.

    Connect the bound wallet to select the statements. Selections are local only; nothing is submitted until you personally sign the wallet proof.

    Waiting for the bound wallet.

  3. 3

    Verify the exact payment bytes

    The helper parses the legacy message locally. Accounts, permissions, instruction order, data bytes, memo and both SHA-256 values must match exactly.

    Message SHA-256–
    Unsigned SHA-256–
    Server memo–
    Destination USDC account–
    Network fee / maximum–
    Fee evidence SHA-256–
    Payment expiry–
    Preparation expiry–

    No preparation exists.

  4. 4

    Sign exactly once

    The complete message bytes are compared again immediately before and after Phantom. Any mismatch is rejected locally before the Coordinator receives anything.

    A durable pre-sign intent is written immediately before Phantom. If the outcome becomes unknown, the canary remains locked for manual review and no second signature is requested.

    Signing is disabled until the matching release digest is pinned.

  5. 5

    Finality and immediate delivery

    A local completion record is created only after finalized payment, immediate LUMA delivery, finalized delivery and Coordinator state FULFILLED.

    Not submitted.