> For the complete documentation index, see [llms.txt](https://ipusd.gitbook.io/ipusd-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ipusd.gitbook.io/ipusd-docs/user-guide/example-user-scenarios.md). # Example user scenarios ### Subscribing before a Round opens Alice subscribes with 1,000 ipUSD while no Round is active. Her ipUSD enters the FIFO queue, but no IP Vault shares become claimable. Two days later, the Operator schedules a Round with 5,000 ipUSD of Settlement Capacity. Even after the Timelock expires and the Round opens, Alice must wait for Settlement. When `closeRound` is executed, her subscription can be settled at the applicable NAV if her queue position is covered by the available Capacity. ### Subscribing during an active Round Round 08 is open with 5,000 ipUSD of Settlement Capacity. Bob subscribes with 500 ipUSD before the cutoff. His subscription enters the FIFO queue and does not immediately issue shares. If his queue position is covered, it can be settled when Round 08 closes. The displayed Remaining Settlement Capacity does not by itself guarantee that Bob’s full subscription will be settled. ### A subscription is partially covered Carol subscribes with 1,000 ipUSD. When her request reaches the front of the queue, only 600 ipUSD of Settlement Capacity remains. The contract settles 600 ipUSD into IP Vault shares. The remaining 400 ipUSD stays in the queue through a linked record and keeps its position. Carol can claim the shares allocated to the settled portion while the remaining amount waits for a later Settlement or an Instant Withdrawal match. ### Settlement Capacity has been exhausted David subscribes with 300 ipUSD, but earlier requests use all available Settlement Capacity. His subscription remains queued and automatically carries forward. He does not need to submit it again when new Capacity becomes available. If the amount remains unlocked, David can cancel it after the cancellation delay. ### Subscribing after the cutoff Round 08 has reached its cutoff. Emma submits a 700 ipUSD subscription afterward. Her subscription enters the queue but is not eligible for Round 08. It waits for a later Round. The same treatment applies if the Operator has already frozen the eligible subscription boundary. ### Using a referral code Fiona enters a referral code before submitting a 500 ipUSD subscription. The code records the referral source. It does not change her fee, queue position, Settlement eligibility, Capacity, NAV, or eventual share allocation. Submitting a referral code is optional. ### Repeated Instant Withdrawals split one subscription Frank has a queued subscription of 600 ipUSD. Another user completes three Instant Withdrawals of 100 shares each. Assuming a NAV per share of 1 ipUSD, the three withdrawals use 300 ipUSD from Frank’s queued funds and allocate approximately 300 IP Vault shares to him. The remaining 300 ipUSD stays queued. The contracts may create several claimable records. The interface groups them into the shared Claim flow, allowing Frank to claim up to 50 eligible records in one batch. ### Standard Withdrawal Capacity cannot cover the next request The Standard Withdrawal queue contains requests for 40, 80, and 30 shares in that order. A future Round provides 100 shares of Standard Withdrawal Capacity. The first 40-share request is fully settled, leaving 60 shares of Capacity. Because the next request requires 80 shares, it cannot be partially settled. The contract stops processing the queue and does not allow the later 30-share request to skip ahead. Both remaining requests wait for a later Round. ### Batch-claiming shares and ipUSD Grace has several claimable records from completed subscription Settlements and Standard Withdrawals. The interface groups the available IP Vault shares and ipUSD into one Claim flow. If Grace has 50 or fewer eligible records, the interface displays Claim all. If more than 50 records are available, the first batch processes up to 50 records. The remaining records stay claimable and can be processed in another transaction. Depending on whether the records contain shares, ipUSD, or both, Grace’s wallet may request more than one underlying transaction.