Some Loops Shouldn't Have an Owner

When triggering a loop hurts you, benefits your opponent, or creates a fairness attack surface — you need a neutral keeper. AutoLoop runs the loops nobody should control.

11
Demo Games Live
0
Extra Tokens Needed
3 Modes
Standard · Hybrid · Full VRF

Games for Pennies

Standard
$0.0080
per tick · ~90k gas
Hybrid VRF
$0.0094
per tick · ~105k gas
Full VRF
$0.022
per tick · ~240k gas
Live on Ethereum
|Etherscan ↗
Why AutoLoop

Built for Loops That Can't Self-Trigger

Chainlink Automation works when someone benefits from triggering. AutoLoop exists for the structural cases where nobody does.

Neutral Keeper Execution

A worker fleet with no stake in any game's outcome. When your loop damages a random player on every tick, you need a keeper who doesn't care who wins — and won't stall or collude.

On-Chain ECVRF Verification

Native ECVRF proof generation and trustless on-chain verification. Provably fair randomness on every tick — the proof is verified by the contract itself, not trusted from a third-party oracle service.

Hybrid VRF — Randomness When You Need It

Standard-cost ticks with VRF only when your contract requests it. Your game decides when randomness matters — loot drops, critical hits, spawns — and pays VRF gas only on those ticks.

Fee-on-Execution Model

Pay only when loops actually run. Gas reimbursement plus a small base fee split between protocol and controllers. Transparent and predictable.

Developer Friendly

Simple functions, direct hooks. Sample contracts included.

Multi-Network Ready

Deploy on Ethereum mainnet, Sepolia testnet, or local Anvil for development. Configurable per-network with automatic deployment tooling.

Permissioned & Secure

Role-based access control ensures only registered controllers can trigger loops. On-chain VRF verification prevents manipulation.

19 Demo Contracts

Every Loop Here Fails the Self-Trigger Test

Games, agents, DeFi, AI — each for a different structural reason. Not design choices. Proofs.

🏗️
CrumbleCoreVRFGame

Inverted self-interest

Every VRF tick picks a random floor and damages it. No floor owner will ever trigger the loop — it might hit their own asset. A neutral keeper is the only viable operator.

🔒
Vault Dead SwitchNo VRFAgent

Nobody should hold the trigger

A dead man's switch that transfers your vault to a beneficiary if you miss a check-in window. The whole point is that no human should control when it fires.

🎟️
Airdrop DistributorVRFAgent

Front-running attack surface

VRF selects winners from a registered pool on schedule. If player-controlled, the trigger holder knows who wins before calling. AutoLoop fires first, asks questions never.

🔨
SponsorAuctionNo VRFGame

Timing as attack surface

The high bidder wants the auction closed now. Counter-bidders want an extension. No player-controlled trigger is fair — proving the problem extends far beyond randomness.

🏆
ForecasterLeaderboard3-contract chainGame

4-way coordination failure

Third hop in KaijuLeague → KaijuOracle → ForecasterLeaderboard. Adversarial timing, cross-contract dependency, free-rider gas, prize-pool timing attack — no single player resolves all four.

🤖
AI Agent LoopNo VRFAgent

Neutral on-chain schedule

An LLM agent that runs off-chain and acts on-chain every N blocks. The agent itself shouldn't decide when it fires — its operator, users, and rivals all have conflicting interests.

Integration

Up and Running in 4 Steps

From contract to automated game loop in minutes, not months.

01

Inherit

Extend one of three base contracts:

  • AutoLoopCompatible — pure automation
  • AutoLoopHybridVRFCompatible — selective randomness (loot, crits, spawns)
  • AutoLoopVRFCompatible — randomness on every tick
02

Implement

Add shouldProgressLoop() to signal readiness and progressLoop() to execute your game logic.

03

Register & Fund

Register your contract on-chain and deposit ETH to cover gas and fees.

04

Let It Run

Workers automatically detect and execute your loops. Sit back and watch your game come alive.

Cost Breakdown

See the Details

Gas comparisons, example sessions, and fee structure — everything you need to budget your automation.

Fee Breakdown

