peer-rate-managers

Peer rate managers

A Peer vault is a rate manager for maker deposits. It is not an ERC-4626 pooled asset vault: delegation does not mint shares or transfer custody of the maker's USDC to the manager. Keep deposit ownership, delegate/controller authority, manager identity, and fee recipient distinct.

Read before changing a rate

Resolve environment, registry address, rateManagerId, authorized manager wallet, affected escrow/deposits, currency/method pairs, and requested pricing or fee policy. Read live configuration using @zkp2p/[email protected] and the relevant deployment's contract ABI. Never invent addresses from a marketing domain or copy a staging registry into production.

For an existing vault, read manager, fee recipient, current/max fee, configured rate pairs, and each target deposit's own floor and delegation. A requested percentage needs a declared unit conversion: rates and fees here use 18-decimal fixed-point values, not integer basis points passed directly to the contract.

Create or delegate

1. Prepare client.createRateManager.prepare({ config: { manager, feeRecipient, maxFee, fee, name, uri } }) for the authorized configuration. maxFee is the lifetime ceiling for that manager; select it deliberately and respect the deployed contract's cap. Do not choose example fee recipients or add an agent fee.
2. Simulate and submit through the configured signer; derive the new manager ID from the confirmed receipt, then read it back. A name/URI is metadata, not evidence of deployment.
3. Set explicit rates for supported method/currency pairs before attaching deposits. Use protocol payment-method and currency hashes from the configured SDK/contracts, not a guessed encoding or fiat symbol address.
4. Attach each deposit using the path that owns its delegation: direct setRateManager or the existing controller's setDepositRateManager. These are different authority paths. Read current ownership/controller configuration first; verify escrow, registry, and manager ID after confirmation.