CI rehearsal only (do not merge)

[michael-moffett]

Fork CI only. Do not merge.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[michael-moffett]

@greptileai review

[greptile-apps]

Confidence Score: 2/5

The PR should not be merged until existing mint extensions, confidential settings, and excess lamports survive applicable updates.

Findings

1.  Existing mint extensions disappear ▶
2.  Partial updates clear confidential settings ▶
3.  Mint updates discard excess SOL ▶

Summary

The PR adds surfnet_setMint, Rust and generated TypeScript update types, and tests for plain and confidential Token-2022 mints.

• Existing mints need safer handling: confidential updates can discard extension data, and any update can discard excess lamports.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A["setMint: load or create mint"] --> B["Apply base-field update"]
  B --> C{"confidential supplied?"}
  C -- No --> D["Repack base; retain extension bytes"]
  C -- Yes --> E["Build new data with only ConfidentialTransferMint"]
  D --> F["Replace account balance with rent minimum"]
  E --> F
  F --> G["Write authoritative account update"]

Loading

_{Reviews (1) · Last reviewed commit: "feat(core): surfnet_setMint cheatcode wi..."}

[greptile-apps]

Existing mint extensions disappear When setMint adds confidential settings to a Token-2022 mint that already has a transfer-fee or other extension, this branch builds new account data containing only the confidential extension. The existing extension is silently removed, so a transfer-fee mint, for example, loses its fee configuration. Preserve the existing extensions or reject the update.

[greptile-apps]

Partial updates clear confidential settings On an already-confidential mint, an update that supplies only autoApproveNewAccounts writes null values over the existing authority and auditor key. This silently discards settings the caller did not ask to change, contrary to setMint’s promise to retain omitted fields. Preserve those fields when updating an existing extension.

[greptile-apps]

Mint updates discard excess SOL When an existing mint holds more SOL than the minimum rent balance, even a decimals-only update replaces its balance with that minimum. The excess SOL disappears from the simulated account. Retain the existing balance when it is sufficient, adding lamports only if the updated account needs more rent.