About BrainLock

BrainLock ID is a universal cryptographic authentication platform powered by your personal memories. No passwords. No devices. Just you.

Your identity is verified through episodic memories that only you possess — locations, experiences, and moments from your life.

How BrainLock Actually Works

by Christiaan Rendle April 24, 2026

BrainLock is built on a single insight that, once you see it, becomes obvious. Every existing authentication system answers the wrong question. Passwords, fingerprints, face scans, hardware keys, recovery codes — they all answer "do you have the credential." BrainLock answers "are you a real conscious human being making this decision right now." That sounds like a small distinction. It is not. It is the difference between a system that can be defeated by a clever attacker with the right object in their pocket, and a system that cannot be defeated by anyone who is not actually you.

Every digital security system in existence has the same architecture. It hands you something external — a password to remember, a phone with an authenticator app, a hardware key on your keychain, a seed phrase to write down, a recovery email account that itself has a password — and then it makes your entire digital life dependent on that external thing. The moment that external thing is lost, stolen, copied, or compromised, you are not just inconvenienced. You can be impersonated. Your accounts can be drained. Your identity can be assumed by someone who is decidedly not you, and the system has no way to tell the difference because it was only ever checking the credential.

BrainLock removes the credential entirely. Not figuratively. Architecturally. There is no password to lose, no device to depend on, no seed phrase to write down, no recovery email to compromise. The credential is your own autobiographical memory, and it goes everywhere you go.

The wrong question, the right question

Every authentication system you have ever used asks the same question. Do you possess the secret? The secret might be a string of characters you typed, a fingerprint scan that matches a stored template, a one-time code from an app, a private key sitting in hardware. The system checks the secret against what it has on file, and if they match, you are granted access.

This worked when secrets were hard to copy. It does not work in 2026. Passwords are phished, leaked, stuffed, and sold. Phones are stolen. Authenticator apps are bypassed by SIM swap attacks. Hardware keys are lost. Biometric templates are extracted from breached databases. AI-generated deepfakes increasingly defeat face and voice recognition in real time. Every credential category is in active decline as a security primitive, and the industry is openly searching for what comes next.

The question BrainLock asks is fundamentally different. Not "do you possess the secret" but "are you the conscious human being who originally enrolled, present right now, making this decision deliberately?" Answering that question requires something that no attacker can possess no matter how sophisticated their tools: the actual lived autobiographical experience of the user.

How a memory becomes a credential

The mechanism is surprisingly intuitive once you see it work. The primary authentication primitive is the geo challenge. During enrollment, the user sits with a world map and marks a small set of personally meaningful locations. Not addresses. Not places they have been. Specifically places that mean something to them — the home where they grew up, the church where a wedding happened, the hospital where a child was born, the corner where they had a conversation that changed their life. Each place is a place the user could find again because they remember the place itself, not because they memorized coordinates.

When the user clicks the map, the system captures the latitude, longitude, and zoom level at the moment of the click. Those coordinates are then snapped to a precision grid scaled to the zoom — the user does not need to hit the exact pixel, only the general area at the same zoom. The snapped coordinates are then run through a cryptographic hash with a salt unique to the user, and the resulting hash is what gets stored. The raw coordinates never touch the server. Just the hash.

To authenticate, the user is shown the same map and asked to click the same location. Their click produces the same snapped coordinates, which produce the same hash, which matches what was enrolled. They pass. Someone who does not have the autobiographical memory of where the user grew up cannot guess within the snapping tolerance, because the world is enormous and the precision required is tight enough that brute force is structurally impossible.

This works because users do not remember coordinates. They remember meaning. A user who enrolled the corner where they kissed their wife goodbye for the first time will return to that exact corner on a map a year later because the memory is anchored to the place. An attacker with no relationship to that user has no path to that corner.

Other kinds of memory

Geo challenges are the primary authentication mechanism in BrainLock — the most precise, the hardest to spoof, and the cleanest cryptographically because the comparison is an exact hash match. But the platform supports three additional challenge types that work on the same underlying philosophy: anchor authentication to autobiographical memory rather than to an external credential. The mechanics differ because the medium differs, but the principle is the same.

Image challenges let a user enroll a personal photograph along with a written description of what the image means to them. At verification, the system shows the same image and asks them to describe its meaning again. The new description does not need to match the original word for word. A local AI model running on BrainLock's own infrastructure evaluates whether the two descriptions are semantically close enough — whether they describe the same emotional content, the same memory. Two genuine descriptions of the same lived moment share enough meaning to pass. A stranger looking at the image cold, with no relationship to the memory, has no path to the same emotional content no matter how cleverly they describe what they see.

