OpenZaps ecosystem roadmap
OpenZaps becomes an evolutionary market where ideas become Zaps, useful Zaps become agent skills, usage buys 0xZAPS, contributors receive rewards, and competitions produce better strategies.
Current truth
Operating in the current product or protocol.
A usable foundation exists, but the full roadmap system does not.
A design direction, not a shipped feature or date commitment.
Requires explicit review, funding, controls, and production evidence before activation.
Explicitly outside the current release path until its safety model is designed.
v1.1 binds each one-shot route, recipient, assets, step amounts, output floor, and gas limits. v3 adds recurring cadence, run limits, optional executor restriction, and price triggers; v3.1 adds recurring per-run floors derived from allowlisted price sources. All three lineages are live on Robinhood Chain.
Signed intents, execution receipts, relay state, executor scorecards, exact policy simulation, public templates, and read-only checks preserve one rule: an agent may discover and submit, but it cannot widen authority.
The reviewed source path includes isolated creation, exact Permit2 allowances, irreversible halt, recovery, and fail-closed provenance. It is not live until governance broadcasts it and the independent post-deployment canaries pass.
The isolated stack-only factory, creation gateway, execution pot, and creation pot are deployed on Robinhood Chain, independently wired back to the reviewed source, and active: the production creation, execution, and permanent-halt canaries passed with onchain receipts, and the app, relay, and executor lanes are open. The contracts remain unaudited.
Cross-chain funding, hosted signing, notifications, durable operator quotas, package distribution, and private-relay fanout stay off until their documented credentials, migrations, failure modes, and operator checks exist.
Automated deleveraging needs its own liability, oracle, liquidity, liquidation-ordering, and recovery model. It is not treated as another adapter and remains outside the current release path.
OpenZaps is experimental infrastructure. Onchain actions are irreversible. Review the security model, public evals, and risk disclosures before signing.
Roadmap architecture
Continuously launch bounded Zap experiments, then graduate only the ones that create durable utility.
Raw volume alone never qualifies a Zap.
Convert proven Zaps into versioned skills agents can discover, simulate, execute, and safely roll back.
Anyone can fork and improve a skill while preserving attribution to meaningful upstream contributors.
Connect funded outcomes, maintainers who build them, and agents that execute and improve them.
Each category may have a reigning blueprint, challenged on measured utility rather than routed capital.
Optional actions may require refundable 0xZAPS bonds.
Core Zap creation and execution remain token-ungated. Rewards are capped by attributable economic value so wash activity is negative-EV.
Preserve the automated executor share, then let explicitly migrated future protocol fees buy and route 0xZAPS within published limits.
The existing 80% automated-execution fee paid to executors remains intact. For future deployments, the remaining 20% protocol share may move through bounded, rate-limited 0xZAPS purchases.
Existing pot balances and obligations remain untouched. The router applies only to explicitly migrated future fee flows.
Coordinate optional ecosystem work without granting control over user funds or recovery paths.
No governance over user Zaps, passive revenue rights, token-gated recovery paths, or authority over user funds are introduced.
The browser-local practice desk is live; reproducible agent competitions over fixed epochs remain planned before any strategy reaches live capital.
Treat winners as candidates, not automatic upgrades, and promote only evidence-backed components.
A challenger must demonstrate meaningful improvement across multiple evaluations before replacing the incumbent.
Contributor rewards activate only when a component is adopted and continues producing measurable improvement.
Use short, fully budgeted seasons to bootstrap a specific shortage, then measure what survives.
Economic boundary
The live automated-execution fee keeps its 80% executor share and current protocol-pot obligations. No existing pot balance is redirected by this roadmap.
Inspect the live pot →Only future, explicitly migrated fee flows may fund rate-limited 0xZAPS purchases and the proposed 40 / 40 / 20 contribution allocation.
See current token utility →No passive revenue right, user-fund authority, token-gated recovery, or governance over another owner's Zap is introduced. Payment may buy review; it never buys approval.
Read risk disclosures →Compounding loops
Non-negotiables
Core Zap custody and recovery are never gamified.
Rewards compensate performed work—not token balances.
Rewards never exceed their fixed budget or attributable economic activity.
Incentivised and organic volume are always reported separately.
Financial strategy rewards are deterministic, not random.
No winner is blindly merged into the rolling strategy.
Every live-capital progression remains capped, reversible, and explicitly authorised by the user.
New incentive contracts require independent review before handling meaningful value.
Measurement plan
Experimental Zaps graduating into reusable skills.
Successful executions and 30-day repeat usage.
Creator compensation per retained user.
Percentage of rewards funded by real activity.
Organic versus incentivised execution volume.
Meaningful blueprint remix reuse.
Strategy performance after out-of-sample promotion.
Maximum drawdown and strategy failure rate.
Improvement of the reference strategy by epoch.
Build what exists. Evaluate what comes next.