You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Solana CT: SDK — confidential mint transaction building + proof-account approach (Sprint 1) #9381
currentSupplyCiphertext = on-chainconfidential_supply (identity = 64 zero bytes for fresh mint)
ConfigureConfidentialTransferAccount instruction:
One-time ATA setup — register ElGamal pubkey + AES key
Part of the token account configuration flow
Proof-account tx group sequencing (SendQ skeleton):
Group the 5-6 txs for a single mint/burn as one logical unit (create-record → write → 3 verify → confidentialMint)
SendQ must sequence these together; the indexer parses the group
This is the proof-account tx group — the required 5-6 tx sequence per mint/burn. This is NOT the same as transfer-splitting multi-tx (a single confidential transfer split across multiple txs because ZK proofs do not fit one tx) — that is an edge case deferred to the production scope doc.
Key details (validated on devnet)
confidential_supply on fresh mint = identity ciphertext (64 zero bytes), NOT encryptU64(0)
Record account is reusable across retries + closeable (closeAccount reclaims rent)
Context state accounts are one-shot + closeable (closeContextStateProof reclaims rent)
Proof gen inputs (supply key, auditor pubkey) come from KMS worker — SDK assembles instruction data, does NOT do proof crypto
The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 26EF:21E642:706AA3:76D25B:6A69E4D6)
Activity
Copilot commentedon Jul 29, 2026
The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 26EF:21E642:706AA3:76D25B:6A69E4D6)