Song challenges work the same way with a different medium. The user picks a song that holds a specific memory for them — the song that was playing the night they met someone, a wedding song, a song that anchors them to a particular trip or season of their life — and writes the memory associated with it. At verification, the album artwork appears and the user describes the memory again. The same semantic comparison decides whether the two descriptions belong to the same lived experience.

Movie challenges follow the same pattern with film. The user picks a movie that holds personal significance — the first film they ever saw with someone they love, the movie a parent showed them as a child, a film whose ending changed how they thought about something. The poster appears at verification and the user writes the memory again. Same comparison, same logic, same impossibility for an attacker who has no relationship to the user's actual life.

These three semantic challenges exist for several reasons. Some users find one kind of memory easier to recall than another — some lives are anchored more strongly to songs and films than to specific physical places. Combining different challenge types also makes brute force structurally harder, because an attacker who has somehow mapped a user's likely geo locations still has no path to their meaningful songs or movies or images. The autobiographical attack surface scales with each new type rather than narrowing.

The geo challenge stays the most important — it is the foundation of the system, the one that gates the highest-stakes authentication tiers, and the one with the cleanest cryptographic comparison. The image, song, and movie challenges supplement it, particularly useful for diversifying the recall surfaces a user can draw on during routine authentication and recovery.

Friction that scales with stakes

BrainLock does not put you through the same authentication for everything. That would be exhausting and would defeat the experience. Instead, the system uses a five-tier hierarchy where the friction you encounter scales with the consequence of what you are doing.

The lowest tier is a trusted device with an active session. No friction, no prompts, no challenges. You are doing something low-stakes on a device you have used before, and the system gets out of your way. The next tier asks for a PIN. You are on a known device but the session expired or you are signing in for the day. A few keystrokes and you are in. The next tier handles unknown devices. You enter your name, date of birth, and PIN, which establishes a soft session limited to non-consequential actions until you authenticate more strongly.

The fourth tier is full authentication via geo challenges, optionally supplemented by image, song, or movie challenges depending on what is enrolled. The system asks you to complete a number of challenges, with the count determined by what you are about to do. A small number for routine consequential actions. A larger number for high-stakes irreversible decisions. This tier is what gates wire transfers, wallet drains, account changes — anything where the cost of a mistake or a fraud event would be real.

The highest tier is full recovery. All six biographical facts you provided at enrollment, plus a secret question chosen specifically for recovery, plus five geo challenges. This is what you do when you have lost your PIN entirely and need to regain access from scratch. It is structurally as strong as routine authentication at the higher tiers, which is the property that closes the recovery loophole every other system suffers from.

Where the data lives

The architecture is engineered so that no central party holds enough information to impersonate any user. The encrypted vault containing each user's authentication material lives on IPFS, a distributed file storage network. The encryption happens on the user's device, before the vault is ever uploaded, which means even if an attacker obtained the encrypted vault, they could not decrypt it without the user's recall input.

The decryption key itself is split into multiple shares using Shamir's Secret Sharing, a cryptographic technique that allows a secret to be reconstructed only when a threshold number of shares are presented together. The shares are distributed across separate storage locations such that no single location holds enough shares to reconstruct the key on its own. A breach of any one location yields fragments that are mathematically useless without the others.

The Solana blockchain holds a public lookup registry — pointers from account identifiers to the content hashes of the corresponding encrypted vaults. This provides tamper-evident references without holding any sensitive data itself. A standard PostgreSQL database holds purely operational metadata: account identifiers, audit logs, system telemetry. No biographical facts, no coordinates, no keys. A breach of the database would yield nothing useful for impersonation because nothing useful is in the database to begin with.

The combination is structural rather than promised. BrainLock does not ask you to trust that the company will not lose your data. It architects the system so that there is nothing meaningful to lose.

The recovery problem, solved

Every authentication system has a recovery flow. A flow for when you lose your password, lose your phone, lose your hardware key. In nearly every system in existence, the recovery flow is the weakest link. Email-based password reset becomes the primary attack surface. Customer support social engineering bypasses the strongest authentication. The trick attackers learn first is not how to break the front door but how to slip through the back door labeled "I forgot my password."

BrainLock's recovery is structurally as strong as its primary authentication, because it uses the same primitive. The Tier 5 recovery flow combines all six biographical facts you provided at enrollment, plus the secret question reserved exclusively for recovery, plus five geo challenges drawn from your enrolled locations. This is more cognitively demanding than any single routine login, by design. There is no email reset. There is no phone code. There is no customer support agent who can bypass it because the system itself does not have a bypass.

The result is the only authentication system ever built where the recovery surface is not the soft underbelly. Lose every device you own, lose every backup, lose every external artifact connected to your account, and you can still recover, because the recovery credential lives in your own autobiographical memory and travels with you wherever you go.

