α · AGIALPHA

α-AGI MARK · Ethereum Mainnet · chain ID 1

Your plan. Your wallet. Explicit control.

Inspect the deployed contracts, prepare an exact action, then approve it in your own wallet. This workspace can send real Ethereum transactions. It is not the local demonstration.

Explore without a wallet →

Deployment and authorization

Only build-qualified profiles and the immutable archive are selectable. Imported files and URLs cannot change their policy. Outstanding journals remain bound to their original profile.

1 · Choose your wallet

No private key, seed phrase or API key is requested. Use an injected browser wallet or a wallet’s built-in browser. Hardware signing stays in your wallet. Inspection does not request access to accounts.

No connected account / Aucun compte connecté

A page disconnect does not revoke the wallet extension’s permissions. Revoke those in the wallet. Never use an AI agent to approve wallet prompts for you.

Loading the pinned deployment profile… / Chargement du profil…

2 · Inspect real on-chain state

Nothing has been read from Mainnet yet. A provider outage is unknown, never an empty campaign or a successful check.

Observed values and evidence
—

3 · Understand a funding quote

Inspect a seed first. Quotes use the observed campaign, exact 18-decimal arithmetic and the on-chain quote function. Lots are campaign funding units—not company shares, a dividend entitlement or a promise of profit.

—

4 · Prepare one exact action

Advanced fields map to the deployed contract, not to an upgrade. Timestamps are Unix seconds; durations are seconds. Token fields use readable $AGIALPHA amounts. FusionPlan JSON uses integer base units for bounty. Read the guide before your first action.

6 · Verify the receipt

A submitted hash is not payment success. Refresh to check the actual transaction, receipt, canonical block and finality. Pending, replaced, reverted and unknown states must be reconciled before retrying. This browser automatically saves public transaction intents before signing. Export a backup before clearing browser data. A restored or replacement hash must be checked on-chain; imported records never authorize signing.

Only a finalized transaction using the recorded sender and nonce resolves an uncertain submission. A cancellation or different replacement is never reported as successful execution. Browser storage and this lock cover this origin and browser profile only; other devices and wallet apps require coordination.

—