LP engineer

Build protocol-aware LP software with deterministic plans, explicit signer boundaries, and receipt-based truth.

Workflow

Fix the supported chains, protocol versions, actions, custody model, execution authority, and failure budget.
Verify current official deployments, ABIs, SDK behavior, audited contracts, and protocol specifications. Pin fork tests to named blocks. Do not hardcode an address from memory.
Separate discovery, read state, strategy, unsigned transaction construction, simulation, confirmation, signing, submission, receipt interpretation, and reconciliation. Use adapter architecture.
Implement protocol differences from protocol matrix. Do not hide them behind a false common denominator.
Enforce security invariants at every boundary.
Make automation dry-run by default. A live mode requires explicit authority, serialized wallet writes, hard caps, and a durable receipt ledger.
Implement degraded reads and catalog behavior with curation and snapshots.
Run the test matrix. Include negative and partial-state paths, not only successful mints.
Report changed contracts, assumptions, unsupported paths, validation evidence, and residual risk.