This roadmap outlines the integration of the Riquid Self-Driving Yield Engine into the SettlerEngine hexagonal architecture.
- Define
YieldStrategyEntity - Define
YieldProviderPort (Interface) - Update
SettlementEnginePort: AddDepositToYieldandWithdrawFromYieldmethods.
- BSC RPC Provider: Implement a Geth-compatible provider for BNB Smart Chain (BSC).
- Asset Support: Add configuration and tracking for BNB, USDT (BEP-20), and BUSD.
- Contract Bindings: Generate Go ABIs/bindings for Riquid Vaults.
-
riquid_adapter.go: Implementation of theYieldProviderinterface for Riquid Yield Engine using generated bindings. - Withdrawal Logic: Implement
WithdrawFromYieldmethod. - State Machine Integration: Logic to encode/decode calls to Riquid strategy contracts via bindings.
- Auto-Route Service: Implementation of routing logic upon
SETTLEMENT_CONFIRMEDevents. - Threshold Logic: Implement gas-efficiency triggers to prevent micro-transactions.
- Cron Worker: Develop a "Self-Driving" background worker for periodic harvesting and reinvestment.
- Event Bus Wiring: Settlement events are now published via
LocalBusand consumed byYieldService.
- ERC-4337 Integration: Logic to manage funds via non-custodial account abstraction (Provider + UserOps).
- Session Key Manager: Sign "Harvest" and "Reinvest" transactions using restricted-scope keys.
- Paymaster Integration: Support for gas sponsorship on BSC via
Paymasterclient.
- Prometheus Metrics: Track APY performance, total value locked (TVL) in yield, and "Time-to-Settle".
- Integration Tests & Wiring: End-to-end wiring in
settlerd, unit tests for yield logic, and event-driven routing tests.
Core Requirement: All implementations must maintain the Non-Custodial nature of SettlerEngine. Automation must be achieved through cryptographic delegation (Session Keys), not centralized management.