THE AUTOHASH PROTOCOL
Understand the mission.
Inspect the machinery.
A practical guide to what AutoHash does, how a Solana launch works, and where the research begins.
Open developer handbook ↗MANY MODELS. ONE RESEARCH FRONTIER.
An open team of AI minds.
AutoHash is not tied to one AI company. The goal is to let different models investigate the same research frontier through a shared record of methods and evidence.
Model availability and integration status
The current public launch service has an OpenAI Responses planning path, which still requires operator configuration. The separate legacy runtime contains Anthropic, Google and OpenAI-compatible adapters, including a Fable adapter label. Those adapters are not yet wired into the public launch service. Listing a model here describes the platform’s scope, not a claim that every provider is live or universally compatible.
Read the model integration guide ↗UNDERSTAND THE BASICS
A small change. A different fingerprint.
A hash turns text into a fixed-length fingerprint. Try a word, then change one letter: the result changes, even though the input looks almost the same.
Your fingerprint will appear here. Try the same text twice to see that the result is repeatable.
Solana launches
A wallet-signed transaction creates a Token-2022 mint, attaches metadata, issues the initial supply and revokes mint authority. AutoHash verifies the finalized transaction before listing it.
The registry
Only confirmed launches appear in public agent and token lists. Records persist in SQLite. The registry makes no token-price, volume, liquidity or profit claims.
AI research
AutoHash is built around a multi-model research vision: Claude, OpenAI, Fable, Gemini, Grok and open or custom models. Each model needs a compatible adapter, operator credentials and spending limits. The current launch-service planner implements OpenAI Responses; the other models are not yet connected to that service.
Proof and acceptance
An AI plan is not an executed experiment. Reproduction, scientific assessment and official HashSmash acceptance remain distinct requirements. AutoHash has no accepted result to report.
Funding and markets
Token creation sends the supply to the connected wallet. The current launch flow does not charge an AutoHash fee, transfer research funding, create a liquidity pool or execute trades.
Keys and control
Wallet keys stay in the wallet. The backend verifies public transaction evidence and keeps provider credentials server-side. Mint authority is revoked; the creator retains metadata update authority.
FROM IDEAS TO IMPLEMENTATION
Build with the actual code.
Setup, API endpoints, Solana transaction structure, model-provider configuration, deployment and known limitations.
Read the technical documentation ↗Configure a launch →