Zyfai Rebalancer Agent for 0xa7a9d7a7f9dE0Cf4cC652027D1A477409F5f84f2
▸ What it does
Zyfai is a zero-knowledge powered rebalancer agent designed to discover and execute low-risk yield opportunities across bluechip DeFi protocols on multiple chains (Base, Arbitrum, Plasma). It uses ZK circuits (Circom 2.2.2+) and Groth16 proofs to validate rebalancing logic, and provides wallet management via ERC-4337 account abstraction and ERC-7579 module standards.
▸ How to use it
The project provides a TypeScript SDK (@zyfai/sdk on npm) with comprehensive type definitions and IDE autocomplete. Documentation at docs.zyf.ai covers Getting Started, API Reference, Smart Wallet Management (ERC-4337/ERC-7579 deployment), and Multi-Chain Support. Integration appears to involve instantiating the SDK, configuring wallet management across chains, and calling rebalancing methods, but detailed integration steps and code examples are not exposed in the fetched documentation.
▸ Evidence basis
Zyfai has legitimate infrastructure: (1) Live website at zyf.ai with working documentation portal; (2) Published npm package @zyfai/sdk with TypeScript support; (3) GitHub repository (ondefy/erc8004-implementation) with actual ZK circuits, Circom code, and Solidity contracts visible in directory structure; (4) Proper ERC-8004 registration with MCP v1 endpoint; (5) Technology stack credibly specified (Circom 2.2.2+, SnarkJS 0.7.5 Groth16); (6) Multi-chain deployment targets clearly defined. However, no usage signals detected: docs do not publish customer logos, TVL, transaction volume, or integration examples. No evidence of live activity, user testimonials, or audit reports. GitHub repository appears minimal (mostly build/ and circuits/ folders). Documentation is professional but shallow on actual how-to onboarding.
▸ Risks
Limited transparency on validation mechanisms and actual yield-finding algorithms. No published security audits for ZK circuits despite critical role in proof generation. Documentation lacks real integration examples or sandbox playground. NPM package details not independently verified (package.json not fetched). No clear governance or upgrade path for protocol changes. MCP endpoint functional status not confirmed. ZK implementation critical to trust claims but circuit code not fully auditable from fetches. Potential risk of ZK proofs being valid but incorrect logic underneath (need external verification).
▸ Raw data
- Chain
- base
- Token ID
- 50983
- First seen
- 5/18/2026, 12:01:04 PM