CI rehearsal only (do not merge)

[michael-moffett]

Fork CI only. Do not merge.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Adds test-only cheatcode for mint configuration.

The PR should not merge until setMint preserves mint changes made between its read and authoritative write.

Findings

1.  Concurrent mint changes are lost ▶

Summary

Adds surfnet_setMint to create or patch SPL Token and Token-2022 mints, including confidential-transfer mint configuration, with Rust types, SDK bindings, and tests.

• Existing mint extensions and lamports are intended to be retained during updates.
• The new read–modify–write path can overwrite a concurrent mint change.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A["setMint request"] --> B["Read or generate mint"]
  B --> C["Patch base fields and optional confidential extension"]
  C --> D["Top up rent"]
  D --> E["Authoritative account write"]

Loading

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

[greptile-apps]

Concurrent mint changes are lost

If a transaction changes the mint after setMint reads it but before this authoritative write, setMint replaces the whole account with its earlier copy. For example, a decimals-only update can restore the old supply after a concurrent mintTo, losing the supply increase. Coordinate the read and write so fields outside the requested update are preserved.