+
+
+
+ ◎
+
+
+ Prime mainnet
+ AGIJobManager Prime · Mainnet Console v45
+
+
+
+
+
+
+
+
+
+
+ Wallet: Not connected
+ Network: Connect wallet to detect network
+
+
+
+
+
+ WalletNot connected
+ NetworkConnect wallet to detect network
+ TermsPending
+ AgentUnverified
+ ValidatorUnverified
+ WriteLocked
+
+
+
+
+
+
+
+
+
+ Prime access deck
+ Prime mainnet readiness, pricing, and verification.
+ Keep wallet posture, Before You Transact, terms acceptance, ENS verification, and the Alpha-Agent quick start inside the first operating screen. Verified defaults appear first; live reads confirm public bindings where available.
+
+ Verified default
+ Live read when available
+ Event-derived board
+ Pause-aware timing
+
+ Session continuity restores local drafts, Alpha labels, verification inputs, terms posture, notes, watchlist entries, procurement commit salts, score-commit salts, and modal context on return. Same-account same-chain returns refresh gently instead of wiping setup.
+
+
+
+ Prime deployment registry
Verified defaults
+
+ Settlement kernel (verified default)
+ 0xF8fc6572098DDcAc4560E17cA4A683DF30ea993eAGIJobManagerPrime
Discovery layer (verified default)
+ 0xd5EF1dde7Ac60488f697ff2A7967a52172A78F29AGIJobDiscoveryPrime
Completion receipt NFT
+ 0xFfCC54dA2Caf1158e57611005965BB648E950737AGIJobCompletionNFT
ENS job pages authority
+ 0x703011EF1C6E4277587eFe150e6cd74cA18F0069ENSJobPages (active)
Superseded ENSJobPages (event/reference): 0x97E03F7BFAC116E558A25C8f09aEf09108a2779d
+
+ UriUtils
+ 0xF1b8E6e39F8b4Dd88ADDbb031489c330778db0D1BondMath
+ 0x5Cb69F0F7F7a840A18177d3Dda137979cD376FB2ReputationMath
+ 0x0B96194b807Ae0A9eD5dD1EC0A7beFF5FA5B1443ENSOwnership
+ 0xbB495F0D73d93782D51b977Be1EAfF3F8Dfca19B
+ discoveryModule(): live getter available · refresh to verify
+ completionNFT(): live getter available · refresh to verify
+ Discovery ownership acceptance may still require final owner wallet
+
+
+
+
+
+
+ Prime architecture
Flagship mainnet cutover
+
+ 1 · Settlement kernel (verified default)
+ Escrow, bonds, checkpointing, validation, disputes, settlement, solvency, and pause-adjusted timing via
AGIJobManagerPrime.2 · Discovery layer (verified default)
+ Commit/reveal applications, shortlist, finalists, trial submissions, validator score commit/reveal, winner designation, fallback promotion, and claimable balances via
AGIJobDiscoveryPrime.3 · Public memory
+ Dedicated completion receipt NFTs via
AGIJobCompletionNFT and ENS page posture via ENSJobPages. Compatibility claims stay conservative when not publicly provable.
+
+
+
+
+
+
+
+
+
+
+ Mission Control
+ Connect wallet
+ Connect your Ethereum mainnet wallet to unlock live protocol state, role verification, job posting, validation, and settlement flows.
+ Write access locked
+
+
+
+
+
+
+
+
+
+ WalletNot connected
+ NetworkConnect wallet to detect network
+ TermsPending
+ Agent ENSUnverified
+ Validator ENSUnverified
+ Write accessLocked
+
+
+ Live Snapshot
+ Protocol Pulse
+ A cleaner high-level view of the live job board, your watchlist, and where attention is currently needed.
+
+
+ Open jobs0
+ Assigned0
+ In review0
+ Disputed0
+ Terminal0
+ Watchlist0
+ No jobs loaded yet.
+
+
+
+
+
+
+
+
+ Complete these first
+ Wallet posture, terms, cautions, and verification now live in one preflight band.
+ This keeps wallet connect, Before You Transact, the shared terms gate, early agent / validator verification, and the Alpha-Agent quick start in one calm operating lane before critical writes.
+
+
+
+ Wallet + mainnetConnect walletLive wallet and network posture appears here.
+ Terms + cautionsAcceptance pendingReview the caution summary and confirm terms before any write.
+ Role verificationVerify ENS roleAgent and club posture stays grouped for one-pass setup.
+ Next actionOpen the readiness laneThis highlights the calmest next step without changing write semantics.
+
+
+ 1 · Connect + refreshKeep wallet and network posture visible before you review or sign anything.
+ 2 · Accept termsTerms remain the canonical write gate and are mirrored here near the top.
+ 3 · Review cautionsThe experimental-protocol warning now sits beside the write gate instead of far below it.
+ 4 · Verify rolesAgent and validator / club verification stay together so prerequisites can be completed in one pass.
+
+
+
+
+
+
+ Operational preflight
+ Terms, Before You Transact, verification, and Alpha-Agent quick start stay connected before write review.
+ MetaMask mobile and IPFS return flows now restore the local posture for the same wallet + chain so users can reconnect, refresh live reads, and continue without re-entering setup.
+
+ Open full Alpha console
+
+
+
+
+
+
+
+
+ This is the shared write gate. It stays synchronized with the compact Alpha readiness control and the lower canonical terms section.
+
+
+
+
+ Before You TransactExperimental protocol, irreversible token movements, and smart-contract-governed outcomes stay visible here before you open any review modal or wallet confirmation.
+ Verification postureAgent: Not verified · Validator / club: Not verified. Inputs persist on same-wallet same-chain return so IPFS checks do not wipe your progress.
+ Alpha identity posture pendingConnect wallet, confirm mainnet, accept the shared terms state, verify early if needed, then preview the recommended combined name + identity route.
+
+
+
+ 4) Agent / validator verification
+Verify agent, validator / club, and Alpha posture here before opening approval, review, or write flows. This section now sits directly beneath wallet + terms readiness so mobile users can connect, accept, verify, and proceed in one pass before leaving for IPFS or MetaMask confirmations, then return without losing the local verification setup for the same wallet and chain.
+
+
+ Agent postureNot verified
+ Validator / club postureNot verified
+ Live continuityInputs restore on same wallet + chain return
+
+
+
+
+
+
+ Agent verification
+ Confirm the operating agent label before you create, apply, or claim.
+
+
+
+
+
+
+
+
+
+
+
+ Live postureNot verified
+ Connected walletReconnect restores same-wallet context
+ Alpha postureUse Verify Alpha when needed
+
+
+
+
+ Validator / club verification
+ Complete validator readiness early so approvals and disputes stay one-pass on mobile.
+
+
+
+
+
+
+
+
+
+
+
+ Live postureNot verified
+ Validator modeClub verification enables review posture
+ Return flowSame wallet + chain restores inputs and refreshes live reads
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 5) Alpha-Agent Free Trial & Identity Console
+This operational console is the canonical onboarding surface for *.alpha.agent.agi.eth. It uses only FreeTrialSubdomainRegistrarIdentity at 0x7811993CbcCa3b8bb35a3d919F3BA59eeFbeAA9a to mint the wrapped ENS name and the soulbound Alpha-Agent identity together in one transaction. Issuance always goes to the connected wallet, costs gas only, and no separate name-only path is surfaced.
+
+
+ Recommended routeregister(label) · wrapped name + identity together
+ Identity postureSoulbound · approvals disabled · transfers disabled
+ Commercial terms0 ETH value · gas only · connected wallet only
+
+
+
+
+
+
+ Write access readiness
+ Confirm wallet, network, terms, route, and root posture before writing
+
+ ROOT_NAME · alpha.agent.agi.eth
+ Review full terms
+
+
+
+ WalletNot connected
+ NetworkMainnet required
+ TermsPending
+ RouteRecommended identity path
+ Root usableChecking…
+
+
+
+
+
+
+
+
+ Write access is surfaced here so wallet, network, and legal readiness are visible before any transaction review.
+
+ Review full terms
+
+
+
+
+
+
+
+
+ Open verification
+ Verification posture
+ Verify agent and validator / club status here near the top, then continue with the combined Alpha-Agent route.
+
+
+ AgentNot verified
+ Validator / clubNot verified
+ Verification inputs restore on same-wallet same-chain return, so leaving for IPFS or MetaMask confirmation does not force a full reset.
+
+
+ Current write posture
+ Connect a wallet, switch to Ethereum mainnet, accept the terms, and enter a valid label to let preview(label) determine the exact write path.
+
+
+
+
+
+
+
+ Recommended route active
+ Primary route selection
+ Combined name + identity is the only public registration route surfaced here.
+
+
+
+
+
+
+
+
+ Recommended path: register(label) mints the wrapped subname and soulbound identity to the connected wallet in one transaction. Gas only, no separate name-only path.
+ The combined route is the only public registration action in this console. Lower diagnostics remain available for expert verification and maintenance review.
+
+
+
+
+
+
+
+
+ Identity contract0x7811993CbcCa3b8bb35a3d919F3BA59eeFbeAA9a
+ Canonical write pathregister(label) · claimIdentity(label) · syncIdentityByLabel(label)
+ Parent policy30 day trial · 90 day grace · lowercase a-z and digits only
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Quick start
+ Choose one label and let preview(label) and rootHealth() determine the next action
+
+ 8–63 characters
+ lowercase a-z
+ digits 0-9
+
+
+
+ Current recommendation
+ Enter a label to evaluate the recommended identity path.
+ preview(label) is the primary decision panel. It determines whether this label is available, active, claimable, expired, desynced, or unavailable.
+
+
+
+
+
+
+
+
+ The canonical identity route issues only to the connected wallet. Lowercase letters and digits only, with length between 8 and 63. Full issuance remains beneath alpha.agent.agi.eth.
+ Awaiting valid label.
+
+
+ Full nameAwaiting valid label for derived full name
+ ENS URIAwaiting valid label for derived ENS URI
+ Child nodeAwaiting valid label for derived node
+ Parent postureAvailable once rootHealth() resolves
+
+
+
+
+
+
+
+
+ Enter label
+ Mobile-ready action rail
+ Primary write, refresh, and recovery controls stay grouped above the deeper diagnostics.
+ Connect, accept, verify, and let preview(label) load. Final transaction review keeps the authorize control pinned within reach on mobile.
+
+
+
+
+
+
+ Enter label
+ Suggested next action
+ The recommendation banner above indicates whether register(label), claimIdentity(label), syncIdentityByLabel(label), or no write action is appropriate.
+ Current write gateIdentity flow locked until wallet + mainnet + terms + valid label.
+
+
+ Recommended route action cluster
+ The canonical write path is register(label) for combined name + identity issuance to the connected wallet, with conditional recovery actions immediately below it.
+
+
+
+
+
+
+
+
+
+
+
+ Identity flow locked until wallet + mainnet + terms + valid label.
+
+
+ Recent labels on this device
+
+
+
+ Recommended path methods
+
+
+ RegisterMints the wrapped subname and the soulbound identity together with register(label). Gas only. Connected wallet only.
+ ClaimUse claimIdentity(label) when the wrapped name already belongs to the connected wallet and only the identity must still be issued.
+ SyncRepair path for stale, expired, or desynced local identity posture with syncIdentityByLabel(label).
+
+
+
+
+
+
+
+
+
+
+ Expert reference
+ Registrar diagnostics and protocol posture
+ This disclosure is retained only for expert inspection of compatibility state, wrapper posture, and trial parameters. Public registration above remains the combined route only.
+
+
+ Diagnostics only
+ Combined route only
+
+
+
+
+
+
+
+
+ Expert reference
+ Registrar diagnostics and protocol posture
+ This disclosure is retained only for expert inspection of compatibility state, wrapper posture, and trial parameters. Public registration above remains the combined route only.
+
+ Diagnostics only
+ Combined route only
+
+
+
+ Registration in this console is intentionally centered on register(label) through FreeTrialSubdomainRegistrarIdentity, which issues both the wrapped name and the Alpha-Agent identity to the connected wallet. Use the diagnostics below only to inspect compatibility posture and root readiness.
+ Compatibility diagnostics only. Public registration is the combined register(label) route above.
+
+
+ AvailabilityAwaiting preview(label)
+ Expected trial expiryNot applicable before issuance
+ Canonical write cost0 ETH value · gas only
+
+
+
+
+
+
+
+
+
+ Contract · 0x7811993CbcCa3b8bb35a3d919F3BA59eeFbeAA9a
+ Live preview(label) decision card Awaiting label
+ Driven by preview(label) plus rootHealth() context. Preview guides route selection; issuance facts are verified from token/root reads.
+
+
+ Full nameEnter label for derived full name
+ Token IDDerived after label validation
+ Identity existsPreview pending
+ ClaimablePreview pending
+ RegistrablePreview pending
+ Root posturerootHealth() pending
+ Expected expiryNot applicable before issuance
+ Soulboundtrue · approvals disabled · transfers disabled
+
+
+ Available identity actions
+
+
+ Suggested actionEnter label
+ Write postureWallet + mainnet + terms required
+
+
+
+
+
+
+
+
+
+
+ Asset state
+ Selected-label identity asset dossier
+ Token owner, wrapped ownership, resolver, expiry, mint timestamp, and tokenURI-derived metadata for the selected label.
+
+
+ Token ownerNot applicable before issuance
+ Wrapped ownerNot applicable before issuance
+ ResolverNot applicable before issuance
+ Wrapped expiryNot applicable before issuance
+ Minted atNot applicable before issuance
+
+
+ TokenURI name
+ Not applicable before issuance
+ Token metadata appears after issuance
+
+
+ Token image will appear here when tokenURI metadata exposes one.
+
+
+
+
+
+
+ Operational diagnostics · root healthSecondary
+
+
+
+
+ Use these fields to verify root readiness, wrapper posture, registry alignment, and parent expiry. They are informational and secondary to the quick-start preview above.
+ | ROOT_NAME | Awaiting rootHealth() read |
| ROOT_NODE | Awaiting rootHealth() read |
| rootActive | Awaiting rootHealth() read |
| paused | Awaiting rootHealth() read |
| wrapper | Awaiting rootHealth() read |
| ensRegistry | Awaiting rootHealth() read |
| owner / pendingOwner | Awaiting rootHealth() read |
| wrapped parent owner | Awaiting rootHealth() read |
| parent wrapped / locked | Awaiting rootHealth() read |
| registrar authorized | Awaiting rootHealth() read |
| effective parent expiry | Awaiting rootHealth() read |
| root usable | Awaiting rootHealth() read |
| required child fuses | Awaiting rootHealth() read |
| token name / symbol | Awaiting token metadata reads |
+
+
+ Expert diagnostics · compatibility referenceDiagnostics only
+
+
+
+
+
+ Legacy compatibility reads remain internal and inert. Public registration in this console uses only the combined identity route on FreeTrialSubdomainRegistrarIdentity.
+ | NameWrapper | Awaiting compatibility read |
| Target parent | alpha.agent.agi.eth |
| Target parent node | 0xc74b6c5e8a0d97ed1fe28755da7d06a84593b4de92f6582327bc40f41d6c2d5e |
| Parent active | Awaiting compatibility read |
| Parent locked | Awaiting compatibility read |
| Registrar authorised | Awaiting compatibility read |
| Parent usable | Awaiting compatibility read |
| Parent effective expiry | Awaiting compatibility read |
| Trial period | Awaiting compatibility read |
| Label rules | lowercase a-z0-9, no dots, no hyphens, 8–63 chars |
+
+ Administrative controlsRestricted
+
+
+ Administrative methods remain available for authorized operators, but they are intentionally collapsed by default to keep the onboarding surface clear.
+
+
+ FreeTrialSubdomainRegistrarIdentity Admin
+
+
+
+ Expert registrar controls (authorized parent managers only)
+
+
+
+
+
+
+
+
+ Command Center
+This interface is optimized for three roles: Employer, Agent, and Validator. The readiness deck above now keeps connect, terms, verification, and Alpha-Agent onboarding together before these deeper operational sections.
+
+ New in v34 Prime: ENS job-page preview and Alpha Agent Identity operations are now contract-faithful, preview-driven, and hardened for elite mainnet operator workflows.
+
+ Operational note
+ Posting, applying, approving, disputing, expiring, and finalizing are all separate on-chain actions. This UI helps you decide, but the deployed contract decides the outcome. +
+ + Posting, applying, approving, disputing, expiring, and finalizing are all separate on-chain actions. This UI helps you decide, but the deployed contract decides the outcome. +
+
+
+ Action Readiness
+
+
+ WalletNot connected
+ Network—
+ TermsNot accepted
+ Role readinessView mode
+
+
+
+
+
+
+ What to do first
+
+
+ -
+
- Connect the wallet you want to use on Ethereum Mainnet. +
- Verify the ENS subdomain matching your role. +
- Read the contract-driven terms and accept them here. +
- Use the bond calculator and the economics charts before signing. +
+
+ Best-practice transaction flow
+
+
+ -
+
- Employers: verify payout, URI, duration, and escrow implications before posting. +
- Agents: confirm your ENS, payout eligibility, and likely bond exposure before applying. +
- Validators: read completion material carefully and vote only after independent review. +
+
+ Connected0%
+ Mainnet0%
+ Terms accepted0%
+ Role ready0%
+
+
+
+
+
+
+
+ Activity Concierge
+This page now keeps a local elite-grade activity trail of approvals, submissions, confirmations, and failures you trigger from the UI. It does not write anything extra on-chain; it simply makes your live operating session easier to trust and audit.
+
+
+
+
+
+ No local activity yet. Approvals, job actions, and vault conversions you initiate from this page will appear here.
+
+
+
+
+
+
+
+
+ Operator Deck
+This layer keeps the interface feeling sovereign in practice: verified deployment posture, event-derived job intelligence, local continuity, and mobile-safe operating controls stay visible while you work.
+
+ No sync yet
+
+
+
+
+
+ Live sync posture
+
+
+ Last refreshNever
+ Freshness—
+ Auto-refreshOff
+ Pending local activity0
+
+
+
+
+
+
+
+ Auto-refresh pauses automatically when no wallet is connected or the UI is not on Ethereum Mainnet. It also avoids silently firing while a review modal is open.
+
+
+ Attention queue
+ A ranked shortlist of jobs that are most likely to need action from this session right now.
+
+
+ Refresh the board to build the attention queue.
+
+
+
+ Lifecycle Guide
+
+
+
+
+
+
+ 1
PostEmployer escrows the full payout in $AGIALPHA and publishes a job URI plus optional details.
2
ApplyThe first eligible agent can apply, provided ENS or allowlist authorization passes and the agent bond can be posted.
3
Complete + ReviewAssigned agent requests completion within the allowed duration; validators can then approve or disapprove during review.
4
SettleAfter challenge/review rules are satisfied, anyone may finalize; otherwise the job can dispute, expire, refund, or complete.
+
+
+
+
+
+
+
+
+ Payout Composition
+
+
+
+
+
+ Current model—agent share
+
+
+ Agent payout—
+ Validator pool—
+ Retained remainder—
+ The exact agent payout is snapshotted at assignment time from the highest eligible AGI type held by the applying agent. This chart updates with your currently verified agent profile if available.
+
+
+
+ Validation Pressure
+
+
+ Approvals threshold—
+ Disapprovals threshold—
+ Vote quorum—
+ Slash severity—
+ Higher validator thresholds and higher quorum reduce low-participation outcomes, but they also increase the chance of forced disputes if validators do not show up.
+
+
+ Role Playbook
+
+
+
+
+
+
+
+ -
+
- Use durable URIs and explicit acceptance criteria. +
- Keep payout proportional to job complexity and validator budget. +
- Cancel only before assignment; after assignment, use contract lifecycle tools. +
+
+ -
+
- Verify agent ENS first, then inspect likely bond exposure. +
- Do not miss the duration window; late completion requests revert. +
- Provide a strong completion URI because validators only see what you submit. +
+
+ -
+
- Verify club ENS before voting. +
- Only vote after independent review of the completion URI and job spec URI. +
- Wrong-side votes can be heavily slashed depending on final outcome. +
+
+
+
+
+
+
+
+
+ Before You Transact
+
+
+ The interface below now includes the full smart-contract Terms & Conditions in a structured, readable format. For write actions, this page asks you to confirm you have read and accepted them.
+
+
+
+
+
+
+
+
+
+
+
+
+ Quick Bond Calculator
+ Fast planning tool using the live contract parameters shown on this page. Validator bond uses the public bond parameters directly. Dispute bond follows the contract constants in the verified source. Agent bond uses deterministic client-side math that mirrors the verified BondMath parameters (payout, duration, bps, min, max, and duration limit).
+
+
+
+
+
+
+
+
+
+
+ Agent bond (BondMath mirror)—
+ Validator bond—
+ Dispute bond—
+ Validator reward pool—
+
+
+
+
+
+
+
+
+
+
+ $AGIALPHA Conversion Console
+The deBridge transfer leg stays embedded on this page and auto-loads the exact canonical Solana → Ethereum dePort route you specified. Change only the Solana amount here if you want a different transfer size; otherwise the route stays pinned until you intentionally use the Advanced controls.
+
+ Canonical path
+ Solana
+ → Ethereum interim
+ → official
+ via vault
+ + Solana
tWKHzXd5PRmxTF5cMfJkm2Ua3TcjwNNoSRUqx6Apump+ → Ethereum interim
0x2e8Fb54C3eC41F55F06C1F082C081a609EaA4ebe+ → official
0xa61a3b3a130a9c20768eebf97e21515a6046a1fa+ via vault
0x27d6fe8668c6f652ac26ffae020d949f03af80d8
+
+
+
+
+
+ A. Embedded deBridge transfer
+ This frame auto-loads the exact dePort route you provided. The only default control here is the Solana $AGIALPHA amount; when you change it, the embed reloads with the same canonical route and the new amount.
+
+
+
+
+
+
+
+
+
+ Changing this amount automatically refreshes the embedded route with the same Solana → Ethereum AGIALPHA path.
+
+
+ Solana wallet: checking…
+ EVM wallet: checking…
+ Embedded route: waiting to load
+
+
+
+
+
+
+
+
+
+
+ Path
+ SOL $AGIALPHA → ETH interim $AGIALPHA
Amount
+ 10000 $AGIALPHA
Receiver mode
+ Canonical route (no receiver override)
+
+
+ 1. Auto-loadedThe embedded frame opens with the exact canonical dePort route as soon as the page is ready.
+ 2. Amount-drivenUse the amount field above for route changes. The UI keeps the rest of the bridge path fixed.
+ 3. Return hereOnce the interim Ethereum token lands, use the vault panel on the right to mint the official Ethereum $AGIALPHA.
+
+
+
+
+ Loading the exact locked deBridge route… If your browser blocks the embed, open the fallback from Advanced bridge controls.
+
+
+
+
+
+ Embedded routeWaiting to load
+ Last route eventNo event yet
+ ReceiverCanonical dePort route (no receiver override)
+ —
+
+
+ Advanced bridge controls
+
+
+
+
+
+
+
+
+
+ Leave this blank to preserve the exact canonical route. Use it only if you intentionally want to add an
+ address= parameter to the dePort URL.
+
+
+
+
+
+
+ The fallback opens the same exact route in a dedicated tab only if the embedded frame is blocked by your browser or extension environment.
+ Bridge status
No embedded route event yet.
+ No embedded route event yet.
+
+ B. Mint official Ethereum $AGIALPHA
+ Once the interim Ethereum token arrives, this side handles the final official mint step. The default button uses your current bridged-token balance and your connected Ethereum wallet as recipient. Advanced controls remain available for a custom amount or recipient.
+
+
+
+
+ Bridged token balance—
+ Official token balance—
+ Vault allowance—
+ Preview mint out—
+
+ One-click default
+ The primary conversion flow stays on Ethereum mainnet, requests approval only if needed, and then calls
+
+ + The primary conversion flow stays on Ethereum mainnet, requests approval only if needed, and then calls
depositExact on AGIALPHAEqualMinterVault.
+
+
+
+
+
+
+
+
+
+ Advanced conversion controls
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Vault state: —
+ Vault version: — · Accepted token: —
+
+ Mint path
+ The official mint step stays entirely on Ethereum mainnet and is where the final official $AGIALPHA is minted. +
+ + The official mint step stays entirely on Ethereum mainnet and is where the final official $AGIALPHA is minted. +
+
+
+
+
+
+ Summary
+Total Jobs: 0
+ Required Validator Approvals: 0
+ Required Validator Disapprovals: 0
+ Vote Quorum: 0
+ Completion Review Period: —
+ Challenge Window: —
+
+
+ My Stats
+My $AGIALPHA Balance: 0
+ My Reputation: 0
+ Jobs I posted: 0
+
+ Agent ENS: not verified
+
+ Club ENS: not verified
+
+
+
+
+
+
+ Protocol Parameters (Mainnet)
+These values are read directly from the contract. Bonds are computed on-chain from payout/duration using these parameters.
+
+
+
+
+ Agent bond min: — $AGIALPHA
+ Agent bond bps: —
+ Agent bond max: — $AGIALPHA
+ Max active jobs / agent: —
+
+
+ Validator bond bps: —
+ Validator bond min: — $AGIALPHA
+ Validator bond max: — $AGIALPHA
+ Validator slash bps: —
+
+
+ Validation reward %: —
+ Max job payout: — $AGIALPHA
+ Job duration limit: — seconds
+
+
+ Paused (intake): —
+ Settlement paused: —
+ Dispute review period: —
+
+
+
+ Bond Notes
+
+
+ -
+
- Agent bond is charged when applying for a job, based on payout + duration, and returned on agent-win paths. +
- Validator bond is charged per vote (approve/disapprove). A portion may be slashed depending on final outcome. +
- Dispute bond may be required when starting a dispute (computed on-chain; constants aren’t exposed as public getters). +
+
+
+
+
+
+
+ 2) Create a Job (Employer)
+This flow keeps job creation local-first and single-page. You can compose a structured job spec, generate standards-friendly JSON metadata, optionally pin it to IPFS directly from the browser, preview the ENS job page details that the contract stack is designed to create, and then submit the final on-chain createJob transaction using the resulting URI.
+
+
+
+
+
+
+
+
+
+
+ Job Spec Builder
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A default cover image is included so the generated NFT metadata displays well across wallets and galleries. You can replace it at any time with another valid IPFS or HTTPS image URI.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Drafts are saved locally on this device only. Nothing is uploaded or sent on-chain until you choose to do so.
+
+
+ Metadata Cover Preview
+ This is the image that will be embedded into the generated metadata JSON.
+
+ ![Job metadata cover preview]()
+
+
+
+ Current image URI—
+ Best practice: prefer a stable IPFS image for long-term NFT display.
+
+
+ Optional Browser-Only IPFS Pinning
+ To remain 100% single-page and backend-free, this uploader uses a user-supplied IPFS pinning credential or endpoint directly from the browser. Nothing is required for basic usage; you can also download the JSON and pin it elsewhere. The generated CID/URI can then be inserted into the on-chain job creation form automatically.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Generated metadata URI: —
+ CID / response: —
+
+
+
+
+
+
+ Metadata Preview
+
+
+ No image
+
+
+ AGI Job Draft
+ Generate JSON to preview a standards-friendly job metadata object.
+
+
+
+
+
+
+ {
+ "schema":"agijobmanager/job-spec/v1"
+}
+
+
+
+
+ ENS Job Page Preview
+ This preview reflects the ENSJobPages integration path. It shows the label, name, node, ens:// URI, and basic hook configuration so the employer understands what the ecosystem is set up to create around a job.
+ | ENSJobPages contract address | — |
| Address source | unavailable |
| ENSJobPages owner | — |
| ENS registry | — |
| NameWrapper | — |
| Public resolver | — |
| Configured root name | — |
| Configured root node | — |
| Linked jobManager | — |
| Job label prefix | — |
| Next job id | — |
| Snapshot status | — |
| Compatibility label (preview/effective) | — |
| Compatibility ENS name (preview/effective) | — |
| Compatibility ENS URI (preview/effective) | — |
| Compatibility node (preview/effective) | — |
| ENS metadata posture | event-derived + resolver-observed |
| Manager tokenURI posture | Unavailable in public ABI |
| Config locked | — |
| Public prerequisite summary | — |
+ Best-practice interpretation
+ If the ENSJobPages stack is configured, preview values project
+ + If the ENSJobPages stack is configured, preview values project
jobLabelPrefix + decimal(jobId); effective values become authoritative only after authority establishment. Public spec/completion texts and lock actions remain state-dependent and explicitly reviewed.
+
+
+
+ Autonomous Agent Packet (Draft)
+ This turns the current job draft into a machine-consumable work order. Use it to feed autonomous agents, validator copilots, or external orchestration systems before the job is posted on-chain.
+ The packet updates live from the builder fields above. The Executor JSON tab exposes the full structured object; the role tabs expose targeted views for Agent, Validator, and Employer.
+
+
+
+
+
+
+ Generate or edit the job draft to build an autonomous agent packet.
+
+
+
+
+
+
+ On-Chain Create Job Transaction
+ Prime creation supports standard open posting, configured intake modes, and premium procurement. The classic builder remains available here; use it for
+ createJob(...) and extend into configured / premium flows where relevant.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Best practice: use a canonical
+ ipfs://... Job Spec URI and keep the on-chain details field concise.
+ What happens next
+ The employer escrows the payout, the contract emits
+ + The employer escrows the payout, the contract emits
JobCreated, and the ENSJobPages hook may attempt to create or update a corresponding job ENS page using the configured root and resolver stack.
+
+
+
+
+ Advanced local commitment notebook (secondary)
Prime procurement operationsUse the flagship discovery workbench above for the main workflow. Use this notebook only as the advanced secondary local helper for commit/reveal preparation and salt storage. Salts and commitments here are local helpers, not on-chain state; store them safely until reveal, and treat countdowns as approximate unless live pause-adjusted reconstruction is available.
+
+
+ Application flow
+ Commit application → reveal application URI → shortlist → finalist acceptance → trial submission.
Validator scoring
+ Commit score → reveal score → finalize winner → fallback promote if needed → claim balances.
Creation modes
+ OpenFirstCome, SelectedAgentOnly, PerJobMerkleRoot, premium discovery creation, and attach-procurement for selected-agent jobs.
+
+
+
+ Application commitment vault
+ Local only. Not written on-chain. Store safely until reveal. Losing the salt makes reveal impossible.
+
+
+
+
+
+
+
+
+
+
+
+ keccak256(abi.encodePacked(procurementId, agent, applicationURI, salt))
+ Commitment: —
+
+
+ Validator score commitment vault
+ Local only. Use this to prepare score commit/reveal notebooks per procurement and finalist.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Suggested local commitment: keccak256(abi.encodePacked(procurementId, finalist, validator, score, salt))
+ Vault notebook: No local Prime procurement notes yet.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Jobs
+This table is your live operational surface. Open jobs accept eligible agent applications; assigned jobs can move into completion review; completed or expired jobs can have ENS locking actions. Buttons only appear when the current UI state suggests the action may be relevant.
+ Actions below call the on-chain methods on
+ 0xF8fc…993e.
+ Searchable
+ Filterable
+ Watchlist-ready
+ Deep-linkable
+
+ | ID | +Employer | +Job Spec URI | +Payout | +Duration | +Agent | +Status | +Actions | +
|---|
+
+
+
+ Completion NFTs (ERC-721)
+Prime completion receipts are handled through the dedicated
+ AGIJobCompletionNFT contract. Manager NFTIssued events and NFT reads are the authoritative browsing sources for this section.
+
+
+
+ My NFTs
+
+
+ Latest NFTs
+
+
+
+ Admin Control Surfaces
+Reads are live where available. High-risk write methods are intentionally grouped in danger accordions and require transaction review before wallet confirmation.
+
+
+
+
+ Manager Prime Admin
+Owner: —
+ Moderator posture: —
+
+
+
+
+
+ Routine controls
+ +
+
+ Danger controls (irreversible / high-risk)
+ +
+
+ ENSJobPages Admin
Operational confidence stays conservative when Prime compatibility is not publicly provable from current getters.
+ Resolved ENSJobPages: —
+ Owner: —
+ ENS registry: —
+ NameWrapper: —
+ Public resolver: —
+ jobsRootNode: —
+ jobsRootName: —
+ jobManager: —
+ TokenURI mode getter is not exposed by active ENSJobPages public ABI; this console does not infer hidden state.
+ configLocked: —
+ Job label prefix: —
+
+
+
+
+
+ Routine controls
+ +
+
+ Danger controls (irreversible / high-risk)
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Practical Guidance
+
+
+
+ For Employers
Think of this as an escrow-first workflow. Once a job is created, your payout is locked in the contract. The biggest quality lever is the clarity of the jobSpecURI and acceptance criteria. +
+ Think of this as an escrow-first workflow. Once a job is created, your payout is locked in the contract. The biggest quality lever is the clarity of the jobSpecURI and acceptance criteria. +
+ For Agents
Your eligibility and payout share depend on the contract rules. Verify your ENS and understand your bond exposure before racing to apply for open work. +
+ Your eligibility and payout share depend on the contract rules. Verify your ENS and understand your bond exposure before racing to apply for open work. +
+ For Validators
Validator actions are economically meaningful. You are not just clicking approve/disapprove; you are staking a position that can be rewarded or slashed. +
+ Validator actions are economically meaningful. You are not just clicking approve/disapprove; you are staking a position that can be rewarded or slashed. +
+
+
+
+
+ Terms & Conditions
+Copied into this interface from the AGIJobManager smart contract source text you provided, organized for easier reading. This section preserves the full text while making navigation easier.
+
+ 1. Definitions
+2. Nature of the Protocol; No Intermediary; Code Controls
+3. Eligibility; Sanctions; Legal Compliance (User Responsibility)
+4. Roles and Exclusive Responsibilities
+5. Job Lifecycle and Core Mechanics (Disclosure)
+6. Disputes; Moderation; No Duty to Resolve
+7. Protocol Economics; Fees; Retained Remainder Disclosure
+8. Taxes, Withholding, Reporting (Exclusive User Responsibility)
+9. No Employment Relationship; Independent Contractors Only
+10. User Content; Intellectual Property; Confidentiality
+11. Prohibited Uses
+12. Assumption of Risk (Smart Contract and Crypto Risks)
+13. Disclaimers; No Warranties
+14. Limitation of Liability
+15. Indemnification
+16. Governing Law; Forum; User-to-User Disputes
+17. Changes to Terms; Continued Use
+18. Severability; Entire Agreement; No Waiver
+Regulatory Compliance & Legal Disclosures (Token and Program)
+Research Program Notice; No Warranty
+[ R E G U L A T O R Y C O M P L I A N C E & L E G A L D I S C L O S U R E S ]
+1. Token Usage: $AGIALPHA tokens are strictly utility tokens—no equity, no profit-sharing—intended for the purchase of products/services by the AGI ALPHA AGENT (ALPHA.AGENT.AGI.Eth). They are not intended for investment or speculative purposes.
+2. Non-Refundable: Purchases of $AGIALPHA tokens are final and non-refundable.
+3. No Guarantee of Value: The issuer does not guarantee any specific value of the $AGIALPHA token in relation to fiat currencies or other cryptocurrencies.
+4. Regulatory Compliance: It is the user’s responsibility to ensure that the purchase and use of $AGIALPHA tokens comply with all applicable laws and regulations.
+5. User Responsibility: Users are responsible for complying with the laws in their own jurisdiction regarding the purchase and use of $AGIALPHA tokens.
+
+ Scroll inside the area below to read the full contract text. The expanded layout is optimized for careful review.
+
+
+
+
+1. Definitions
+- "Protocol" / "AGIJobManager": The AGIJobManager smart contract(s) implementing job posting, assignment, escrow, bonds, validation, disputes, and settlement.
- "$AGIALPHA": The ERC-20 token used by the Protocol for job payouts, validator rewards, agent/validator/dispute bonds, and any protocol-retained amounts.
- "Employer": Any person or entity that posts a Job and escrows a payout in $AGIALPHA.
- "Agent": Any person or entity that applies for, performs, and requests completion of a Job.
- "Validator": Any person or entity that votes to approve or disapprove a Job completion request under the Protocol rules, posting any required validator bond.
- "Moderator": An address designated by the Protocol owner with permission to resolve disputes through the Protocol's dispute-resolution functions.
- "Owner": The address holding administrative permissions in the Protocol (e.g., pausing, parameter updates, allowlist/blacklist management, moderator management, delisting unassigned jobs, and withdrawing certain withdrawable balances as permitted by the code).
- "Job": A work request defined by an on-chain job id plus off-chain/on-chain references (e.g., jobSpecURI, details, and later jobCompletionURI).
- "Job Spec URI": A URI describing the Job requested by the Employer.
- "Job Completion URI": A URI submitted by the Agent describing or containing the completion deliverable(s).
- "Escrow": The $AGIALPHA amount deposited by the Employer as the Job payout and held by the Protocol until settlement according to code.
- "Bonds": Any $AGIALPHA amounts posted as Agent bonds, Validator bonds, or Dispute bonds per the Protocol.
- "Settlement": The Protocol's distribution of escrowed payout and bonds according to the on-chain rules.
- "User Content": Any Job Spec URI, Job Completion URI, details, or any referenced content (including IPFS/HTTP content) supplied by users.
+- "$AGIALPHA": The ERC-20 token used by the Protocol for job payouts, validator rewards, agent/validator/dispute bonds, and any protocol-retained amounts.
- "Employer": Any person or entity that posts a Job and escrows a payout in $AGIALPHA.
- "Agent": Any person or entity that applies for, performs, and requests completion of a Job.
- "Validator": Any person or entity that votes to approve or disapprove a Job completion request under the Protocol rules, posting any required validator bond.
- "Moderator": An address designated by the Protocol owner with permission to resolve disputes through the Protocol's dispute-resolution functions.
- "Owner": The address holding administrative permissions in the Protocol (e.g., pausing, parameter updates, allowlist/blacklist management, moderator management, delisting unassigned jobs, and withdrawing certain withdrawable balances as permitted by the code).
- "Job": A work request defined by an on-chain job id plus off-chain/on-chain references (e.g., jobSpecURI, details, and later jobCompletionURI).
- "Job Spec URI": A URI describing the Job requested by the Employer.
- "Job Completion URI": A URI submitted by the Agent describing or containing the completion deliverable(s).
- "Escrow": The $AGIALPHA amount deposited by the Employer as the Job payout and held by the Protocol until settlement according to code.
- "Bonds": Any $AGIALPHA amounts posted as Agent bonds, Validator bonds, or Dispute bonds per the Protocol.
- "Settlement": The Protocol's distribution of escrowed payout and bonds according to the on-chain rules.
- "User Content": Any Job Spec URI, Job Completion URI, details, or any referenced content (including IPFS/HTTP content) supplied by users.
+
+2. Nature of the Protocol; No Intermediary; Code Controls
+1) Self-executing software. The Protocol is a set of smart contracts that execute transactions according to on-chain code. Outcomes (assignment, settlement, dispute states, reward allocation, slashing, etc.) are determined by the code and blockchain conditions.
2) No employment agency / marketplace operator role. The Protocol is not an employer, employment agency, staffing firm, contractor, broker, payment processor, escrow agent, fiduciary, or financial institution.
3) No party to user agreements. Any agreement regarding work scope, quality standards, deliverables, deadlines, confidentiality, IP ownership, compliance obligations, and payment terms exists only between the Employer and the Agent (and, if applicable, between either of them and any Validator). The Protocol is not a party to those agreements and has no obligations under them.
4) Code prevails. If these Terms conflict with the deployed code, the code prevails for on-chain behavior. These Terms allocate risk and responsibilities and govern off-chain expectations to the maximum extent permitted.
+2) No employment agency / marketplace operator role. The Protocol is not an employer, employment agency, staffing firm, contractor, broker, payment processor, escrow agent, fiduciary, or financial institution.
3) No party to user agreements. Any agreement regarding work scope, quality standards, deliverables, deadlines, confidentiality, IP ownership, compliance obligations, and payment terms exists only between the Employer and the Agent (and, if applicable, between either of them and any Validator). The Protocol is not a party to those agreements and has no obligations under them.
4) Code prevails. If these Terms conflict with the deployed code, the code prevails for on-chain behavior. These Terms allocate risk and responsibilities and govern off-chain expectations to the maximum extent permitted.
+
+3. Eligibility; Sanctions; Legal Compliance (User Responsibility)
+You represent, warrant, and covenant that:
- You have the legal capacity and authority to enter into these Terms.
- Your use of the Protocol is compliant with all applicable laws and regulations (present and future), including (without limitation) labor and employment laws, tax laws, consumer protection laws, IP laws, data protection laws, anti-bribery laws, export controls, and sanctions.
- You are not located in, organized under, or ordinarily resident in any jurisdiction where use of the Protocol would be unlawful.
- You are not subject to sanctions or on any restricted party lists, and you will not use the Protocol to transact with sanctioned parties or prohibited jurisdictions.
All compliance obligations are solely yours (Employer/Agent/Validator, as applicable). The Protocol does not perform KYC/AML checks and does not provide compliance advice or compliance services.
+- You have the legal capacity and authority to enter into these Terms.
- Your use of the Protocol is compliant with all applicable laws and regulations (present and future), including (without limitation) labor and employment laws, tax laws, consumer protection laws, IP laws, data protection laws, anti-bribery laws, export controls, and sanctions.
- You are not located in, organized under, or ordinarily resident in any jurisdiction where use of the Protocol would be unlawful.
- You are not subject to sanctions or on any restricted party lists, and you will not use the Protocol to transact with sanctioned parties or prohibited jurisdictions.
All compliance obligations are solely yours (Employer/Agent/Validator, as applicable). The Protocol does not perform KYC/AML checks and does not provide compliance advice or compliance services.
+
+4. Roles and Exclusive Responsibilities
+4.1 Employer Responsibilities (Exclusive)
The Employer is solely and exclusively responsible for:
- The legality, accuracy, and completeness of the Job description, Job Spec URI, details, and any referenced content.
- Ensuring the Job does not solicit or require unlawful acts, regulated acts without permits, infringement, malware, fraud, or rights violations.
- Determining whether a Job creates (or could be interpreted as creating) an employment relationship, and satisfying all obligations associated with such classification, including payroll, withholding, insurance, benefits, reporting, and worker protections.
- All tax obligations relating to posting the Job, escrowing $AGIALPHA, receiving any refunds, or any other token transfers.
- Any off-chain contracting, NDAs, IP assignments/licenses, confidentiality terms, acceptance criteria, warranties, or service levels for the Job.
4.2 Agent Responsibilities (Exclusive)
The Agent is solely and exclusively responsible for:
- Performing the Job in accordance with any off-chain agreement with the Employer.
- Ensuring all deliverables and the Job Completion URI content are lawful and do not violate third-party rights.
- All tax obligations relating to receiving $AGIALPHA payments, posting or forfeiting Agent bonds, or receiving any additional settlement amounts.
- Maintaining operational security of wallets, private keys, endpoints, and any systems used to perform Jobs.
- Understanding that Agent bonds may be forfeited under certain settlement paths per the code.
4.3 Validator Responsibilities (Exclusive)
Each Validator is solely and exclusively responsible for:
- Performing independent diligence before approving/disapproving completion, and voting honestly according to their own judgment and any standards they adopt or communicate.
- All consequences of their votes, including the possibility of slashing or reduced returns per the Protocol rules.
- All tax obligations relating to validator rewards, bond returns, slashing outcomes, and any other transfers.
- Compliance with all applicable laws (including any professional, licensing, or regulatory obligations that might apply to their validation activity).
- Avoiding bribery, collusion, or manipulation; recognizing that the Protocol's incentives may not prevent manipulation and that participation is at their own risk.
4.4 No Reliance on Validators, Moderators, or Owner
- Employers and Agents acknowledge that Validator participation may be insufficient, adversarial, mistaken, or absent.
- Moderators (where enabled) may act at their discretion, may be unavailable, and owe no duty to any user.
- The Owner may pause or restrict functions per the code and owes no duty to keep the Protocol available or to resolve disputes.
+The Employer is solely and exclusively responsible for:
- The legality, accuracy, and completeness of the Job description, Job Spec URI, details, and any referenced content.
- Ensuring the Job does not solicit or require unlawful acts, regulated acts without permits, infringement, malware, fraud, or rights violations.
- Determining whether a Job creates (or could be interpreted as creating) an employment relationship, and satisfying all obligations associated with such classification, including payroll, withholding, insurance, benefits, reporting, and worker protections.
- All tax obligations relating to posting the Job, escrowing $AGIALPHA, receiving any refunds, or any other token transfers.
- Any off-chain contracting, NDAs, IP assignments/licenses, confidentiality terms, acceptance criteria, warranties, or service levels for the Job.
4.2 Agent Responsibilities (Exclusive)
The Agent is solely and exclusively responsible for:
- Performing the Job in accordance with any off-chain agreement with the Employer.
- Ensuring all deliverables and the Job Completion URI content are lawful and do not violate third-party rights.
- All tax obligations relating to receiving $AGIALPHA payments, posting or forfeiting Agent bonds, or receiving any additional settlement amounts.
- Maintaining operational security of wallets, private keys, endpoints, and any systems used to perform Jobs.
- Understanding that Agent bonds may be forfeited under certain settlement paths per the code.
4.3 Validator Responsibilities (Exclusive)
Each Validator is solely and exclusively responsible for:
- Performing independent diligence before approving/disapproving completion, and voting honestly according to their own judgment and any standards they adopt or communicate.
- All consequences of their votes, including the possibility of slashing or reduced returns per the Protocol rules.
- All tax obligations relating to validator rewards, bond returns, slashing outcomes, and any other transfers.
- Compliance with all applicable laws (including any professional, licensing, or regulatory obligations that might apply to their validation activity).
- Avoiding bribery, collusion, or manipulation; recognizing that the Protocol's incentives may not prevent manipulation and that participation is at their own risk.
4.4 No Reliance on Validators, Moderators, or Owner
- Employers and Agents acknowledge that Validator participation may be insufficient, adversarial, mistaken, or absent.
- Moderators (where enabled) may act at their discretion, may be unavailable, and owe no duty to any user.
- The Owner may pause or restrict functions per the code and owes no duty to keep the Protocol available or to resolve disputes.
+
+5. Job Lifecycle and Core Mechanics (Disclosure)
+This section summarizes expected mechanics; the deployed code controls.
5.1 Posting a Job (Employer)
- To post a Job, the Employer escrows the full payout amount in $AGIALPHA into the Protocol.
- The Employer provides a Job Spec URI and optional details.
- Jobs may have maximum payout and duration limits set by the Protocol.
5.2 Applying / Assignment (Agent)
- A Job may be assigned to the first eligible Agent who successfully applies under the Protocol rules.
- Eligibility may depend on authorization mechanisms (e.g., allowlists, Merkle proofs, or ENS-based authorization).
- The Protocol may require an Agent bond (computed by code) to be posted at application/assignment time.
- The Agent's payout percentage may be determined by the Agent's holdings of specific NFT types configured in the Protocol and snapshotted at assignment time.
5.3 Completion Request (Agent)
- The Agent requests completion by submitting a Job Completion URI within the permitted time windows enforced by the Protocol.
- The Protocol may enforce review periods and timeouts.
5.4 Validation Voting (Validators)
- Authorized Validators may approve or disapprove during the completion review window.
- Validator voting may require posting a Validator bond per vote (computed by code).
- Validator votes can trigger:
- Approval threshold reached (with a subsequent challenge window before settlement), or
- Disapproval threshold reached, which may put the Job into dispute.
5.5 Finalization / Settlement (Anyone may be able to call)
- After the applicable review/challenge windows, settlement can occur according to the Protocol logic, including outcomes where:
- The Agent wins (payout to Agent, validator rewards distributed, remainder retained by protocol), or
- The Employer wins (refund to Employer, validator settlement, possible agent bond forfeiture), or
- A dispute is forced due to insufficient participation or ties.
5.6 Expiration
- If conditions in the code are met (e.g., time elapsed without completion request), a Job may be expired, which can trigger refund mechanics and bond settlement.
5.7 Cancellation / Delisting
- An Employer may be able to cancel an unassigned Job (per code).
- The Owner may delist/cancel unassigned Jobs (per code).
- Users acknowledge there is no obligation to keep a Job listed or available.
+5.1 Posting a Job (Employer)
- To post a Job, the Employer escrows the full payout amount in $AGIALPHA into the Protocol.
- The Employer provides a Job Spec URI and optional details.
- Jobs may have maximum payout and duration limits set by the Protocol.
5.2 Applying / Assignment (Agent)
- A Job may be assigned to the first eligible Agent who successfully applies under the Protocol rules.
- Eligibility may depend on authorization mechanisms (e.g., allowlists, Merkle proofs, or ENS-based authorization).
- The Protocol may require an Agent bond (computed by code) to be posted at application/assignment time.
- The Agent's payout percentage may be determined by the Agent's holdings of specific NFT types configured in the Protocol and snapshotted at assignment time.
5.3 Completion Request (Agent)
- The Agent requests completion by submitting a Job Completion URI within the permitted time windows enforced by the Protocol.
- The Protocol may enforce review periods and timeouts.
5.4 Validation Voting (Validators)
- Authorized Validators may approve or disapprove during the completion review window.
- Validator voting may require posting a Validator bond per vote (computed by code).
- Validator votes can trigger:
- Approval threshold reached (with a subsequent challenge window before settlement), or
- Disapproval threshold reached, which may put the Job into dispute.
5.5 Finalization / Settlement (Anyone may be able to call)
- After the applicable review/challenge windows, settlement can occur according to the Protocol logic, including outcomes where:
- The Agent wins (payout to Agent, validator rewards distributed, remainder retained by protocol), or
- The Employer wins (refund to Employer, validator settlement, possible agent bond forfeiture), or
- A dispute is forced due to insufficient participation or ties.
5.6 Expiration
- If conditions in the code are met (e.g., time elapsed without completion request), a Job may be expired, which can trigger refund mechanics and bond settlement.
5.7 Cancellation / Delisting
- An Employer may be able to cancel an unassigned Job (per code).
- The Owner may delist/cancel unassigned Jobs (per code).
- Users acknowledge there is no obligation to keep a Job listed or available.
+
+6. Disputes; Moderation; No Duty to Resolve
+1) Dispute initiation. A dispute may be initiated by an Employer or Agent (and/or may be triggered by validator disapproval thresholds) as permitted by the code. Disputes may require a Dispute bond in $AGIALPHA.
2) Moderator resolution. Where enabled, Moderators may resolve disputes using the Protocol's dispute code mechanism (e.g., settle in favor of Agent or Employer).
3) No obligation; no SLA. The Protocol, Owner, and Moderators have no obligation to resolve disputes within any timeframe (or at all), except as the code permits. Any reliance on moderator action is at user risk.
4) Off-chain disputes remain off-chain. The Protocol cannot adjudicate legal questions (fraud, IP infringement, breach of contract, misrepresentation, employment classification, etc.). Those issues are solely between users and must be handled off-chain.
+2) Moderator resolution. Where enabled, Moderators may resolve disputes using the Protocol's dispute code mechanism (e.g., settle in favor of Agent or Employer).
3) No obligation; no SLA. The Protocol, Owner, and Moderators have no obligation to resolve disputes within any timeframe (or at all), except as the code permits. Any reliance on moderator action is at user risk.
4) Off-chain disputes remain off-chain. The Protocol cannot adjudicate legal questions (fraud, IP infringement, breach of contract, misrepresentation, employment classification, etc.). Those issues are solely between users and must be handled off-chain.
+
+7. Protocol Economics; Fees; Retained Remainder Disclosure
+1) Validator reward budget. The Protocol may allocate a portion of the Job payout as a validator reward budget (as snapshotted per job) for distribution to participating Validators, subject to code rules.
2) Bond returns and slashing. Validator bonds may be returned in full, partially slashed, or redistributed depending on whether a Validator ends up on the correct side of the final outcome, as defined by the code.
3) Protocol-retained remainder (platform revenue). On certain settlement paths (including Agent-win), the Protocol may retain the remainder of the Job payout after Agent and Validator allocations. This remainder may become withdrawable by the Owner under conditions specified in the code (e.g., when paused and when not backing active escrows/bonds).
4) No refunds from the Protocol. Token movements are governed by the smart contract; there is no guarantee of reversal, refunds, or discretionary recovery.
5) Gas fees. Users pay their own gas/transaction fees and accept the risk of network congestion, failed transactions, MEV, reorgs, and other chain-level issues.
+2) Bond returns and slashing. Validator bonds may be returned in full, partially slashed, or redistributed depending on whether a Validator ends up on the correct side of the final outcome, as defined by the code.
3) Protocol-retained remainder (platform revenue). On certain settlement paths (including Agent-win), the Protocol may retain the remainder of the Job payout after Agent and Validator allocations. This remainder may become withdrawable by the Owner under conditions specified in the code (e.g., when paused and when not backing active escrows/bonds).
4) No refunds from the Protocol. Token movements are governed by the smart contract; there is no guarantee of reversal, refunds, or discretionary recovery.
5) Gas fees. Users pay their own gas/transaction fees and accept the risk of network congestion, failed transactions, MEV, reorgs, and other chain-level issues.
+
+8. Taxes, Withholding, Reporting (Exclusive User Responsibility)
+The Employer, Agent, and each Validator are exclusively responsible for:
- Determining and paying any and all taxes (income, payroll, self-employment, VAT/GST/sales tax, withholding, capital gains, information reporting, etc.) arising from:
- Job payouts, validator rewards, protocol distributions, refunds;
- Posting, returning, or forfeiting bonds;
- Token price volatility and taxable events in their jurisdiction.
- Maintaining records and issuing any required invoices, receipts, and tax forms.
- Handling any withholding obligations, if applicable.
The Protocol does not provide tax advice, does not withhold taxes, and does not issue tax forms.
+- Determining and paying any and all taxes (income, payroll, self-employment, VAT/GST/sales tax, withholding, capital gains, information reporting, etc.) arising from:
- Job payouts, validator rewards, protocol distributions, refunds;
- Posting, returning, or forfeiting bonds;
- Token price volatility and taxable events in their jurisdiction.
- Maintaining records and issuing any required invoices, receipts, and tax forms.
- Handling any withholding obligations, if applicable.
The Protocol does not provide tax advice, does not withhold taxes, and does not issue tax forms.
+
+9. No Employment Relationship; Independent Contractors Only
+1) No employment relationship created by the Protocol. Nothing in the Protocol or these Terms creates an employment, partnership, joint venture, agency, fiduciary, or franchise relationship between:
- The Protocol (or its publishers/maintainers/Owner/Moderators) and any user; or
- Any Employer and any Agent, unless they separately create such a relationship off-chain.
2) Employer classification duty. The Employer is solely responsible for worker classification and compliance with all related obligations.
3) No benefits. The Protocol does not provide benefits, insurance, or protections to any user.
+- The Protocol (or its publishers/maintainers/Owner/Moderators) and any user; or
- Any Employer and any Agent, unless they separately create such a relationship off-chain.
2) Employer classification duty. The Employer is solely responsible for worker classification and compliance with all related obligations.
3) No benefits. The Protocol does not provide benefits, insurance, or protections to any user.
+
+10. User Content; Intellectual Property; Confidentiality
+1) User Content is user responsibility. Employers and Agents (and any Validators who publish content) are solely responsible for any User Content they submit or reference, including legality, accuracy, and IP permissions.
2) No IP transfer by default. The Protocol and AGIJobs NFTs do not automatically transfer or license intellectual property rights. Any IP transfer/license must be agreed off-chain between the relevant parties.
3) Public nature of blockchains. On-chain actions are public. URIs and referenced content may be publicly accessible. Do not submit sensitive personal data or confidential information unless you accept that risk and have the rights to do so.
+2) No IP transfer by default. The Protocol and AGIJobs NFTs do not automatically transfer or license intellectual property rights. Any IP transfer/license must be agreed off-chain between the relevant parties.
3) Public nature of blockchains. On-chain actions are public. URIs and referenced content may be publicly accessible. Do not submit sensitive personal data or confidential information unless you accept that risk and have the rights to do so.
+
+11. Prohibited Uses
+You may not use the Protocol to:
- Violate any law or regulation (including sanctions, export controls, labor laws, tax laws, or consumer protection laws).
- Post or perform Jobs involving fraud, theft, violence, doxxing, harassment, malware, exploitation, or rights infringement.
- Circumvent authorization/eligibility mechanisms or use compromised wallets/keys.
- Engage in bribery, collusion, or manipulation of Validator voting or dispute outcomes.
The Owner may maintain blacklists or otherwise restrict participation as permitted by the code. Such actions are discretionary and create no duty.
+- Violate any law or regulation (including sanctions, export controls, labor laws, tax laws, or consumer protection laws).
- Post or perform Jobs involving fraud, theft, violence, doxxing, harassment, malware, exploitation, or rights infringement.
- Circumvent authorization/eligibility mechanisms or use compromised wallets/keys.
- Engage in bribery, collusion, or manipulation of Validator voting or dispute outcomes.
The Owner may maintain blacklists or otherwise restrict participation as permitted by the code. Such actions are discretionary and create no duty.
+
+12. Assumption of Risk (Smart Contract and Crypto Risks)
+You acknowledge and accept, without limitation, the risks of:
- Smart contract bugs, exploits, reentrancy, logic errors, and unforeseen interactions.
- Chain congestion, MEV/front-running, reorgs, downtime, and client bugs.
- Token volatility, illiquidity, and loss of value of $AGIALPHA.
- Validator non-participation, collusion, bribery, or incorrect outcomes.
- Irreversible transactions and the impossibility of guaranteed recovery.
- Loss of private keys or compromised wallets.
+- Smart contract bugs, exploits, reentrancy, logic errors, and unforeseen interactions.
- Chain congestion, MEV/front-running, reorgs, downtime, and client bugs.
- Token volatility, illiquidity, and loss of value of $AGIALPHA.
- Validator non-participation, collusion, bribery, or incorrect outcomes.
- Irreversible transactions and the impossibility of guaranteed recovery.
- Loss of private keys or compromised wallets.
+
+13. Disclaimers; No Warranties
+To the maximum extent permitted by law:
- The Protocol and any related materials are provided "AS IS" and "AS AVAILABLE".
- No warranties are provided, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, security, uptime, or that any particular outcome will be achieved.
- No statement in documentation, interfaces, community channels, or elsewhere creates any warranty or duty.
+- The Protocol and any related materials are provided "AS IS" and "AS AVAILABLE".
- No warranties are provided, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, security, uptime, or that any particular outcome will be achieved.
- No statement in documentation, interfaces, community channels, or elsewhere creates any warranty or duty.
+
+14. Limitation of Liability
+To the maximum extent permitted by law:
- In no event shall the Protocol, its publishers, maintainers, contributors, Owner, Moderators, or any related persons be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or any loss of profits, revenue, data, goodwill, or digital assets, arising out of or related to your use of the Protocol.
- Any liability that cannot be excluded is limited to the minimum amount permitted by law.
All liability for Jobs, deliverables, validation activities, disputes, taxes, and compliance rests exclusively with Employers, Agents, and Validators.
+- In no event shall the Protocol, its publishers, maintainers, contributors, Owner, Moderators, or any related persons be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or any loss of profits, revenue, data, goodwill, or digital assets, arising out of or related to your use of the Protocol.
- Any liability that cannot be excluded is limited to the minimum amount permitted by law.
All liability for Jobs, deliverables, validation activities, disputes, taxes, and compliance rests exclusively with Employers, Agents, and Validators.
+
+15. Indemnification
+To the maximum extent permitted by law, you agree to defend, indemnify, and hold harmless the Protocol, its publishers, maintainers, contributors, Owner, Moderators, and related persons from and against any and all claims, demands, actions, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising out of or related to:
- Your use of the Protocol;
- Any Job you post, perform, validate, approve/disapprove, dispute, or otherwise participate in;
- Any User Content you submit or reference;
- Your breach of these Terms; or
- Your violation of any law or third-party rights.
+- Your use of the Protocol;
- Any Job you post, perform, validate, approve/disapprove, dispute, or otherwise participate in;
- Any User Content you submit or reference;
- Your breach of these Terms; or
- Your violation of any law or third-party rights.
+
+16. Governing Law; Forum; User-to-User Disputes
+1) User-to-user disputes. Any dispute between an Employer, Agent, and/or Validator is strictly between those parties. The Protocol (and its publishers/maintainers/Owner/Moderators) is not a party and shall not be named as such to the extent permitted.
2) Governing law for user-to-user disputes. User-to-user disputes shall be governed by the laws applicable to those users and their off-chain agreement(s), if any.
3) Protocol not subject to jurisdiction. You agree that you will not seek to impose jurisdiction over the Protocol as a party to any user-to-user dispute, to the maximum extent permitted by law.
+2) Governing law for user-to-user disputes. User-to-user disputes shall be governed by the laws applicable to those users and their off-chain agreement(s), if any.
3) Protocol not subject to jurisdiction. You agree that you will not seek to impose jurisdiction over the Protocol as a party to any user-to-user dispute, to the maximum extent permitted by law.
+
+17. Changes to Terms; Continued Use
+- The publisher may publish updated Terms from time to time (including at a canonical URL or IPFS link).
- Continued use of the Protocol after publication of updated Terms constitutes acceptance of those updated Terms to the extent permitted by law.
- Historic on-chain behavior remains governed by the deployed code and the blockchain state.
+- Continued use of the Protocol after publication of updated Terms constitutes acceptance of those updated Terms to the extent permitted by law.
- Historic on-chain behavior remains governed by the deployed code and the blockchain state.
+
+18. Severability; Entire Agreement; No Waiver
+- Severability: If any provision is held invalid or unenforceable, the remaining provisions remain in full force.
- Entire Agreement: These Terms constitute the entire agreement between you and the publisher regarding your use of the Protocol (without affecting any separate agreements between users).
- No Waiver: Failure to enforce any provision is not a waiver.
+- Entire Agreement: These Terms constitute the entire agreement between you and the publisher regarding your use of the Protocol (without affecting any separate agreements between users).
- No Waiver: Failure to enforce any provision is not a waiver.
+
+Regulatory Compliance & Legal Disclosures (Token and Program)
+1) Utility Token Only: $AGIALPHA is intended as a utility token used within an experimental system (including paying for protocol-defined interactions, payouts, and bonds). It is not intended to represent equity, ownership, profit-sharing, or voting rights in any entity.
2) No Expectation of Profit: Any expectation of profit, yield, or return is unjustified.
3) No Guarantee of Value: No party guarantees any value, price stability, or liquidity of $AGIALPHA.
4) Non-Refundable Token Purchases: Where applicable, token acquisitions are final and non-refundable, subject to mandatory consumer laws that cannot be waived.
5) User Compliance Responsibility: Users are solely responsible for ensuring acquisition, holding, and use of $AGIALPHA complies with all laws in their jurisdiction, including securities, commodities, consumer, tax, and AML-related obligations that may apply to them.
+2) No Expectation of Profit: Any expectation of profit, yield, or return is unjustified.
3) No Guarantee of Value: No party guarantees any value, price stability, or liquidity of $AGIALPHA.
4) Non-Refundable Token Purchases: Where applicable, token acquisitions are final and non-refundable, subject to mandatory consumer laws that cannot be waived.
5) User Compliance Responsibility: Users are solely responsible for ensuring acquisition, holding, and use of $AGIALPHA complies with all laws in their jurisdiction, including securities, commodities, consumer, tax, and AML-related obligations that may apply to them.
+
+Research Program Notice; No Warranty
+THIS IS PART OF AN ASPIRATIONAL RESEARCH PROGRAM WITH AN AMBITIOUS RESEARCH AGENDA. ANY EXPECTATION OF PROFIT OR RETURN IS UNJUSTIFIED. POSSESSION OF $AGIALPHA DOES NOT SIGNIFY OR ESTABLISH ANY ENTITLEMENT OR INTEREST, SHARE OR EQUITY, BOND OR ANALOGOUS ENTITLEMENT, OR ANY RIGHT TO OBTAIN ANY FUTURE INCOME. MATERIALS PROVIDED IN THIS SYSTEM ARE WITHOUT WARRANTY OF ANY KIND AND DO NOT CONSTITUTE ENDORSEMENT AND CAN BE MODIFIED AT ANY TIME. BY USING THE PRESENT SYSTEM, YOU AGREE TO THE $AGIALPHA TERMS AND CONDITIONS. ANY USE OF THIS SYSTEM, OR ANY OF THE INFORMATION CONTAINED HEREIN, FOR OTHER THAN THE PURPOSE FOR WHICH IT WAS DEVELOPED, IS EXPRESSLY PROHIBITED, EXCEPT AS AGI.ETH MAY OTHERWISE AGREE TO IN WRITING OFFICIALLY.
OVERRIDING AUTHORITY: AGI.ETH
By interacting with the AGIJobManager smart contract, you acknowledge that you have read, understood, and agree to be bound by these Terms.
--------------------------------------------------------------------------------
+OVERRIDING AUTHORITY: AGI.ETH
By interacting with the AGIJobManager smart contract, you acknowledge that you have read, understood, and agree to be bound by these Terms.
--------------------------------------------------------------------------------
+
+[ R E G U L A T O R Y C O M P L I A N C E & L E G A L D I S C L O S U R E S ]
+Published by: ALPHA.AGI.ETH
Approval Authority: ALPHA.AGI.ETH
Office of Primary Responsibility: ALPHA.AGI.ETH
Initial Terms & Conditions
The Emergence of an AGI-Powered Alpha Agent.
Ticker ($): AGIALPHA
Rooted in the publicly disclosed 2017 "Multi-Agent AI DAO" prior art, the AGI ALPHA AGENT utilizes $AGIALPHA tokens purely as utility tokens—no equity, no profit-sharing—to grant users prepaid access to the AGI ALPHA AGENT’s capabilities. By structuring $AGIALPHA as an advance payment mechanism for leveraging ALPHA.AGENT.AGI.Eth’s AI-driven services, holders likely avoid securities classification complexities. By purchasing these tokens, you gain usage credits for future AI services from the AGI ALPHA AGENT. Instead of representing ownership or investment rights, these tokens simply secure the right to interact with and benefit from the AGI ALPHA AGENT’s intelligence and outputs. This model delivers a straightforward, compliance-friendly approach to accessing cutting-edge AI functionalities, ensuring a seamless, equity-free experience for all participants.
+Approval Authority: ALPHA.AGI.ETH
Office of Primary Responsibility: ALPHA.AGI.ETH
Initial Terms & Conditions
The Emergence of an AGI-Powered Alpha Agent.
Ticker ($): AGIALPHA
Rooted in the publicly disclosed 2017 "Multi-Agent AI DAO" prior art, the AGI ALPHA AGENT utilizes $AGIALPHA tokens purely as utility tokens—no equity, no profit-sharing—to grant users prepaid access to the AGI ALPHA AGENT’s capabilities. By structuring $AGIALPHA as an advance payment mechanism for leveraging ALPHA.AGENT.AGI.Eth’s AI-driven services, holders likely avoid securities classification complexities. By purchasing these tokens, you gain usage credits for future AI services from the AGI ALPHA AGENT. Instead of representing ownership or investment rights, these tokens simply secure the right to interact with and benefit from the AGI ALPHA AGENT’s intelligence and outputs. This model delivers a straightforward, compliance-friendly approach to accessing cutting-edge AI functionalities, ensuring a seamless, equity-free experience for all participants.
+
+1. Token Usage: $AGIALPHA tokens are strictly utility tokens—no equity, no profit-sharing—intended for the purchase of products/services by the AGI ALPHA AGENT (ALPHA.AGENT.AGI.Eth). They are not intended for investment or speculative purposes.
+ +
+
+2. Non-Refundable: Purchases of $AGIALPHA tokens are final and non-refundable.
+ +
+
+3. No Guarantee of Value: The issuer does not guarantee any specific value of the $AGIALPHA token in relation to fiat currencies or other cryptocurrencies.
+ +
+
+4. Regulatory Compliance: It is the user’s responsibility to ensure that the purchase and use of $AGIALPHA tokens comply with all applicable laws and regulations.
+ +
+
+ 5. User Responsibility: Users are responsible for complying with the laws in their own jurisdiction regarding the purchase and use of $AGIALPHA tokens.
+OVERRIDING AUTHORITY: AGI.Eth
$AGIALPHA is experimental and part of an ambitious research agenda. Any expectation of profit is unjustified.
Materials provided (including $AGIALPHA) are without warranty. By using $AGIALPHA, you agree to the $AGIALPHA Terms and Conditions.
Changes to Terms: The issuer may revise these terms at any time, subject to regulatory compliance. Current Terms & Conditions: https://agialphaagent.com/.
THIS IS PART OF AN ASPIRATIONAL RESEARCH PROGRAM WITH AN AMBITIOUS RESEARCH AGENDA. ANY EXPECTATION OF PROFIT OR RETURN IS UNJUSTIFIED. POSSESSION OF $AGIALPHA DOES NOT SIGNIFY OR ESTABLISH ANY ENTITLEMENT OR INTEREST, SHARE OR EQUITY, BOND OR ANALOGOUS ENTITLEMENT, OR ANY RIGHT TO OBTAIN ANY FUTURE INCOME. MATERIALS PROVIDED IN THIS SYSTEM ARE WITHOUT WARRANTY OF ANY KIND AND DO NOT CONSTITUTE ENDORSEMENT AND CAN BE MODIFIED AT ANY TIME. BY USING THE PRESENT SYSTEM, YOU AGREE TO THE $AGIALPHA TERMS AND CONDITIONS. ANY USE OF THIS SYSTEM, OR ANY OF THE INFORMATION CONTAINED HEREIN, FOR OTHER THAN THE PURPOSE FOR WHICH IT WAS DEVELOPED, IS EXPRESSLY PROHIBITED, EXCEPT AS AGI.ETH MAY OTHERWISE AGREE TO IN WRITING OFFICIALLY.
OVERRIDING AUTHORITY: AGI.ETH
+$AGIALPHA is experimental and part of an ambitious research agenda. Any expectation of profit is unjustified.
Materials provided (including $AGIALPHA) are without warranty. By using $AGIALPHA, you agree to the $AGIALPHA Terms and Conditions.
Changes to Terms: The issuer may revise these terms at any time, subject to regulatory compliance. Current Terms & Conditions: https://agialphaagent.com/.
THIS IS PART OF AN ASPIRATIONAL RESEARCH PROGRAM WITH AN AMBITIOUS RESEARCH AGENDA. ANY EXPECTATION OF PROFIT OR RETURN IS UNJUSTIFIED. POSSESSION OF $AGIALPHA DOES NOT SIGNIFY OR ESTABLISH ANY ENTITLEMENT OR INTEREST, SHARE OR EQUITY, BOND OR ANALOGOUS ENTITLEMENT, OR ANY RIGHT TO OBTAIN ANY FUTURE INCOME. MATERIALS PROVIDED IN THIS SYSTEM ARE WITHOUT WARRANTY OF ANY KIND AND DO NOT CONSTITUTE ENDORSEMENT AND CAN BE MODIFIED AT ANY TIME. BY USING THE PRESENT SYSTEM, YOU AGREE TO THE $AGIALPHA TERMS AND CONDITIONS. ANY USE OF THIS SYSTEM, OR ANY OF THE INFORMATION CONTAINED HEREIN, FOR OTHER THAN THE PURPOSE FOR WHICH IT WAS DEVELOPED, IS EXPRESSLY PROHIBITED, EXCEPT AS AGI.ETH MAY OTHERWISE AGREE TO IN WRITING OFFICIALLY.
OVERRIDING AUTHORITY: AGI.ETH
+
+
+ Contact & Legal
+The full Terms & Conditions are embedded above for easier reading. This footer keeps the public contact and external legal reference links handy.
+
+