[0_0] GH0ST

EXPERIMENT 002 / AUTHENTICATED CALLDATA

Qwen.
Public computation.

Qwen3-0.6B, quantized to 4 bits. Weights published in Robinhood transaction calldata. Every inference step executes in contracts against authenticated weight witnesses.

Loading release…28 layers · 64-token context · greedy decoding
WEIGHT PUBLICATION GAS—
CONFIRMED PUBLICATION FEES—
MODEL PAYLOAD307.58 MB
THE COST OF A RESPONSE

The complete local inference benchmark is pending. Funding is disabled until validation and controller deployment are confirmed.

Publication gas and inference gas are separate. This is an experimental research interface. A chat can require a large refundable deposit, extensive calldata and many transactions. The quote below is a maximum budget; future network fees cannot be known exactly in advance.

01 / REQUESTYou fund the computation
Execution settings

Only this address can advance the session. It pays transaction gas and receives capped reimbursement from escrow. Leave your wallet selected to execute here.

REFUNDABLE MAXIMUM DEPOSIT—

The contract calculates the bounded work and escrow requirement.

No inference starts automatically. Fee caps are fixed for the session. If market fees exceed them, execution pauses until fees fall or you cancel.

02 / EXECUTION
CONFIRMED RESPONSE

The model’s output will appear here as tokens are confirmed onchain.

No session loaded.

Small compatible steps are batched, up to eight per transaction. This wallet-driven queue asks for each transaction’s approval; it does not grant automatic signing access. Keep the page open while running.

Wallet balance
—
Escrow remaining
—
Executor reimbursement credited
—
Your withdrawable credit
—
Executor recovery

Active executor: —. The requester can assign another address. This does not alter fee caps.

Loading pinned model assets…
TRANSACTION JOURNALOnly receipt-confirmed progress is shown
    Interrupted wallet submission

    If submission was interrupted before a hash was returned, copy the transaction hash from your wallet. The page verifies its sender, nonce and contents before reconciliation. It never resubmits automatically.

    Published weights.
    Verified witnesses.

    Transaction history supplies the weight bytes. Your browser retrieves the relevant publication transactions, checks their Merkle proofs, and resubmits the required chunks to the contracts. Tokenization and proof assembly happen locally; model computation happens onchain.

    Historical calldata needs an accessible archive RPC. Cached witnesses reduce repeat downloads, but the calldata is still submitted for each execution step.

    Inspect the contracts.

    Weight registry
    —
    Matrix kernel
    —
    Inference controller
    —

    Requester escrow uses a disclosed, capped reimbursement formula. It is not an exact prediction of the final receipt fee. The requester can cancel and withdraw unused escrow; the executor can withdraw earned credits.