Onchain wealth automation
The system connects onboarding, money movement, policy checks, scheduled workers, and Aave V3 position protection.
01Context
Problem
The product needed to move users from bank onboarding to smart-wallet execution. It also needed to monitor Aave borrowing health and act before a position reached liquidation risk.
Constraints
- The complete Aave production environment could not be reproduced locally.
- External providers exposed asynchronous webhooks and failure states.
- Financial and onchain operations required idempotency and reconciliation.
02System
Architecture
Plaid and Bridge onboarding
Backend account and wallet state
Policy and risk checks
Scheduled workers
Simulation and validation
Smart contracts and Aave V3
Reconciliation
My role
Started with backend work, then learned Next.js in the project and took responsibility for key frontend flows. Owned platform architecture, provider integrations, scheduled execution, admin operations, and lead technical decisions.
Decisions
- Separated provider state from internal account and compliance state.
- Used scheduled workers and explicit policy checks to monitor Aave health factors and reduce liquidation risk.
- Combined source inspection, invariants, dry runs, available simulations, and controlled deployment when full reproduction was unavailable.
03Validation
Tests and checks
- Tracked provider and transaction state through idempotent integration flows.
- Validated controlled deployments against production reconciliation.
- Monitored managed positions over the production run.
04Outcome
Result
Bridge and Plaid-linked virtual accounts processed more than USD 500K over six months without an integration incident. The Aave automation supported more than USD 2M in collateral flow across 84 positions with no managed position liquidated over 18 months.
Limits
The USD 500K virtual-account volume covers six months of provider integrations; the USD 2M collateral flow and 84 managed Aave positions describe a separate 18-month scope. These volumes are not additive. Zero liquidations describes that observed run, not a guarantee. The complete Aave production environment was not available for local reproduction. Confidence depended on narrower simulations, source inspection, invariants, and controlled rollout.