hackquest logo

Standing

Chains can only push, so stablecoins have no subscriptions and no chargebacks. Standing is a capped, revocable onchain mandate where each charge sits in escrow through a reversal window, and the right to reverse is earned through clean payment history.

视频

技术栈

Solidity
Foundry
OpenZeppelin
Next
Wagmi
TailwindCSS
Typescript
Uniswap Permit2

描述

Every subscription runs on pull: the payer authorizes once and the payee draws funds repeatedly. Blockchains are push-only, because only the holder of a private key can move funds. So a merchant wanting recurring stablecoin revenue either begs customers to remember each month or takes custody of their funds. There is also no chargeback. A payer who pre-authorized a pull has no remedy short of court, while Mastercard projects US chargeback volume at 146 million disputes worth $15.3 billion in 2026.


We surveyed 28 builders in crypto communities. The most common way they collect recurring payments from crypto-native customers is a bank transfer. 24 of the 28 have declined stablecoins for recurring billing, and the top reason was "no way to auto-charge on a schedule," with "no way to handle disputes or refunds" third. Those are the two mechanisms Standing builds. 19 said they would run a testnet integration; none said no.


Standing is a mandate the payer signs once, stating who may charge, how much at most, and how often. The revoke button belongs to the payer alone and works immediately, without the merchant's cooperation. Each charge lands in escrow with an unlock time rather than going straight to the merchant. During that window the payer can reverse it; after the window it finalizes on its own. No arbiter, no adjudication, nobody to trust.


The hard part is that if reversing is free, customers do it when nothing went wrong, and no merchant would accept that. So Standing makes the right earned rather than granted. It vests only after clean payment history, and its ceiling scales with the value that history represents, so cheap history cannot unlock expensive theft. A fresh address holds no reversal right at all, which removes the Sybil clawback by construction rather than by policing it. Reversal history is public in both directions, so merchants price payer risk before accepting a mandate, and a merchant's own hold window shortens as they earn trust. That portable two-sided reputation is something card networks structurally cannot offer, because the data is their moat.


Built for crypto-native businesses that bill monthly: exchanges and trading desks, developer tooling, data and analytics APIs. Standing takes a protocol fee on settlement only, capped at 1% in code and never charged on a reversal, so revenue tracks successful payments and the payer's remedy stays free. Reputation state is written on every settlement, so the design depends on low per-charge gas, which is why it is deployed and verified on Robinhood Chain Testnet and Arbitrum Sepolia, through Uniswap's Permit2 at its canonical address so the allowance stays revocable and expires on its own.

本次黑客松进展

All of it. The repository starts from an empty directory on 18 September, inside the buildathon window, and the first commit is the Foundry scaffold. 69 commits, nothing carried in from earlier work. What was built: a single deployed Solidity contract (1,390 lines across 10 files) composed from abstract modules covering EIP-712 mandate signing, a mandate registry with per-payer revocation and a global kill switch, Permit2-based pulling with an exact-transfer assertion, time-locked escrow, and two reputation books that price a payer's reversal right and a merchant's hold window. Alongside it, 3,672 lines of tests across 19 files, 174 passing including handler-based invariant tests run against a deliberately hostile ERC-20. A 3,077 line Next.js frontend with separate payer and merchant flows and a wallet-free public lookup. Deployed and verified on both Robinhood Chain Testnet and Arbitrum Sepolia. Two things happened during the build that the commit history shows. First, I stress-tested my own access control and found a live vulnerability: the reversal ceiling was read from the merchant's policy at reversal time, so a merchant could take a charge and then set the cap to zero, stripping the payer's remedy while their money was already escrowed. I proved it with a passing test, fixed it by snapshotting the merchant's terms into the hold at charge time, and confirmed the test then failed. Second, I surveyed 28 builders from crypto platforms to check the premise rather than assume it, and the two most-cited blockers to accepting stablecoins for recurring billing turned out to be the two mechanisms this contract provides.

融资状态

Bootstrapped, no outside capital raised. Standing was built solo during the buildathon and has no revenue: both deployments are testnets. Not currently running a raise, but open to conversations with investors or partners working on stablecoin payments infrastructure. Closest thing to traction: of 28 builders surveyed, 19 said they would run a testnet integration and none said no, and 9 left contact details for follow-up.
队长
RRaymond Abiola
项目链接
赛道
DeFiInfra