Managing Positions
How approvals, ledger shares, fee claims, additions, full withdrawals, and alternate payout recipients work after you choose a range.
Approvals and deposit
Each ERC-20 leg that needs permission asks for a bounded approval before the deposit. A native ETH leg is attached as transaction value and any unused amount is returned. The quote is a ceiling, and every confirmed wallet prompt is a separate chain transaction.
Your ledger share
The hook pools deposits that use the same ticks and records each holder's proportional ERC-6909 share. It is not an NFT and normally does not appear in a wallet token list. Shares are transferable at contract level, but the Wyrm interface does not currently provide a transfer workflow. Future staking can also restrict transfer while a share is staked.
Add, claim, and withdraw
Adding to identical bounds mints more shares after settling the range's prior accounting. Claiming sends accrued fees without removing principal. Withdrawing burns the chosen share percentage and returns the range's current asset mix. A full principal withdrawal can leave a separate fee balance, which remains claimable until collected.
Contract exit and interface access
The ledger's withdrawal path does not read the pause or claim-fee state. The hosted interface can still be unavailable or refuse actions because of geofencing, and the chain or a token can fail to process a transfer. These are different layers. Contract addresses are published on Contracts for independent access.
A payout can use a different recipient where the deployed contract supports it. This can route around an address-specific token blocklist. It does not override an issuer's token-wide pause or make a restricted transfer lawful.
