ARL: post-graduation swaps and LP management

Use the canonicalPool created by Graduation. Do not run arl:create-pool again for a graduated token. Manager NFT IDs (concentrated) and pool NFT IDs (compounding) are different namespaces; always retain the pool model and manager address.

Unsigned actions read AMMORA_ACCOUNT; AMMORA_SEND=1 requires the matching signer. Send-only commands refuse AMMORA_SEND=0; they are not dry-run planners. Follow each file's argument header and the integrated guide for actual inputs. Current additional methods are in direct/Compounding optional positions. The older builder audit (GitHub access may be required) preserves historical gaps, not current availability. Use claim-all-position-fees.ts and the batch guide for sequential multi-position claims.

Claim managed concentrated LP fees to a payout address

For the complete Config-to-Graduation launchpad flow, start with the single launchpad guide. This page expands its LP payout/delegation step.

Connect the Position Manager NFT owner or an authorized fee delegate and pass the fee destination as the optional third argument. The token ID is the manager NFT ID printed by arl:get-user-positions, not the pool's internal position ID.

# Send the position's accrued base/quote fees to a reviewed treasury address.
AMMORA_SEND=1 npm run arl:claim-position-fee -- <pool> <managerNftId> <payoutAddress>
# Omit the destination to keep the existing behavior: pay the owner.
AMMORA_SEND=1 npm run arl:claim-position-fee -- <pool> <managerNftId>

The connected authorized caller signs and pays native gas. The payout wallet receives the fee tokens and does not need to sign. A delegate needs the exact fee permission described below; the claim command does not grant permission. A custom payout changes only this claim's destination: NFT ownership, future fee rights, liquidity, vesting and permanent locks stay unchanged. Fees can be collected from permanently locked liquidity; that does not unlock or withdraw principal.

The SDK authenticates the factory/pool/manager binding and plans claimPositionFees(managerNftId, payoutAddress). The example uses that same address for simulation and receipt validation. It refuses a zero/invalid destination and extra arguments. If both fee amounts are zero it sends no transaction; this is a no-op, not a successful positive payout.

After signing, retain the hash and successful canonical receipt. Match the manager's PositionFeesClaimed event to the expected manager NFT ID, destination and raw base/quote amounts. For each fee token, compare the payout wallet's balance at receipt-1 and receipt block; the increase must equal the event amount. Also check ERC-20 Transfer logs, the owner's token balance during that claim, NFT owner, pool binding, vested/unlocked liquidity and permanent locked liquidity. Gas changes are separate from fee-token transfers.

Actual GIWA alternate LP payouts (GitHub access may be required) cover existing NFTs #5/#7 paying two distinct controlled wallets, with #6's zero-fee rounding dust excluded. Review your own full payout address before signing; copying test addresses would send fees to those test wallets.

Fee-only delegation and a separate payout

The owner grants one of two explicit permissions with arl:fee-delegate. This replaces the NFT's single delegate slot, so inspect the existing delegate first. Use only addresses and destinations reviewed by the NFT owner. No liquidity, reward, lock or transfer permission is included.

# Connected as NFT owner: allow this delegate to send fees to a reviewed separate address.
AMMORA_SEND=1 npm run arl:fee-delegate -- <pool> <managerNftId> <delegate> claim-fee
# Connected as that delegate: claim to a separate treasury/payout wallet.
AMMORA_SEND=1 npm run arl:claim-position-fee -- <pool> <managerNftId> <payoutAddress>
# Connected as NFT owner: clear both the delegate address and all permission bits.
AMMORA_SEND=1 npm run arl:fee-delegate -- <pool> <managerNftId> revoke

claim-fee is ClaimFee (8): the delegate can choose any nonzero fee destination. Grant it only to a trusted wallet because it permits redirecting fees. For collection that must pay the NFT owner, grant claim-fee-to-owner (ClaimFeeToOwner, 16) instead; that delegate cannot redirect to a different address. Omitting the claim destination always pays the NFT owner, even if the connected caller is the delegate. Only the owner can grant/revoke; delegation grants neither NFT ownership nor a right to withdraw locked principal. Revocation restores the zero address with permission 0.

The SDK authenticates the pool/manager and enforces caller, permission bits and payout before planning; the exact request must then simulate on chain before signing. An unrelated wallet, a revoked delegate or an owner-only delegate attempting redirection is refused. Never force a failed simulation onto the chain.

Actual delegated GIWA payment and authorization proof (GitHub access may be required) includes owner-only redirection refusal, positive delegated payment, unrelated caller refusal and permission cleanup. Refusals are deployed-contract eth_call simulations with InvalidPermission, not intentionally mined failed transactions.

Fresh SDK 0.3.1 execution (GitHub access may be required) repeats the actual delegated payment and refusal boundary from the separately installed consumer, with permission16/8 checks and final revocation. Follow the fresh-project dependency guide (GitHub access may be required) when copying these files; they require src/shared as well as the SDK.