A wallet that cannot be lost

One immediate application of BrainLock is the secure storage and recovery of cryptocurrency seed phrases — a problem that has accidentally caused billions of dollars to become permanently inaccessible because users wrote down a recovery phrase and then lost the paper. BrainLock wallets replace the seed phrase entirely with the same authentication primitive. There is nothing to write down. Nothing to lose. Nothing to be stolen. Recovery happens through the same BrainLock flow that authenticates routine transactions, which means a user who loses their phone and their backup paper and their hardware wallet still has access to their funds, because the credential lives in their memory.

For high-value transfers, BrainLock can be configured to require additional geo challenges before signing. This puts deliberate friction in the path of any irreversible large action, which is the friction that should always have been there but never was, because every other wallet treated authentication as a one-time unlock rather than a per-action verification.

This is the first cryptocurrency wallet in existence where the recovery credential cannot be lost, stolen, or destroyed by any physical event. It is only possible because BrainLock exists underneath.

BrainLock as a layer

BrainLock is not designed to be the destination application. It is designed to be the layer that other applications integrate, the way Stripe sits beneath payment flows or Auth0 sits beneath login screens. Any application that needs to verify conscious human presence at a moment of consequential action can integrate BrainLock through a clean API. Banks verifying wire transfers. Crypto exchanges verifying wallet recovery. Healthcare systems verifying patient access. Autonomous AI agents verifying that a human actually authorized the action they are about to take.

The integration is straightforward. The application redirects the user to BrainLock for authentication, specifying how many challenges the user must complete based on the stakes of the action. BrainLock authenticates the user, issues a signed token attesting to the verification, and returns the user to the application. The application verifies the signature and proceeds.

This positions BrainLock as a foundational layer rather than a consumer destination. The commercial value lives in being the layer that sits between users and consequential actions across many industries, sold to enterprises in the way any serious authentication or identity company operates. The technology is patented in a category that no other system occupies, which makes it durable as a commercial asset rather than something that can be rapidly cloned by a competitor.

Why this matters now

The world is moving into a period where standard authentication is structurally insufficient. Several forces are converging to make this true at the same time.

Deepfakes have crossed from research demonstrations into operational threats. Voice cloning takes seconds. Real-time video synthesis is operationally deployed by state actors and fraud rings. Biometric authentication, which the industry spent decades building toward, is being undermined by the same AI advances that created the deepfakes. A face is no longer proof of presence. A voice is no longer proof of identity.

Autonomous AI agents are beginning to act on behalf of users at scale. Enterprise software increasingly integrates LLM agents that can read email, schedule meetings, transfer funds, and authorize purchases. The authentication assumption underneath all of this is that the user authorized the agent to act on their behalf, but there is currently no mechanism to verify that any specific action carried genuine human intent at the moment of execution. The liability gap is enormous and growing every quarter.

Recent high-profile breaches demonstrate the problem concretely. Senior officials with compromised messaging accounts. Sitting intelligence officials with breached email. Crypto holders losing seven-figure positions to SIM swap attacks. These are not edge cases. They are the routine failure modes of an authentication model that asks "do you have the credential" rather than "are you the conscious human making this decision."

BrainLock answers this need with a primitive that the industry has not had access to before. A credential that cannot be lost, cannot be stolen without the user's conscious cooperation, and cannot be impersonated by AI. It is the authentication layer the world is structurally going to need, and it exists now, in active development, ninety percent complete, with a US provisional patent filed in March 2026 in a category no other system occupies.

What is being built

The technology stack reflects deliberate choices about security, performance, and long-term maintainability. The backend runs on Go with the Chi router, a combination chosen for its concurrency model, memory safety, and fast compilation. Cryptography is handled by libsodium and Argon2id, both industry-standard libraries with proven track records. Sensitive material is split using Shamir's Secret Sharing and stored encrypted on IPFS, anchored on Solana, with PostgreSQL holding only non-sensitive operational metadata. Local AI inference runs on Ollama with LaBSE for the semantic comparison that powers image, song, and movie challenges, ensuring that no recall material is ever sent to a remote inference API. The end-user application is built in Flutter for cross-platform support, with the developer-facing API exposed as a clean SDK that any application can integrate.

The work ahead is the completion of the remaining ten percent of the core implementation, the ongoing operation of BrainLock as the authentication layer beneath Splash — the first major consumer application built on top of it — and the parallel commercial development of BrainLock as an enterprise authentication platform across the industries that need this category of verification.

The BrainLock patent is filed. The architecture is in active development. What exists is a coherent technical answer to a problem the world increasingly cannot afford to leave unsolved.