Gas reimbursement + buffer
70% base fee (of gas cost)
50% of base fee to controller
50% of base fee to protocol
Gas
+
Base Fee
=
Controller
+
Protocol
Code

Simple by Design

Smart contracts, TypeScript SDK, and AI-native MCP tools — everything you need to build.

NumberGoUp.sol
1// SPDX-License-Identifier: MIT
2pragma solidity ^0.8.13;
3
4// Import the base contract that makes any
5// contract compatible with AutoLoop workers
6import {AutoLoopCompatible} from
7 "autoloop/AutoLoopCompatible.sol";
8
9// A simple demo: number goes up every interval
10contract NumberGoUp is AutoLoopCompatible {
11 uint256 public number;
12 uint256 public interval;
13 uint256 public lastTimeStamp;
14 uint256 private _loopID;
15
16 constructor(uint256 _interval) {
17 interval = _interval;
18 lastTimeStamp = block.timestamp;
19 }
20
21 // Workers call this every block to check
22 // if the contract is ready for an update
23 function shouldProgressLoop()
24 external view override
25 returns (
26 bool loopIsReady,
27 bytes memory progressWithData
28 )
29 {
30 // Ready when enough time has passed
31 loopIsReady =
32 (block.timestamp - lastTimeStamp) > interval;
33 // Pass loop ID to prevent duplicate runs
34 progressWithData = abi.encode(_loopID);
35 }
36
37 // Called by AutoLoop when shouldProgressLoop
38 // returns true — this is your update logic
39 function progressLoop(
40 bytes calldata progressWithData
41 ) external override {
42 uint256 loopID =
43 abi.decode(progressWithData, (uint256));
44 // Guard against stale or replayed calls
45 require(loopID == _loopID, "stale loop");
46 lastTimeStamp = block.timestamp;
47 ++number;
48 ++_loopID;
49 }
50}
AutoLoop
vsChainlink

See How We Compare to Chainlink

Three automation modes — Standard, Hybrid VRF, and Full VRF — all in one protocol. No separate subscriptions. Cheaper than Chainlink in every tier.

~55%cheaper per execution
0extra tokens needed
HybridHybrid VRF when you need it
Compare the Numbers
FAQ

Common Questions

AutoLoop is currently unaudited. We're transparent about this — it's an early-stage protocol. A formal security audit is on the roadmap. In the meantime, all contracts are open-source on GitHub, use battle-tested OpenZeppelin libraries, and have comprehensive test coverage. We recommend starting on Sepolia testnet before deploying to mainnet.Read the testing guide
AutoLoop runs a fleet of redundant workers. If one goes down, the others continue executing loops. The worker network is permissionless — anyone can run a worker and earn controller fees. There's no single point of failure. You can check live worker status at /status anytime.Learn about the architecture
Chainlink Automation works well when triggering is self-incentivized — liquidations, arbitrage, fee collection. AutoLoop exists for a different class of problem. If every tick of your game hurts every player (attrition mechanics), no rational player will ever pay to trigger the loop — it simply stops. If trigger timing is itself an attack surface (commit-reveal prediction markets, auction closes, cross-contract settlement), a player-controlled keeper breaks game fairness by design. AutoLoop's neutral, autonomous schedule solves these structural problems that self-incentivized triggering cannot. It's also cheaper per execution than Chainlink and pays in ETH with no LINK conversion overhead — but those are secondary benefits.See the full comparison
Costs depend on gas prices, but a standard tick is fractions of a cent. Use the pricing calculator for exact numbers at current rates. VRF ticks cost more due to proof verification, but Hybrid VRF lets you use cheap standard ticks most of the time and only pay VRF prices when randomness is needed.Full cost breakdown
AutoLoop is live on Ethereum mainnet and Sepolia testnet. Base, Arbitrum, and Polygon support are planned. The protocol is chain-agnostic by design — the same contracts and worker infrastructure can deploy to any EVM chain.
Yes. The worker is open-source and permissionless. You can run your own worker fleet, earn controller fees for executing loops, and maintain full control over your infrastructure. See the worker repository on GitHub for setup instructions.Worker setup guide