Recur Labs is the engineering organization behind the Recur permissioned‑pull
standard. Our job is to make continuity native to money: liquidity that rebalances
before failure instead of after it.
We design and maintain the primitives that let value move safely, continuously,
and under revocable consent — across wallets, L2s, treasuries, custodians, and
exchanges.
RIP‑001 · Permissioned‑Pull Objects
Signed, revocable pull rights. A wallet can authorize “you may pull up to X under these limits.”
This is the core primitive.
RIP‑002 · Consent Registry
A shared on‑chain index of active consents, revocations, and cumulative pulls. Wallets and auditors
can verify “is this still allowed?” without trusting an app.
RIP‑003 · Cross‑Network Flow Intent
A signed instruction that describes where liquidity should move across domains (which chain is over‑funded,
which is under‑funded, how much may move, by whom, and until when).
RIP‑004 · Non‑Custodial Rebalancing
Execution logic for RIP‑003. Liquidity moves from the surplus domain to the deficit domain using
permissioned pull, without bridges, wraps, or pooled custody.
RIP‑005 · Flow Channels
Continuous, rate‑limited pull between a grantor and grantee. Enables streaming payouts, automated
treasury draining, recurring settlement — under pause and revoke.
RIP‑006 · Universal Clock & Adaptive Routing
A shared timing model and router logic. Channels across chains stay in sync on rate limits and allocation
targets, so no venue gets over‑drawn.
RIP‑007 · Policy‑Bound Pull
Programmatic policy on top of consent: spend ceilings, jurisdiction limits, KYC requirements,
allowed destinations, rate guards, emergency stops — the compliance surface institutions require.
RIP‑008 · Settlement Mesh
Network‑wide equilibrium. Liquidity allocates itself toward target weights across chains,
custodians, and venues using only revocable consent, no custody.
