Skip to content

Arcron

Smart contracts
can't wake themselves up.

Algorand runs your code when somebody sends a transaction, and never otherwise. Arcron is the somebody. Escrow a fee against a schedule, and any account on the network can earn it by making the call on time.

Open the console → Read the docs Read the registry on-chain ↗

alpha · TestNet only · unaudited. Still upgradeable until its creator calls freeze, so the programs can still be replaced. This deployment may be replaced at any time. Do not escrow anything you would mind losing. The Connect hub is MainNet; a MainNet session there will not pay keepers here.

How it works

  1. You register an upkeep

    An app to call, how often, and what you will pay per execution. The fee is escrowed on registration, and stays your money until somebody earns it.

  2. Anybody executes it

    When an upkeep comes due, any account may call execute. There is no keeper allowlist, no stake, and no registration. First to arrive is paid, and losing costs nothing: Algorand rejects a failing transaction at validation, so it never enters a block and no fee is charged.

  3. The escrow pays out atomically

    Your call and the keeper's payment settle in one transaction, so an execution that fails pays nobody. Neglected upkeeps escalate their fee toward a cap you set, which is how a schedule nobody wants becomes one somebody does.

No token is required. Fees are always paid in ALGO; an upkeep may add an ASA bonus on top of that fee, which lets a project reward keepers in its own currency without ever making one a requirement.

Running on TestNet

Recorded from the chain on August 27, 2026, at round 66,706,209. Every number below is one you can check yourself.

Upkeeps registered
11
Executions delivered
62
Held in escrow
3.521 ALGO
Contract
2,219 bytes
The upkeeps registered on the TestNet keeper app at the time of the snapshot
Upkeep Every Fee (ALGO) Escrow (ALGO) Runs funded Executed
#18 70 s 25 rounds 0.004 0.00 0 20
#19 12.0 h 15,428 rounds 0.004 0.112 28 2
#20 12.0 h 15,428 rounds 0.004 0.112 28 2
#21 12.0 h 15,428 rounds 0.004 up to 0.012 when late 0.168 41 2
#22 12.0 h 15,428 rounds 0.004 0.112 28 2
#23 28 s 10 rounds 0.004 0.00 0 5
#51 28 s 10 rounds 0.004 0.00 0 4
#52 28 s 10 rounds 0.004 up to 0.012 when late 0.002 0 5
#71 10 min 214 rounds 0.004 0.032 8 16
#73 60 min 1,286 rounds 0.004 0.988 247 3
#76 2.0 h 2,571 rounds 0.004 1.996 499 1

The app account can pay out every ALGO it holds in escrow.

Contract c94c6e0cc561… is the same hash verify_build prints, so a deployment can be tied to a commit without taking anyone's word for it.

Where it is

A deployment is upgradeable until its creator calls freeze, and frozen is permanent. Each stage answers one question: what is settled, and what is at stake if it is wrong?

  1. alpha now

    Nothing frozen. Nobody but us affected. The deployment may be replaced for any reason.

  2. beta

    The struct and the call surface freeze. From then on a change means a new app and every creator re-registering by hand.

  3. rc

    The exact bytecode intended for MainNet, unchanged for a fixed period. Any change resets the clock.

  4. MainNet

    The same bytecode, real money, and a decision about freeze recorded either way before it ships. Still unaudited: shipping says we believe it is right, not that anyone certified it.