Persists a Solana account in DB
It is assumed, the nonce account has been already created on-chain (via createNonceAccountMessage)
Build the unsigned message that creates a nonce account on-chain.
The account address is derived from PAYER plus a random seed rather
than generated as a keypair: createAccountWithSeed takes newAccount as
a plain address, and initializeNonceAccount does not need the new account
to sign either. PAYER is therefore the only required signature, which is
what lets the whole message be signed by a single remote signer and leaves
no throwaway private key in the process.
baseAccount is omitted deliberately — the base is PAYER, which already
signs as the payer, so naming it again would only add a duplicate signer.
The caller signs and broadcasts; this service holds no signing capability. The derived address is returned so it can be persisted with create once the transaction lands.
tallies of available vs total nonce accounts in the DB
Manage Solana nonce pool.
This is for the corresponding workflow or admins to invoke. In service operations, you should be using
SolanaNonceServiceinstead.