In this article
Every settlement professional, escrow officer, OTC desk, and title company that has started accepting crypto payments eventually runs into the same question: who holds the keys, and how do we make sure they are still there in two years? The answer starts with understanding what a seed phrase actually is — not at a surface level, but mechanically — and then building a storage strategy that fits how a business operates rather than how a solo developer operates.
This article covers both. It explains the cryptography in plain language, maps the real failure modes that have cost businesses real money, and lays out a layered storage framework that a compliance-conscious firm can implement today.
The mechanics: what a seed phrase actually is
A seed phrase — also called a recovery phrase, secret phrase, or mnemonic phrase — is a random set of words generated by your crypto wallet when you create it. This sequence of words serves as the master key to all your cryptocurrency funds and accounts.
The technical standard behind almost every modern wallet is BIP-39, introduced in 2013. The words come from a fixed set of terms called the BIP39 word list and are auto-generated when you open your wallet for the first time. The phrase is generated from a fixed list of 2,048 words. That list was designed deliberately: it minimises any potential confusion by avoiding similar-sounding words and keeping all words between four and eight letters long.
The phrase is randomly generated and consists of a series of 12 to 24 words chosen from a predefined list. The entropy behind those words is substantial. A 12-word seed phrase has 2¹²⁸ possible combinations. Even checking one trillion guesses per second, it would take longer than the age of the universe to try all possibilities. 24 words provide 256 bits, offering additional theoretical margin. For practical purposes, both lengths are effectively uncrackable by brute force.
The process that turns those words into usable wallet credentials is deterministic and hierarchical. When a wallet is created, the software generates a unique seed phrase. This phrase is then used to derive all the private keys associated with your wallet addresses.
- Seed phraseYour wallet generates your seed phrase using that process, which you write down and store securely.
- SeedThe seed phrase is hashed to produce a seed — a unique sequence of numbers and letters.
- Master keyFrom your seed, your wallet creates a master key (the master private key), which serves as the main input to create private keys.
- Private keysFrom the master key, countless unique private keys can be created, which are used to authorise transactions.
The critical downstream implication for businesses is this: the seed phrase generates a deterministic wallet structure, meaning the same phrase will always produce an identical set of addresses and private keys across any compatible wallet software. This is both the system's greatest strength and its greatest liability. It means recovery is always possible — but so is theft, if the phrase is exposed.
Seed phrases follow the widely used BIP39 standard, which defines how these words are created and used to recover crypto wallets. This means you can often use your seed phrase to restore your wallet across different apps as long as those apps support the same standard. That portability matters in practice: if a vendor discontinues software, or a hardware device fails, the phrase travels cleanly to a new tool.
Seed phrase vs. private key: the distinction matters
Many professionals encounter both terms and conflate them. They are related but not the same thing. A private key is a long string of alphanumeric characters generated when you create a cryptocurrency wallet. It is a secret key that should be kept confidential and never shared with anyone. A seed phrase is a set of words from which your private keys are derived using a specific algorithm. It acts as a human-readable backup of your private keys, making it easier to back up and restore your wallet.
Think of the private key as a single door key — it opens one address. The seed phrase is the master blueprint from which every key in the entire building can be cut. The benefit of this system is that you only need to secure one thing — your seed phrase. From this single phrase, your wallet can recreate every address and access your funds across multiple blockchains.
What happens if the seed phrase is lost
If you lose your seed phrase and no longer have access to your wallet through other means, your cryptocurrency is permanently inaccessible. There is no recovery process, no customer service intervention, and no technical workaround. This is by design: the cryptographic security that protects your funds from attackers also means there is no backdoor for recovery.
The scale of this problem across the industry is staggering. According to the analytics firm Chainalysis, as of 2026, approximately 20% of all Bitcoin ever issued — more than 3.8 million BTC — is considered permanently lost. That is hundreds of billions of dollars locked in digital space due to basic human error: users lose their seed phrases. Businesses are not immune. They are, if anything, more exposed — because key custodianship sits with individuals who leave, retire, or are simply not around the day the wallet needs to be accessed.
Why business seed phrase management is a different problem
Consumer guidance for seed phrase security — write it on paper, put it in a drawer, tell no one — is not wrong, exactly. It is just incomplete for any organisation with more than one person involved in treasury operations.
A business faces risks that an individual does not:
Staff turnover. The employee who generated the wallet is gone. Did they document the seed phrase? Where? Did they store it somewhere only they could access? If your organisation holds more than a few thousand dollars of crypto, single-signature wallets are no longer appropriate. One compromised laptop, one phished founder, one disgruntled employee with key access — and the treasury is gone.
Concentration risk. If one person holds the entire seed phrase and is the sole signatory, the organisation has created a single point of failure that is also a single target for social engineering. According to Chainalysis data, 73% of crypto thefts in 2026 resulted from single points of failure — one key, one device, one mistake.
Operational continuity. Businesses need to access funds predictably, not just in emergencies. A seed phrase stored in a safety deposit box that only one executive can access is fine until that executive is unavailable during a time-sensitive settlement.
Auditability. Regulated firms — broker-dealers, title companies, settlement agents — need demonstrable controls. "The CFO has it written in a notebook" is not an audit-ready answer.
Finality. Onchain payments are final. Once a transaction is signed and broadcast, it settles. There is no reversal mechanism, no dispute window. This means every control must exist before the transaction, not after. When shaka.deal routes a deal payment and splits it in one transaction to every party at preset shares, that payout is done the moment it confirms. The seed phrase protecting the originating wallet is, in that sense, also protecting the integrity of the settlement flow itself.
These pressures push businesses toward a set of well-defined storage architectures. The right choice depends on the size of the organisation, the frequency of on-chain activity, and the regulatory context.
The four storage layers and when to use each
Layer 1: Air-gapped physical backup
The best way to store a seed phrase is to physically write it down on durable materials like fireproof and waterproof metal plates and store multiple copies in separate, secure locations such as a home safe, safety deposit box, or a trusted offline storage solution. Never store seed phrases in a non-encrypted digital format, including cloud storage, notes apps, or screenshots, to prevent exposure to malware, phishing, and hacking risks.
Steel or titanium plates do not burn or get damaged by water. Products like Cryptosteel and similar stainless-steel engraving tools are widely used for exactly this reason. For a business, the physical backup is the baseline — but the question is who has access to it, under what conditions, and how access is logged.
A practical rule: physical backups should be stored in locations controlled by the organisation (a company safe, a bank vault under the company's name), not in a personal location controlled by an individual employee. If the employee leaves, the company should retain access to its own credentials.
Store your backup in a fireproof and waterproof lockbox, a home safe, or a bank safe deposit box. If possible, keep a second backup in a different secure location to protect against local disasters. For a business this means geographic separation: one set of backups at the primary office, a second at a separate facility or bank branch. The goal is to survive any single physical event — fire, flood, theft — without losing access.
Layer 2: Shamir's Secret Sharing
Physical duplication helps with loss and disaster, but it multiplies the attack surface. Every additional paper copy is another location where the entire secret can be stolen. Shamir's Secret Sharing (SSS) solves this elegantly.
Shamir's Secret Sharing (SSS) is a cryptographic scheme invented by Adi Shamir in 1979 to solve the problem of safeguarding a secret without a single point of failure. It allows a secret to be split into multiple parts called shares, which are distributed to different participants or locations. The critical property is that only when a sufficient number of these shares are combined — reaching a predetermined threshold — can the original secret be reconstructed. Any group with fewer than the threshold number of shares learns nothing useful about the secret.
To use Shamir Backup, a user first selects the number of shares they want to create and the threshold required to reconstruct the seed phrase. For example, a user may choose to create five shares with a threshold of three. This means that a user can lose two shares and still recover the wallet with the three remaining shares.
This is the fundamental tension of seed backup: redundancy increases availability but decreases security. Shamir's Secret Sharing offers a mathematically elegant solution. Instead of storing one secret in one place, you split it into N shares where any K of them can reconstruct the original, but K-1 or fewer reveal absolutely nothing.
For a business, the practical structure looks like this: a 3-of-5 split, where shares are held by the CFO, an attorney, an operations director, an external auditor or custodian, and one physical safe controlled by the board. Any three can reconstruct. Two shares, whether stolen, lost, or held by a departing employee, give an adversary nothing actionable. If two shares are lost, you can still recover your funds with the remaining three; and if two shares are stolen, the thief gets nothing useful without a third share.
Applied to Bitcoin through the SLIP-39 standard, this approach eliminates the single point of failure without sacrificing recoverability. Adoption of SLIP-39 has grown steadily since its introduction. In June 2024, Trezor made Shamir Backup the default backup method for all Safe Family devices, signaling confidence in the standard's maturity.
The SLIP-39 standard is specifically built for wallet recovery and should be distinguished from informal seed phrase splitting — that is, manually cutting the word list into thirds. Manual splitting is not cryptographically equivalent to SSS. Someone with the first eight words of a 24-word phrase gains partial information that narrows the search space significantly. With true Shamir sharing, if you have fewer points than the threshold, there are infinitely many possible curves — meaning the secret could be literally anything; it is information-theoretically secure.
Layer 3: Multisignature wallets
Shamir's Secret Sharing protects the backup of a seed phrase. Multisignature wallets take a different approach: instead of managing a single key more safely, they require multiple independent keys to authorise any transaction in the first place.
A multisig (short for multisignature) wallet is a type of crypto wallet that requires more than one key to authorize a crypto transaction. Unlike single-signature wallets where one key means full control, multisig eliminates single points of failure. Common setups include 2-of-3 and 3-of-5, where m signatures from n total signers unlock funds.
Each signing key has its own seed phrase. Those seed phrases must each be stored securely — so multisig does not eliminate seed phrase management, it multiplies it by the number of signers. But it fundamentally changes the threat model: multi-signature wallets fix this by requiring multiple independent signers to approve any transaction.
Safe remains one of the strongest choices for EVM teams and on-chain treasuries. Its wallet supports multi-owner approvals, role-based access, multichain treasury management, transaction simulation, spending limits, and onchain N-of-M signing. Safe also positions itself as a self-custody wallet for organisations and power users rather than a simple consumer wallet.
Enterprise applications include treasury management, DAO governance, escrow services, and partnership fund control. For a settlement agent or title company managing Ethereum-based deal flows, a 2-of-3 multisig where two authorised officers must co-sign any disbursement is a direct structural analogue to the dual-signatory controls that govern wire releases in traditional practice.
Regulated operators evaluating multisig in 2026 face wider chain coverage, stricter compliance scrutiny, and a deeper bench of platforms than two years ago. The question is no longer which wallet is safest, but which infrastructure fits the way your business moves money. For EVM-native firms whose deal routing runs through shaka.deal — where the smart contract handles distribution and every party receives their share in the same block — the wallet holding the originating funds still needs multisig governance. The router handles the split; the wallet controls what enters it.
Layer 4: Hardware Security Modules for large-scale operations
For firms operating at institutional scale — OTC desks, clearing firms, large property transaction platforms — physical seed phrase storage eventually gives way to dedicated hardware.
An HSM is a dedicated security device designed to protect and manage cryptographic keys for enterprise, cloud, and high-assurance use cases. A hardware security module is a hardware unit that stores cryptographic keys to keep them private while ensuring they are available to those authorised to use them. The primary objective of HSM security is to control which individuals have access to an organisation's digital security keys. With HSM encryption, you enable your employees to use your private keys without granting them direct access. Used this way, HSMs help reduce your attack surface.
An HSM is a purpose-built device engineered to execute cryptographic operations like data encryption and key management. Using strong encryption standards, tamper-evident design, and crypto-agile frameworks, HSMs safeguard an organisation's most critical digital assets against evolving threats.
The practical implication: an HSM never exposes the private key material to any software layer. Signing operations happen inside the module itself. An attacker who compromises the application server gains nothing, because the key is not there. For a firm processing a high volume of onchain transactions — whether routing split payments across hundreds of deals or managing treasury rebalancing — an HSM represents the ceiling of seed phrase security.
The recommendation for businesses is to implement multisig or distributed storage models with regulated access and internal controls. At scale, that recommendation extends naturally to HSMs or institutional custody platforms that combine hardware-level key protection with auditable approval workflows.
Building a seed phrase governance policy
Technology alone does not protect a business. Policy is what turns good tools into reliable controls. A seed phrase governance policy for a business should cover at minimum five areas:
1. Generation hygiene. Seed phrases must be generated on air-gapped devices — hardware wallets, dedicated offline machines — never in browser extensions, mobile apps, or cloud-connected environments on the day of generation. A common misconception is that digitally storing your seed phrase is as secure as writing it down on paper. While digital storage solutions may offer convenience, they also introduce additional vulnerabilities. Storing your recovery phrase on a computer or in the cloud increases the risk of it being compromised by hackers or malware.
2. Custodian assignment. Every seed phrase must have a named custodian, a named backup custodian, and a documented handover procedure triggered by role changes. When a CFO is replaced or a closing officer leaves, the relevant seed phrase or Shamir share custody must be formally transferred and the previous holder's copy retired.
3. Access logging. Any time a seed phrase or share is accessed — for recovery testing, for wallet migration, for any reason — the event must be logged with date, time, and reason. This is the same discipline applied to master key logs in physical security environments and it maps directly to internal control frameworks that auditors expect.
4. Recovery testing. Test wallet restoration using small amounts first. A seed phrase backup that has never been tested is not a backup — it is an unverified hypothesis. Businesses should schedule annual (or more frequent) recovery drills on test wallets, confirming that each Shamir share combination, each hardware backup, and each custodian actually works before it is needed in an emergency.
5. Incident response. If someone sees your seed phrase, that wallet is not safe anymore. Stop using it. Waiting will not help. Shift everything fast to another wallet with a brand-new recovery phrase. The policy must define who makes that call, what the escalation path is, and how counterparties are notified if an active settlement wallet is compromised mid-deal.
A concrete scenario: a property settlement firm on Ethereum
Consider a property settlement firm that has adopted onchain settlement for commercial real estate transactions. A typical deal involves a buyer, a seller, two brokers, and a title company. The firm uses shaka.deal to route the total transaction amount in one Ethereum transaction, splitting it instantly to all five parties at preset shares — simultaneous, final, no manual wire sequencing.
The firm's treasury wallet, which receives the buyer's funds and triggers the routing, holds anywhere from $500,000 (AUD 770,000) to $4,000,000 (AUD 6,150,000) at any given time. That wallet has a seed phrase.
How should they store it?
The wallet itself is a 2-of-3 multisig on Safe. Three authorised signatories — the settlement principal, the operations manager, and an external legal counsel — each hold a separate hardware wallet. Any two must co-sign to move funds. Each hardware wallet has its own seed phrase.
The seed phrases for each signer are stored using a 3-of-5 Shamir split. Five shares are produced. Three are distributed to company-controlled, geographically separated fireproof safes (head office, secondary office, bank vault). Two are held by named individuals. Any three of the five reconstruct the phrase. An attacker would need to physically breach three separate secure locations to reconstruct even one of the three signer seeds — and reconstructing one still gives them only one of the two signatures required to transact.
Recovery testing is performed quarterly on a testnet wallet. Each Shamir combination is verified. The multisig co-signing workflow is tested. The documented procedure is updated after every staff change.
The governance policy is reviewed annually by the firm's compliance officer and forms part of the documentation package provided to their professional indemnity insurer.
The routing logic — how the deal total divides among the parties — sits in the smart contract called by shaka.deal, not in the wallet. The wallet's only job is to authorise the transaction that feeds the router. That means the seed phrase governance protects not just the firm's treasury but the integrity of every deal settled through the platform.
What to avoid
The following failures are common, documented, and entirely preventable.
Screenshots and cloud photos. The moment a seed phrase is captured as an image and uploaded to a cloud service, it is accessible to anyone who compromises that account. Digital storage is the riskiest method. Screenshots, cloud services, email drafts, and password managers are all easy to compromise.
Email or messaging apps. Sending a seed phrase via email, Slack, WhatsApp, or any networked channel creates a persistent copy in multiple server logs, none of which are under the firm's control.
Single-person custody without succession planning. This is not a security failure, it is an operational continuity failure — and it is equally destructive. If the one person who knows where the phrase is stored becomes unavailable, the business loses access to its own funds.
Fake wallet software. Be wary of fake wallet applications and browser extensions designed to look like legitimate ones but programmed to steal your credentials. Always download wallet software from official websites, verify URLs carefully, and double-check app developers on official app stores.
Word order errors. "The order matters absolutely. 'Apple banana cherry' and 'cherry banana apple' generate completely different wallets." If you forget the order, you would need to test all possible orderings — for 12 words, that is 479 million combinations. Every physical backup must record both the words and their numbered sequence.
The operational logic
Professional settlement infrastructure has always had a key management dimension. Settlement agents maintain dual-control over disbursement accounts. Escrow officers follow documented procedures for releasing funds. Title companies maintain records that outlast individual employees. None of that changes with onchain settlement — it deepens.
The difference is that an onchain payment routed through shaka.deal is final the moment it confirms on Ethereum. There is no wire recall, no bank-side reversal window, no correspondent bank to call. That finality is a feature — it gives every party in a multi-stakeholder deal simultaneous certainty the moment the transaction lands. But it places the entire weight of access control on what happens before that transaction is signed. The seed phrase, and the governance around it, is where that weight rests.
A firm that builds rigorous seed phrase governance — layered physical backups, Shamir distribution, multisig signing, policy, and testing — is not over-engineering. It is applying to onchain assets the same professional discipline it already applies to every other form of client value under its care. That discipline is what makes onchain settlement trustworthy at scale, and it is the foundation on which tools like shaka.deal can deliver the speed and certainty that every party in a deal deserves.
