CI rehearsal only (do not merge)

[michael-moffett]

Fork CI only. Do not merge.

[greptile-apps]

Confidence Score: 3/5

The PR should not merge until setMint rejects mismatched existing mint owners and unsupported token programs for new mints.

Findings

1.  Base updates skip owner validation ▶
2.  Unsupported programs receive mint accounts ▶
3.  Configured auditor cannot be cleared ▶

Summary

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

• Preserves existing mint extensions and tops up lamports to the rent floor.
• Adds Rust tests for mint creation, extension updates, and confidential token-account use.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A["setMint(mint, update, tokenProgram?)"] --> B{"Mint exists?"}
  B -- No --> C["Create initialized mint"]
  B -- Yes --> D["Read existing mint data"]
  C --> E["Apply base-field update"]
  D --> E
  E --> F{"Confidential update?"}
  F -- Yes --> G["Merge Token-2022 extension"]
  F -- No --> H["Preserve existing extension bytes"]
  G --> I["Top up rent and write account"]
  H --> I

Loading

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

[greptile-apps]

Base updates skip owner validation When an existing mint is owned by Token-2022 but tokenProgram is omitted, this check is skipped because the update is not confidential. setMint changes the Token-2022 mint and returns success even though the request defaulted to SPL Token. It can also change another program-owned account if its data decodes as a mint. Check ownership for base-field updates too.

[greptile-apps]

Unsupported programs receive mint accounts When creating a mint, tokenProgram accepts any valid public key. For every program other than Token-2022, the new account receives SPL Token mint data but is owned by the supplied program. An unrelated program cannot use that account as a token mint, yet setMint returns success. Reject unsupported program IDs before creating the account.

[greptile-apps]

Configured auditor cannot be cleared Once auditorElgamalPubkey is set, this update type provides no way to restore the no-auditor state. Omitting it or sending JSON null preserves the existing key. This makes tests that need to remove a configured auditor use another way to change the mint; provide an explicit clear value, as mintAuthority does.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!