Altcoins
Token-2022 adds key files for viewing confidential balances
A November 8 commit lets spl-token read user-supplied ElGamal and AES keys for certain confidential views. The main branch also retains key derivation from a signer.

Keys can be supplied as files
On November 8, the Solana Program repository integrated a change to the Token-2022 command-line interface. It allows users to supply decryption keys directly to view certain confidential data. The change is on the repository’s main branch. It is relevant to accounts or tokens whose confidentiality keys already exist in files and whose operators want to view the data without deriving those keys at that moment from the signer selected in the tool.
The patch introduces two options that each accept a file path. The first takes an ElGamal keypair. The second takes an AES key. The program requires both together and an explicit request to decrypt. The ElGamal pair must match the public key recorded on-chain for the data being viewed. The software checks that match before using the files. The repository also covers the case of an incorrect AES key, with an expected decryption error.
Three commands with different rules
The options are added to the balance, supply, and display commands. The first can decrypt a token account’s confidential balances. The second handles the confidential supply of a token configured for that feature. The display command passes the keys to the processing path that matches the data being viewed. The tests separate account and supply cases. In each case, providing the files is insufficient if the ElGamal key does not match the one the program reads from on-chain data.
The owner parameter is handled differently across commands. In the balance command, it can still select the account to view when custom keys are provided. For supply and display, the new options are declared incompatible with that parameter. When the files are not supplied, the existing path for deriving keys from a signer remains available. The distinction concerns command configuration and the choice of data to read.
The change concerns reading data
The patch lets the tool read and decrypt data with keys that are already available. The code checks the keys along the viewing path. Added tests build temporary files, exercise reads with valid keys, and verify the handling of incorrect keys. The options expect paths to these files. They do not expect key contents in the arguments, and the commit does not provide for publishing the files on-chain.
November 8 is the date the change entered the source code. The commit gives no date for availability in a distributed release of the tool. It changes the client’s viewing commands without announcing a change to the confidential transfer program on Solana. To evaluate the scope, it is important to distinguish the command version in use, the confidentiality feature enabled for the data being viewed, and whether the local keys match the recorded public key.
