SOURCE_URL: https://majikah.solutions/products/majik-signature/docs/ms-signing-accounts --- title: "Signing Accounts" id: "ms-signing-accounts" group: "majik-signature" type: "products" version: "1.2.0" lastUpdated: "2026-09-19T00:00:00.000Z" difficulty: "Beginner" time: "5-8 minutes" tags: [signing-accounts, accounts, seed-phrase, signing-keys, ed25519, ml-dsa-87, post-quantum, security, identity] --- # Signing Accounts > Learn how to create, protect, manage, and use your local Signing Accounts for Ed25519 and ML-DSA-87 digital signatures. ## Overview Signing Accounts are local cryptographic identities in Majik Signature. Each account securely holds the signing keys used to create digital signatures, including Ed25519 and ML-DSA-87 signing keypairs. Your private keys remain protected locally and are used when signing files, while the corresponding public keys can be shared with others for verification. ### Understanding Signing Accounts A Signing Account is your local cryptographic identity in Majik Signature. It contains the private and public signing keys associated with that identity and is used whenever you create a digital signature. Unlike an online profile, a Signing Account is stored locally and is directly responsible for your cryptographic signing operations. ### Your Signing Keys Each Signing Account contains signing keypairs used by Majik Signature. This includes an Ed25519 keypair for classical digital signatures and an ML-DSA-87 keypair for post-quantum digital signatures. Your private keys are used locally to create signatures, while the corresponding public keys can be shared with contacts and used to verify signatures. ### Signing Keys at a Glance | Key | Purpose | Can Be Shared? | | --- | --- | --- | | Ed25519 Private Key | Creates Ed25519 digital signatures | No | | Ed25519 Public Key | Verifies Ed25519 signatures | Yes | | ML-DSA-87 Private Key | Creates post-quantum digital signatures | No | | ML-DSA-87 Public Key | Verifies ML-DSA-87 signatures | Yes | *Caption: The signing algorithms associated with a Majik Signature Signing Account* > **NOTE:** Post-Quantum Signing: ML-DSA-87 is a NIST-standardized post-quantum digital signature algorithm (FIPS 204). Majik Signature uses it alongside Ed25519 so files can carry modern classical and post-quantum signature protection. > **NOTE:** Signing Account management is available under Identity → My Keys. ### Create a Signing Account 1. **Open My Keys** *Navigate to your local signing identities* - Open Identity from the main navigation - Select the My Keys sub-tab - Click the plus (+) icon to create a new Signing Account 2. **Set Account Details** *Configure your local signing identity* - Enter a display name such as 'Personal', 'Work', or 'Company Signing Key' - Set a strong password/passphrase to protect the account locally - This passphrase is used to protect your private signing keys while they are stored on your device 3. **Create or Import Your Seed Phrase** *Establish the account's cryptographic root* - Generate a new 12/24-word BIP-39 seed phrase, or - Enter an existing compatible seed phrase to restore an account - Store your seed phrase securely because it is the recovery material for your cryptographic identity 4. **Complete Setup** - Review the account information - Click Create or the equivalent confirmation action - Your Signing Account will appear under My Keys ### Protect Your Seed Phrase > ⚠️ **WARNING:** Never share your seed phrase with anyone. Anyone who obtains it may be able to regenerate the cryptographic identity associated with your Signing Account. Store it securely offline and keep backup copies in a safe location. Losing your seed phrase may prevent you from recovering the account if the local account data is lost. ### How Your Signing Keys Are Created Your Signing Account is based on a BIP-39 seed phrase. Majik Key uses this deterministic cryptographic root to derive the account's signing identities, including the Ed25519 and ML-DSA-87 keypairs. This allows the same seed phrase to reproduce the corresponding signing identity when an account is restored. ### How Private Keys Are Protected Your private signing keys are sensitive cryptographic material and are intended to remain local to your device. Majik Signature protects stored private-key material using password-based encryption so that your passphrase protects the keys while they are at rest. Your public keys, by contrast, can be safely shared with people who need to verify your signatures. ### Never Share Private Keys > ⚠️ **WARNING:** Your Ed25519 and ML-DSA-87 private keys must remain secret. Never share private-key files, raw private-key material, or your seed phrase with another person or service. A person who gains access to your private signing keys may be able to create signatures that appear to come from your Signing Account. ### Rename a Signing Account 1. **Locate the Account** *Find the identity you want to rename* - Open Identity → My Keys - Find the Signing Account you want to rename - Hover over the account to reveal its available actions 2. **Update the Display Name** *Customize the local account label* - Click the pencil/edit icon - Enter the new display name - Click Save to apply the change > **NOTE:** Renaming a Signing Account only changes how it is displayed locally. It does not change the underlying seed phrase, public keys, private keys, or cryptographic identity. ### Set the Active Signing Account 1. **Choose Your Signing Identity** *Select which local account should sign files* - Open Identity → My Keys - Find the Signing Account you want to use - Click the star icon or equivalent account-selection control - The selected account becomes the active signing identity 2. **Use the Active Account** *Sign files with the selected identity* - When you sign a file, Majik Signature uses the active Signing Account - The account's private signing keys are used locally to create the signature - You can switch between Signing Accounts whenever you need to sign using a different identity > **NOTE:** Changing the active Signing Account changes which local signing identity is used for new signatures. It does not modify signatures that have already been created. ### View or Copy Public Keys 1. **Open Your Signing Account** - Go to Identity → My Keys - Find the Signing Account whose public key you want to share - Open the account's available key actions 2. **Copy the Public Key** *Share verification material safely* - Use the public key or copy key action - The public signing key is copied to your clipboard - You can provide it to people who need to verify your signatures or add you as a contact > **NOTE:** Public signing keys are designed to be shared. They can be used by others to verify signatures produced by your corresponding private keys. Sharing a public key does not reveal your private signing keys. ### Share Your Signing Identity 1. **Generate a Shareable Identity** *Prepare your public signing information* - Open Identity → My Keys - Find the Signing Account you want to share - Use the share/link action to generate or copy its shareable Invite Key 2. **Share with Another Person** *Let them add you to their Contacts* - Send the Invite Key through a communication channel you trust - The recipient can import the Invite Key into Identity → Contacts - They can then use your public key for signature verification or assign you as an expected signer ### Signing Accounts vs. Contacts Signing Accounts represent your own local signing identities and contain the private keys required to create signatures. Contacts represent other people's public signing identities and are used as references for signature verification and expected-signer requirements. In simple terms: My Keys signs; Contacts verify. ### Signing Accounts vs. Contacts | | My Keys | Contacts | | --- | --- | --- | | Represents | Your own signing identity | Another person's signing identity | | Private Keys | Stored locally and protected | Never stored | | Public Keys | Available for sharing | Stored for verification | | Creates Signatures | Yes | No | | Verifies Signatures | Can be used | Primary purpose | | Expected Signer | Represents your identity when selected elsewhere | Can be assigned to files | *Caption: The difference between your own signing identities and external public keys* ### Delete a Signing Account 1. **Locate the Account** - Open Identity → My Keys - Find the Signing Account you want to remove - Hover over it to reveal the available actions 2. **Delete the Account** *Remove the local signing identity* - Click the delete icon - Review the warning and confirm the deletion - The Signing Account and its locally stored key material will be removed ### Deleting an Account Can Affect Recovery > ⚠️ **WARNING:** Deleting a local Signing Account removes its locally stored key material. Make sure you have securely preserved the account's seed phrase or another supported recovery method before deleting the account. Existing signatures remain cryptographically verifiable as long as the corresponding public key is available, but you may not be able to create new signatures from the deleted identity without restoring it. ### Change the Account Passphrase 1. **Open Account Security** - Open Identity → My Keys - Find the Signing Account - Open its security/settings controls 2. **Update the Passphrase** *Re-protect your locally stored private keys* - Enter your current passphrase - Enter a strong new passphrase - Confirm the new passphrase - Save the changes - Your locally stored private signing-key material is re-protected using the new passphrase > **NOTE:** Your passphrase protects the locally stored account data, while your seed phrase is the recovery material for the underlying cryptographic identity. If you lose your passphrase but still have a valid seed phrase, you may be able to restore the Signing Account using the supported account import or recovery flow. ### Using a Signing Account Once a Signing Account is created, it can be selected whenever you need to sign a file. Majik Signature uses the account's local private signing keys to produce the requested signatures. The resulting signature can then be verified using the corresponding public key, either directly or through a saved Contact. > **NOTE:** For multi-signature files, each signer uses their own Signing Account to produce their signature. Other participants only need the corresponding public keys, typically stored through Contacts, to identify and verify those signatures. ### Quick Reference: Signing Account Actions | Action | Purpose | Requirement | | --- | --- | --- | | Create Signing Account | Create a new local signing identity | None | | Import / Restore | Recover a signing identity from supported recovery material | Valid seed phrase or supported backup | | Set Active | Choose which identity will be used for new signatures | Existing Signing Account | | Copy Public Key | Share a public signing key for verification | Existing Signing Account | | Share Signing Identity | Provide an Invite Key so another user can add the public key to Contacts | Existing Signing Account | | Rename Account | Change the local display name | Existing Signing Account | | Change Passphrase | Change protection for locally stored private keys | Current passphrase | | Delete Account | Remove the local Signing Account | Existing Signing Account | *Caption: Common Signing Account management tasks and their purposes* ### Your Signing Account Is Your Signing Identity > ⚠️ **WARNING:** Treat your Signing Account's private keys and seed phrase as highly sensitive. Anyone who gains control of the underlying private signing keys may be able to create cryptographic signatures associated with your identity. Keep recovery material offline, use a strong passphrase, and only share public keys or supported public identity information with others.