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.

Do not merge until explicit null correctly clears an existing confidential mint authority and auditor.

Findings

1.  Explicit null does not clear ▶

Summary

Adds surfnet_setMint to create or patch SPL Token and Token-2022 mints, including confidential-transfer configuration, and exposes it through the Node SDK.

• Preserves existing mint extensions and tops up lamports for the resulting account size.
• Adds Rust tests for creation, extension updates, owner checks, and confidential-token-account integration.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A["setMint request"] --> B["Load existing mint or generate one"]
  B --> C["Check token-program owner"]
  C --> D["Apply base-field updates"]
  D --> E{"Confidential update?"}
  E -- Yes --> F["Build or patch Token-2022 extension"]
  E -- No --> G["Repack base; preserve extensions"]
  F --> H["Top up rent and write account"]
  G --> H

Loading

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

[greptile-apps]

Explicit null does not clear When surfnet_setMint receives confidential.authority: null or auditorElgamalPubkey: null for an existing mint extension, this parsing treats the null like an omitted field. The later assignments are skipped, so the old authority or auditor remains instead of being removed. The new null-removal test covers this case and will fail.