Infrastructure for Permissioned-Pull Liquidity

We maintain the Recur standard, publish the RIP series (001–008), and ship open reference contracts, SDKs, and tooling for continuous, consented flow of digital value.

GitHub / Contracts Partnerships / Contact

Mission Why we exist

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.

What we build RIPs 001–008

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

Canonical revocation + accounting. A shared index for “is this consent still active?” and “how much has been pulled so far?”

RIP-003 · Cross-Network Flow Intent

A signed intent that expresses where liquidity should sit across domains (Ethereum, L2s, custodians, etc.) before anything moves.

RIP-004 · Non-Custodial Rebalancing

Executes a Flow Intent by coordinating consented pulls at the source and destination. No wrapped assets. No pooled bridge custody.

RIP-005 · Flow Channels

Continuous, rate-limited pull streams. Payroll, treasury draining, margin defense — all under revocable consent.

RIP-006 · Universal Clock & Adaptive Routing

A shared timing model and router logic so flows across chains stay synchronized, auditable, and policy-compliant.

RIP-007 · Policy Enforcement

Machine-readable limits (jurisdiction filters, spend ceilings, destination allowlists). Banks, treasuries, and DAOs can say “yes — but only like this.”

RIP-008 · Settlement Mesh

Autonomous liquidity equilibrium. The network continuously nudges funds toward target allocations — without custody and always inside revocable consent.

Open standard stewardship Neutral by design

The Recur protocol is an open standard. Recur Labs maintains the reference implementation, coordinates RIP discussion, and contributes to Ethereum-ecosystem review.

All contracts ship under Apache-2.0. All drafts are archived to IPFS. We don’t custody funds. We define motion.