On PUKs, but a simplistic view of it is a seed that is encrypted for all device keys To encrypt this data, the client uses Per-User Keys. Sign a transaction, the client will fetch the account private bundle and discard it after use. The client will fetch server visible and user privateįrom the server in order to display the wallet accounts, their balances, recent transactions. It cannot decrypt user private or account privateĪs it does not have the encryption keys necessary. Name: account private.Īll Stellar data are stored in the Keybase database. Per-account encrypted data containing the private stellar account key necessary for signing a transaction.the account name) about all the stellar accounts in the user's keybase wallet. A global bundle of encrypted data containing secret metadata (i.e.A bundle of plaintext data, visible to user and server with information about the stellar accounts in the user's keybase wallet.Links in the sigchain for your primary Stellar account ID. Keys on the Keybase servers allows you to have all your Stellar accounts on all your devices. The key is then erased from memory as soon as it is no longer needed.Īlthough the keys are stored on the Keybase servers, the private keys are encrypted withĪ client-side key that the Keybase servers do not have access to. Key bundle from the Keybase servers, decrypts it to get the key, and signs the transaction. When you need a Stellar private key to make a payment, the client downloads the account Other users can find a Stellar address to send you payments. A sigchain link is created for your primary account so A bundle of all your Stellar account information When you add a Stellar account to your Keybase wallet, the private key and the name of theĪccount are encrypted by your client. The Keybase Stellar wallet keeps your Stellar account keys secure yet conveniently available
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |