AI flow generationLive
Schema-constrained intent
Natural language becomes a capability-bound graph. Unknown nodes and fields are rejected before editor state changes.
Uniswap v4 · visual hook studioDescribe the hook.
Describe the hook.
Ship the evidence.
hooked on eth. turns natural-language intent into a validated visual workflow, deterministic Solidity, and an explicit wallet-controlled deployment. AI proposes—typed systems decide, and your wallet signs.
v4-nativedeterministic Soliditypermission-awareCREATE2-readywallet-controlled
HOOKED / VOLUME-FEE.flowValid
TriggerBefore Swapconfigured
ConditionVolume Threshold24h · > 1,000,000
ActionDynamic Feeconfigured
ActionTreasury Split10% · explicit dest
Graph · permissions · accounting validatedDSL v3
A constrained path from idea to deployment evidence.
Each stage consumes a typed artifact from the stage before it. AI proposes intent; it never becomes the compiler or the deployment authority.
01Natural languageState behavior in plain language; unsupported capabilities get an explicit refusal.Available
02Validated Hook DSLSchema-constrained intent, checked with Zod at client and server boundaries.Available
03Visual workflowA capability-bound graph of triggers, conditions, and actions.Available
04Deterministic SolidityVersioned templates lower the validated DSL into reproducible source.Available
05Compile & testsFoundry builds run in an isolated worker; diagnostics are retained.Available
06Automated checksStatic source rules and Slither report findings—without audit claims.Available
07SimulationDeterministic swap and liquidity scenarios with explicit inputs.Available
08CREATE2 miningMine a salt whose address encodes the derived permission bitmap.Available
09Ethereum mainnet deploymentThe connected wallet reviews and signs an evidence-gated mainnet plan.Evidence-gated
Built around the realities of PoolManager.
Callbacks, permissions, accounting, evidence, and deployment constraints are modeled as separate domain boundaries—not glued together by a prompt.
Visual node editorLive
Build, connect, inspect
Edit v4 lifecycle logic visually, with graph and permission errors surfaced as you work—not after you compile.
Permission derivationLive
Bits from behavior
Callback and return-delta bits derive from reachable behavior in the graph, never from hand-set flags.
Deterministic generationLive
Reproducible Solidity
Versioned templates lower validated DSL into source you can regenerate byte-for-byte. No authoritative AI-written Solidity.
Foundry evidenceLive
Isolated build workers
Compile, test, and retain diagnostics outside the frontend process, with hard resource limits on every job.
Automated checksLive
Findings, not claims
Static source rules and Slither report known risk classes. They never replace an independent audit.
Scenario simulationLive
Deterministic scenarios
Run swap and liquidity scenarios with explicit inputs before anything touches a network.
CREATE2 miningLive
Address-encoded permissions
Mine a salt whose deployed address encodes the derived permission bitmap, exactly as v4 requires.
Mainnet deploymentEvidence-gated
The wallet decides
Source identity, permissions, salt, address, findings, and network are shown before your wallet signs anything.
Versioning & exportLive
Immutable revisions
Every revision is preserved. Export a standalone Foundry project with pinned Uniswap dependencies at any point.
Volume-aware fees, without imaginary protocol features.
“Raise swap fees when rolling 24-hour volume exceeds $1M and route 10% of a separately disclosed hook charge to treasury.”
CallbackBefore SwapPoolManager entrypoint
→Hook state24h VolumeRolling, hook-maintained
→Separate pathsFee + accrualLP revenue stays LP revenue
Treasury accounting is a separate hook-owned charge—dynamic LP fees are never touched.
The treasury destination must be supplied explicitly; nothing is inferred.
Return-delta accounting receives additional review gates before deployment.
A clear artifact at every step.
Nothing silently jumps from a prompt to a wallet transaction.
Describe
State the behavior in plain language. Unsupported capabilities return an explicit response, not a guess.
Design & validate
Review the generated nodes, edit parameters, and resolve graph or permission errors in the editor.
Build & test
Generate reproducible source, compile it, and inspect deterministic test and check evidence.
Review & deploy
Confirm address bits, salt, bytecode, and risks on Ethereum mainnet—before the wallet signs.
The model proposes. Typed systems decide.
A strict JSON DSL is the contract between natural language, the editor, protocol validation, generation, simulation, and deployment planning.
- [x]Strict JSON DSL between every stage
- [x]Zod at client and server boundaries
- [x]Permission bitmap derivation
- [x]Pinned Uniswap dependencies
- [x]Standalone Foundry export
- [x]No authoritative AI-written Solidity
VOLUME-FEE.hook.jsonSCHEMA v3 · VALID
// lowered deterministically — never hand-written by the model
{
"callbacks": ["beforeSwap", "afterSwap"],
"nodes": [
{ "type": "trigger", "subtype": "beforeSwap" },
{
"type": "condition",
"subtype": "volumeThreshold",
"config": {
"source": { "type": "hookState" },
"windowSeconds": 86400
}
}
]
}Financial actions stay human-controlled.
No private-key custody
hooked on eth. never requests or stores private keys or seed phrases. Ever.
Wallet-side signing
Authentication and deployment confirmations happen in the connected wallet.
AI cannot deploy
AI proposes workflows. It cannot sign, broadcast, or silently change destinations.
Schema-constrained output
Unknown nodes and fields are rejected before editor state changes.
Isolated build workers
Compiler and analysis jobs run outside the frontend process with hard limits.
Explicit review
Source identity, permissions, salt, address, findings, and mainnet are shown first.
NoteAutomated checks help identify known classes of risk. They do not replace an independent smart-contract audit.
Start from a disclosed pattern.
Templates are workflow starting points—not claims of compilation, review, or deployment.
hooked on eth.
Turn your hook idea into a reviewable workflow.
Start in demo mode. Connect a wallet only when identity or deployment requires it.
Start in Demo ModeNo wallet required · no signup · mainnet-deployable output