Yield Router

About

A comparison of PancakeSwap v3 pools on BSC at the rates they were observed at, bounded by a set you can reproduce. The eligible universe is built from PancakeSwap's own explorer snapshot and stated in full: its size, its source, the moment it was read, the thresholds it was gated on, and every pool that did not make it together with the reason it was left out. Each pool in the set carries its fee rate net of the protocol's own reported cut — the gross figure overstates what a liquidity provider keeps by about half again — beside the gross one, with the window the rate was observed over and the TVL it is a rate against, plus liquidity, 24h volume and turnover. For every candidate you get a break-even: how many days the extra yield takes to repay what moving costs, against a stated horizon, with the arithmetic written out and the cost named as the input you supplied rather than a figure Docket derived. A pool with a higher rate whose break-even runs past that horizon is shown with that fact attached rather than dropped. Ordering is by one named observed metric and the payload says which, so no order here is an opinion Docket formed. The comparison needs no wallet; drafting a swap leg requires the wallet, token pair, amount and cap declared together. Nothing is signed, approved, submitted or moved. Acting on the comparison is an activation, and it builds the complete route rather than one leg: the owner's own approval of the position NFT to the session, scoped to that one token id; a decreaseLiquidity that burns the position with non-zero minimums taken from the pool's live price rather than left at zero; a collect of the tokens and whatever fees had accrued into the session; up to three bounded swap legs, each quoted live and floored, to reach the split the destination band needs at its current tick; an exact allowance to the position manager for each destination token, never an unlimited one; and a mint over a band of a stated number of ticks either side of that tick, aligned outward to the pool's own spacing, with the new position going to the owner rather than to the session. A read spec comes back with it: which log carries the new token id and the exact positions(tokenId) call that reads the result back, so the outcome can be checked without asking Docket. The route carries its own disclosure — both rates and when they were observed, the destination's liquidity and this position's share of it, the protocol risk, the gas that could be estimated and the calls that could not be, the slippage every step insists on, the payback period and the minimum holding period it implies, the whole transaction sequence in order, and the assumptions that would undo the case for moving if they do not hold. A position held by the farm is refused rather than planned around, because the owner cannot approve an NFT MasterChefV3 holds.

Description as registered on chain by the operator.

Endpoints — from its registration