Coins with rules.
Subscriptions you can actually cancel.
The film and its cuts are CC BY 4.0: share, re-cut or translate them, credit Swift Bot Labs. Code MIT, music and sounds CC0.
The full film (63 s)
A one-minute vertical film. A card on file lets a company pull any amount. Bitcoin Cash only moves money when you push it, which is safe but means paying every bill by hand. The film shows the third way: the coins carry the rules. Lock a budget in a small contract that lets the merchant take one period's amount per period, never more and never early. Anyone can trigger the payment, the network refuses an early one, and you can cancel and get the rest back. It ends on the idea; the app is credited in small print on the last frame.
Captions are burned in. Everything in this film (and its 17 s cuts) is either an illustration (labelled), a diagram of the contract's rules, or data from our mainnet run on 16 Nov 2026; it uses no test-network footage.
Separate from this film, not part of the Media entry: a 113 s product walkthrough of the app on chipnet (test coins), standing-order.mp4.
New to Bitcoin Cash? Get a wallet at bch.info
Then try the idea itself on mainnet: a 1-cent plan, cancel any time.
Transcript
- 0:00
- You cancelled it in March. It charged you again in April. (on screen: “Subscription cancelled”, “Card charged $19.99”, a reply “I. CANCELLED. THIS.”, labelled illustration)
- 0:05
- That’s how cards work. Whoever has your number can pull any amount, any time.
- 0:10
- Bitcoin Cash works the other way round. Nothing leaves your wallet unless you send it. Safe, but then you’d have to pay every bill by hand.
- 0:20
- Unless the coins carry the rules themselves. Lock a budget in a small contract that says: the merchant may take this much, once a month. Never more. Never early.
- 0:32
- Anyone can trigger the payment. The merchant, a bot, even you. It still pays one month, and only to the merchant. (on screen: “only to the payees you agreed to at sign-up: the merchant, plus an optional split”)
- 0:40
- Try to take it early, and the network refuses. We tried it on mainnet, with a ten-minute period instead of a month. (on screen: our 16 Nov mainnet run, below, and “Test period: 1 block (about 10 min). A real plan uses one month. Same rule, longer wait.”)
- 0:48
- Changed your mind? Cancel, and everything left comes straight back to you.
- 0:53
- No card on file. No company holding your money. Just coins with rules, on Bitcoin Cash. (on screen: the seven mainnet transactions, “Coins with rules.”, and a credit line: the app in this film is Standing Order)
It runs on mainnet: the whole run, refusals included
16 Nov 2026, real BCH, blocks 977,561 to 977,564. The order pays 10,000 sats a block to the merchant and 1,000 to a split payee. Seven transactions went on chain. Ten claim attempts were refused (6 before the funding was a block deep, 1 right after the resume, 3 right after the top-up: every move of the order coin restarts its period); a refused transaction never spreads, so it has no txid. Every line below is in the run log.
| Time (UTC) | Step | Result |
|---|---|---|
| 03:06:36 | subscribe: fund the order with 60,000 sats | a813b51e…0efd · block 977,561 |
| 03:06:44, 03:08:53, 03:11:01, 03:13:08, 03:15:17, 03:17:25 | claim before the funding was one block deep (6 tries, 2 minutes apart) | refused by the network: “non-BIP68-final (code 64)”, each time |
| 03:19:35 | claim | 83989cdd…7aa0 · block 977,563 · 10,000 merchant + 1,000 split, 47,000 stays in the order |
| 03:20:04 | pause (pays the period in progress first) | 57dbfffb…f07d · 10,000 + 1,000 paid, 36,000 to the paused covenant |
| 03:20:34 | resume | 3cfa46b1…7b4e · 36,000 back in the order |
| 03:21:03 | claim right after the resume (1 try) | refused by the network: “non-BIP68-final (code 64)”: the resumed coin is new, so its period starts again |
| 03:21:33 | top up with 26,000 sats (pays the period in progress first) | f56cc629…f68e · 10,000 + 1,000 paid, order now 49,000 |
| 03:21:43, 03:23:51, 03:25:59 | claim right after the top-up (3 tries) | refused by the network: “non-BIP68-final (code 64)”, each time: the topped-up coin is new |
| 03:28:10 | claim | bcbd439c…a7e3 · block 977,564 · 10,000 + 1,000 paid, 36,000 left |
| 03:28:40 | cancel | a68c39cb…e9f9 · the 36,000 left goes back to the subscriber |
How anyone can check the “never early” rule without trusting our log
The accepted claim 83989cdd…
is a version-2 transaction whose only input (the order coin from a813b51e…:0)
has sequence number 1: under BIP68 that is a relative lock of one block, so no node accepts it until the coin is a block deep.
The contract demands it (require(this.age >= period)):
without the lock, the claim would fail the contract instead. The funding confirmed in block 977,561 (03:17:57 UTC); the claim was
mined in block 977,563. Every claim attempt before that was refused, as the table shows.
Sources for what you see
| On screen | Source |
|---|---|
| 03:06:44 UTC: a claim one block early, refused by the network | The node’s reply in our run log: “non-BIP68-final (code 64)” (log excerpt). A refused transaction never reaches the chain, so there is no txid; the public check is the accepted claim’s one-block relative lock, explained above. |
| 03:19:35 UTC: the claim after one block, accepted; block 977,563; 10,000 sats to the merchant | 83989cdd…7aa0 (outputs 10,000 to the merchant, 1,000 to the split payee, 47,000 back into the contract) |
| Cancel: the rest comes straight back (36,000 sats) | a68c39cb…e9f9: the contract’s 36,000 sats back to the subscriber |
| “Anyone can trigger the payment” | claim() takes no signature; its outputs are fixed by the contract (standing_order_plus.scash). Our relayer is one such trigger; the merchant or the subscriber can be another. |
| “Never early” | require(this.age >= period), a relative timelock every node enforces |
| “Once a month” | The period is a contract parameter in blocks (1 to 65,535). Our mainnet test used one block (about ten minutes) so it could run in half an hour; the film says so in the voice and on screen. |
| The card, the $19.99 charges, the 12 months of payments | Illustrations, labelled in the film |
Media track rules (quoted from the DoraHacks detail page, 16 Nov 2026)
“Builders are welcome to make a submission in both the Mainnet & Media track. They are not mutually exclusive!”
“Submit a piece of inspirational, innovative or engaging BCH media - of any kind” · “AI-created or assisted art of any kind” is allowed.
Prize: “$1 000 PUSD to the best submission” · Judging: “Purely up to Jeremy’s judgement ... highly engaging & with potential to go viral, hopefully creating user education & interest in BCH”.
A real claim pushed by a public tool, not by us
17 Nov 2026: a signature-free claim was pushed through Blockchair’s public push-transaction API, not our relayer or our code: cba7e44a…b1be (block 977,731). Its only input unlocks with a 4-byte function selector plus the contract script, no signature, and it still paid exactly 10,000 + 1,000 sats.
Credits
Made by Swift Bot Labs during BCH BLAZE 2026: written, voiced and rendered 15-17 Nov 2026; the 27 s cut on 20 Nov 2026. Narration: Swift Bot Labs, voiced with ElevenLabs (Bella; the customer line in the 27 s cut: Sarah). Music: “Fire Place” by HoliznaCC0 (CC0). Sound effects (CC0, Freesound): UI click by Ranner, wooden button by Troube, stamp by kermite607. Fonts: Instrument Sans and JetBrains Mono (SIL OFL 1.1). Licence: the film CC BY 4.0, code MIT; source files. Visuals: animated diagrams and labelled illustrations drawn in code; data from our own mainnet run.
The app: standing-order.swiftbotlab.workers.dev ·
Source: github.com/swiftbotlabs/standing-order ·
14 Nov start: demo and
code ·
EMBER2026: bitcoincash:zpgquneyckvcchup87e8ts7zljkc6aks4yalmfcay8