logochainflowLaunch App
Natural-language on-chain automation

Say it. Simulate it. Send it.

Describe a transfer in one sentence. It simulates it, shows you exactly what will happen, and sends nothing until you say so.

No wallet to connect · Testnet only · Gas sponsored

How it works

Three steps to your first automation

  1. Describe your rule

    Write what you want in plain English. ChainFlow parses your intent into a structured on-chain rule.

  2. Review the interpretation

    See exactly what will happen — recipient, amount, network, trigger — before anything touches the chain.

  3. Confirm and execute

    One click. KeeperHub executes the automation on testnet. You get a transaction hash and explorer link as proof.

chainflow · sepoliaidle
>"Send 0.01 ETH to 0xd210…A7A1 every 24 hours"
✓Parsed: transfer · 0.01 ETH · 0xd210…A7A1 · every 24h
✓Simulated: will not revert · gas sponsored
✓Executed: 0x5b67…e471 · confirmed on Etherscan
Safety

What ChainFlow will never do

This is a testnet tool with a KeeperHub-managed account behind it. Here is exactly where the boundaries sit, and what enforces each one.

  • Testnet only

    Every execution targets Ethereum Sepolia. There is no mainnet code path to fall back to.

    chain 11155111
  • No wallet connection

    ChainFlow never asks you to connect a wallet or sign anything. Transfers run from a KeeperHub-managed account, server-side.

    no signature request
  • Nothing runs unconfirmed

    Each rule is simulated first, then waits behind a two-step confirmation that restates the amount before it broadcasts.

    simulate → confirm → broadcast
  • Proof, or it doesn't claim success

    A receipt only reads confirmed when a transaction hash exists to back it. No hash, and it says awaiting hash instead.

    hash-gated status
  • Gas is sponsored

    KeeperHub covers the gas for every execution. Nothing to fund, no balance to top up, no cost to you.

    sponsored by KeeperHub
Things you can say

Sentences that already work

Every line below parses as written. Pick one and it lands in the composer, ready to review.

Balance and schedule triggers are parsed and recorded. Execution runs on your confirmation — ChainFlow does not yet poll for triggers on its own.

One sentence. One confirmation. One hash.

You have seen what it does and where the edges are. The rest takes about a minute.

No wallet to connect · Testnet only · Gas sponsored