FxAeon integrates @aladdindao/[email protected] through a locked set of 15 methods: four for positions, two for borrowing, two for bridging, and seven for fxSAVE. This guide describes that supported integration, not every capability in the SDK or f(x) Protocol.
- Upstream public SDK
FxSdkreads protocol state and prepares unsigned transactions. It does not sign or broadcast them.- FxAeon application wrappers
- The read facade adds deadlines and position validation. Service planners bind SDK output to the reviewed request. The transaction runner handles simulation, explicit wallet approval, receipts, and refresh.
- Networks
- Positions, Borrow, and fxSAVE use Ethereum, chain ID
1. Bridge uses Ethereum and Base, chain ID8453, with distinct source and destination chains.
Compare the pinned SDK source (opens in a new tab), pinned upstream integration guidance (opens in a new tab), local patch (opens in a new tab), and 15-method scope lock (opens in a new tab). Upstream authorship does not imply endorsement of FxAeon.
Three parts of the patch are tracked in upstream pull requests: exact debt-ratio packing (#15) (opens in a new tab), concurrent pool reads (#16) (opens in a new tab), and no delay after the last multicall batch (#17) (opens in a new tab). The short-pool fix is already in the pinned upstream source but not in an npm release; the other parts are FxAeon's own. The SDK scope (opens in a new tab) maps each part.