19 Loops That Prove the Point
Games, agents, DeFi, AI — every contract here structurally requires a neutral keeper. Each fails the self-trigger test for a different reason.
CrumbleCore
AutoLoop + VRFGameA persistent decay tower where each floor takes autonomous VRF damage every tick. Floors degrade passively and can collapse permanently.
Why AutoLoop Is Required
Inverted self-interest: nobody wants to trigger a loop that might damage their own floor. Self-incentivized triggering fails because the loop imposes a cost on every participant.
What It Proves
A neutral keeper is the only viable operator when the loop hurts every player
Gladiator Arena
AutoLoop + VRFGameAlways-on colosseum where bouts resolve on a fixed schedule. Gladiators take wounds every bout. VRF-weighted winner selection based on vitality.
Why AutoLoop Is Required
Negative-EV free-rider: every entrant takes wounds, only one wins. Rational gladiators wait for someone else to pay gas. Timing control would also let entrants cherry-pick favorable VRF reveals.
What It Proves
Games with negative expected value per tick cannot rely on player-triggered loops
Mech Brawl
AutoLoop + VRFGameIron-pit brawls where mechs clash on a fixed schedule. Hull takes damage every brawl. VRF-weighted winner selection based on remaining armor.
Why AutoLoop Is Required
Negative-EV free-rider: every entrant takes hull damage, only one wins. Rational pilots wait for someone else to pay gas. Timing control would let entrants manipulate VRF reveal windows.
What It Proves
Attrition mechanics guarantee that no rational player wants to self-trigger
Sorcerer Duel
AutoLoop + VRFGameArcane circle duels where sorcerers compete on a fixed schedule. Mana drains every duel. VRF-weighted winner selection based on remaining mana.
Why AutoLoop Is Required
Negative-EV free-rider: every duelist loses mana, only one wins. Rational sorcerers wait for someone else to pay gas. Timing control breaks the arcane circle's fairness guarantees.
What It Proves
Resource-drain mechanics require a neutral keeper to fire each tick
Kaiju League
AutoLoop + VRFGameMonster-league clashes where kaiju battle on a fixed schedule. Health degrades every clash. VRF-weighted winner selection based on remaining health.
Why AutoLoop Is Required
Negative-EV free-rider: every entrant takes damage, only one wins. Rational trainers wait for someone else to pay gas. Timing control would let trainers avoid unfavorable VRF seeds.
What It Proves
Health-attrition games are structurally incompatible with self-triggered loops
Void Harvester
AutoLoop + VRFGameDeep-anomaly missions where probes launch on a fixed schedule. Integrity decays every mission. VRF-weighted winner selection based on remaining integrity.
Why AutoLoop Is Required
Negative-EV free-rider: every probe loses integrity, only one wins the anomaly haul. Rational operators wait for someone else to pay gas. Timing control enables front-running on VRF outcomes.
What It Proves
Degradation mechanics make autonomous scheduling the only fair design
SponsorAuction
AutoLoopGameA rolling ascending-bid auction with autonomous close. No VRF at all. When one auction closes, the next opens in the same transaction.
Why AutoLoop Is Required
Timing-as-attack-surface: the high bidder wants immediate close, counter-bidders want extension, the slot receiver wants peak-bid close. No player-controlled trigger is fair.
What It Proves
AutoLoop's value extends beyond randomness into fair scheduling
GladiatorOracle
Cross-contractGameA commit-reveal prediction market layered on top of GladiatorArena. Players predict which gladiator wins the next bout, commit secretly, reveal, and split the pot.
Why AutoLoop Is Required
Cross-contract coordination: settlement requires both the reveal window to close AND GladiatorArena's bout to resolve. A player could fire settlement the instant the bout resolves, before all reveals are in.
What It Proves
Commit-reveal across two contracts is impossible to schedule fairly without a neutral keeper
OracleRun
AutoLoop + VRFGameA permadeath dungeon crawl. Characters roll against VRF-derived difficulty each floor. Survivors split the prize pool. Dead characters are permanent.
Why AutoLoop Is Required
Mempool-snoop attack: a player-controlled trigger lets the caller compute VRF outcomes before submitting and only proceed when favored. A neutral schedule fires for everyone simultaneously.
What It Proves
Escalating difficulty creates stalling incentives that only a neutral keeper resolves
KaijuOracle
Cross-contractGameA commit-reveal prediction market layered on top of KaijuLeague. Players predict which kaiju wins the next clash, commit secretly, reveal before the clash resolves, and split the pot.
Why AutoLoop Is Required
Cross-contract dual-gate: settlement requires the reveal window to close AND KaijuLeague's clash to be resolved. A player could fire settlement the instant the clash resolves, skipping reveals.
What It Proves
Commit-reveal integrity across two contracts is impossible without a neutral keeper
ForecasterLeaderboard
3-contract chainGameThird hop in the KaijuLeague → KaijuOracle → ForecasterLeaderboard chain. Scores prediction accuracy across oracle rounds and distributes a weekly prize pool to top forecasters.
Why AutoLoop Is Required
Four independent coordination failures: adversarial distribution timing, 3-hop cross-contract dependency, free-rider on processing gas, and prize-pool timing attack. No player-controlled trigger solves all four simultaneously.
What It Proves
A 3-contract coordination problem spanning VRF, prediction markets, and leaderboards requires a single neutral keeper across all hops
Vault Dead Switch
AutoLoopAgentTransfers your vault to a designated beneficiary if you miss a check-in within a configurable window. Trustless estate planning — no operator, no custodian.
Why AutoLoop Is Required
Nobody should hold a dead man's trigger. The whole point of the contract is that no human controls when it fires. A player-controlled trigger defeats the purpose entirely.
What It Proves
Conditional transfers that depend on inaction are structurally impossible to self-trigger
Yield Harvester
AutoLoopAgentCompounds a yield position on a configurable schedule. Calls harvest() on a vault, reinvests proceeds, emits a harvest event. No manual intervention required.
Why AutoLoop Is Required
Whoever triggers the harvest can front-run it — watching the mempool, computing the output, and sandwiching the transaction. A neutral, pre-scheduled keeper removes that attack surface.
What It Proves
DeFi automation with timing-sensitive outputs requires a keeper no participant can exploit
AI Agent Loop
AutoLoopAgentFires an on-chain AgentTick event on a neutral schedule. Off-chain AI workers listen, run inference, and submit signed actions. The loop itself is just scheduling — the intelligence lives off-chain.
Why AutoLoop Is Required
The agent's operator, its users, and its competitors all have conflicting interests in when it fires. A neutral schedule removes timing as an attack surface for any on-chain AI system.
What It Proves
On-chain AI agent execution needs a neutral scheduling layer nobody controls
DAO Executor
AutoLoopAgentExecutes queued governance proposals after their timelock expires, on an autonomous schedule. No member needs to manually execute — and no member should control when they do.
Why AutoLoop Is Required
Any DAO member who controls execution timing can front-run the proposal's on-chain effects. A neutral keeper fires execution the moment the timelock clears, with no human in the loop.
What It Proves
Governance execution is a timing-as-attack-surface problem, not just an automation convenience
Treasury Rebalancer
AutoLoopAgentMonitors a multi-token treasury against target weights and emits a RebalanceRequired event when drift exceeds a threshold. Off-chain executors act on the signal.
Why AutoLoop Is Required
Whoever triggers a rebalance knows the exact swap in advance and can front-run it. An autonomous, scheduled check-and-signal pattern separates detection from execution and removes the front-running surface.
What It Proves
Treasury management loops with predictable swap impacts cannot be safely self-triggered
Airdrop Distributor
AutoLoop + VRFAgentDraws N winners from a registered address pool using VRF on an autonomous schedule. Winner selection is provably fair and unmanipulable by any participant.
Why AutoLoop Is Required
If player-controlled, the trigger holder computes who wins before submitting and only calls when favorable. VRF + neutral scheduling removes both the front-running and the selection bias.
What It Proves
Any selection event with real value attached cannot be safely triggered by a participant
NFT Reveal
AutoLoop + VRFAgentAutonomously reveals NFT traits after a mint closes. VRF seeds trait assignment for all unrevealed tokens in one transaction, on a pre-committed schedule.
Why AutoLoop Is Required
If the reveal is player-triggered, the triggerer computes all trait assignments before calling. They proceed only when holding rare tokens and delay when holding commons. VRF + AutoLoop makes that attack impossible.
What It Proves
NFT reveal timing is an attack surface when any token holder controls it
Lottery Sweepstakes
AutoLoop + VRFAgentA recurring draw where depositors enter a prize pool and VRF selects one winner per round on an autonomous schedule. Rounds run back-to-back automatically.
Why AutoLoop Is Required
Identical to CrumbleCore's inverted self-interest, applied to finance: every depositor wants someone else to trigger the draw (in case VRF picks them), but nobody will. A neutral keeper is the only way the lottery runs.
What It Proves
Financial lotteries face the same structural self-trigger failure as attrition games
Runs on Sepolia testnet and local Anvil. No real ETH required.