CI rehearsal only (do not merge)

[michael-moffett]

Fork CI only. Do not merge.

[greptile-apps]

Confidence Score: 3/5

This PR should not be merged until existing extended mints can be updated and plain mint updates enforce the requested token program.

Findings

1.  Wrong mint marker offset ▶
2.  Plain updates ignore mint ownership ▶
3.  Configured auditor cannot be removed ▶

Summary

This PR adds surfnet_setMint to create or update SPL Token and Token-2022 mints, including confidential-transfer configuration, and exposes it through the Node SDK.

• Existing extended mints cannot reliably gain the confidential extension because the builder clears the wrong account-type byte.
• Plain updates do not enforce the requested token program against an existing mint’s owner.
• The update shape cannot remove an auditor after one has been configured.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A["surfnet_setMint"] --> B{"Mint exists?"}
  B -- No --> C["Create initialized mint"]
  B -- Yes --> D["Read existing mint"]
  C --> E["Apply base updates"]
  D --> E
  E --> F{"Confidential update?"}
  F -- Yes --> G["Build Token-2022 extension bytes"]
  F -- No --> H["Preserve extension tail"]
  G --> I["Top up rent and write"]
  H --> I

Loading

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

[greptile-apps]

Wrong mint marker offset When setMint adds confidential support to a Token-2022 mint that already has extensions, this clears byte 165 instead of the mint’s account-type byte at offset 82. The existing marker remains set, so unpack_uninitialized rejects the buffer and the update fails.

Suggested change

	if let Some(account_type) = buffer.get_mut(spl_token_2022_interface::state::Account::LEN) {
	*account_type = 0;
	}
	if let Some(account_type) = buffer.get_mut(spl_token_2022_interface::state::Mint::LEN) {
	*account_type = 0;
	}

[greptile-apps]

Plain updates ignore mint ownership If a caller omits tokenProgram while updating an existing Token-2022 mint, setMint selects the legacy SPL Token program but skips the owner check because the update is not confidential. It reports success and rewrites the mint while leaving its Token-2022 owner unchanged, hiding the program mismatch from callers that subsequently use the requested program.

[greptile-apps]

Configured auditor cannot be removed Once an auditor key is set, omitting auditorElgamalPubkey keeps it and supplying a value only replaces it with another key. The update has no way to restore the supported no-auditor state, so callers cannot remove an auditor through setMint.