Security for assets that cannot be reversed

Start with signing. A machine used to authorize transactions should do nothing else: a clean operating system, no email client, no browser extensions, no messaging apps, application allowlisting so unexpected code cannot run, full disk encryption, and a limited set of network destinations. For higher-value operations that machine should be physically separate and, where the workflow supports it, air-gapped with transactions moved by QR code or removable media under a controlled process. The compromise pattern we see repeatedly is a general-purpose laptop used for signing because it was convenient.

Key handling is a procedure problem more than a product problem. Hardware wallets, multisignature arrangements and threshold or multi-party signing all reduce single points of failure, but only if the surrounding process is real: quorum requirements that cannot be satisfied by one person, seed material recorded on metal rather than paper and stored in geographically separated locations, documented recovery drills that have actually been rehearsed, and a clear rule that no seed phrase is ever typed into a computer, photographed or stored in a password manager. We help design and document those procedures alongside your team, and we implement the technical controls around them.

Social engineering is the dominant threat and it is targeted rather than opportunistic. Fake recruiters sending malware-laden take-home assignments, Discord and Telegram administrator takeovers, support impersonation, and voice or video impersonation of a founder authorizing an urgent transfer. Mobile number porting is a specific and severe risk: anyone using SMS as a second factor is one carrier social-engineering call away from account takeover. We move every account we can to FIDO2 hardware security keys, remove SMS as a recovery method, help you set port-out protection and account PINs with your carrier, and run realistic phishing exercises against your team.

Node and infrastructure operations need ordinary engineering discipline applied carefully. Validators and RPC nodes require predictable uptime, monitored resource usage, redundant network paths, hardened remote access with no exposed management ports, tight key separation between operational and withdrawal functions, and alerting that reaches a human quickly. Registrar and DNS security matters more here than almost anywhere, because a hijacked domain pointing at a lookalike front end is a direct path to user funds, so registrar locks, strong registrar account protection and DNSSEC where supported are part of the baseline.

Treasury operations deserve separation of duties. Cold, warm and hot tiers with defined limits, address allowlisting, a maintained internal address book so nobody pastes an address from a chat window, mandatory small test transactions before large transfers, and dual approval that is enforced technically rather than culturally. We are an IT and security firm. We do not hold keys, take custody or offer financial advice. What we do is build the environment those controls run in. Our full stack is described under Pod Guard, with more at our blockchain IT microsite.