Account Management

hot and cold wallets it is not recommended that all customer deposits be kept in a single wallet hot wallet for which the passphrase is stored on a main server a cold wallet is recommended for holding the majority of the deposits and a manual transaction from the cold wallet to the hot wallet be made when a portion of the deposits needs to be available for day to day operations signum account format the account id is stored internally as a 64 bit signed long variable when used in apis, it is usually returned as both an unsigned number represented as a string and as an alphanumeric reed solomon representation starting with a “s ” prefix example s er8m syv3 r7ek euf3l in api request parameters and response json, you will find both representations the numeric representation is typically displayed as account, sender, and recipient the alphanumeric representation is typically displayed as accountrs, senderrs, recipientrs (added “rs”) rs stands for reed solomon this form of address improves reliability by introducing redundancy that can detect and correct errors when entering and using account id’s in testnet , the alphanumeric reed solomon representation starts with a “ts ” prefix account used for deposits before deposits are accepted, the deposit account needs to be protected with a strong passphrase and protected with a public key account security each address and public key of an account is retained permanently in the blockchain, even if it has a zero balance the use of throwaway addresses is discouraged