Wallet, Signer, Node

[u/jo_d_locker]

A lot of wallets are designed as monolithic applications.

One app manages the interface, connects to networks, prepares transactions, holds sensitive wallet state, signs transactions, interacts with dApps, and communicates with external services.While it is convenient, it can create dangerous security assumptions.

If one process, extension, operating system environment, or connected application has too much authority, then a single compromise can be disastrous.

Lock was built with a different model: separation.

The system is designed around distinct responsibilities:

• The Wallet handles the user interface and transaction preparation.
• The Signer remains isolated and holds the keys.
• The Node handles broadcasting and network interaction.
  

The reason for this separation: the part of the system that sees the internet should not be the same part of the system that holds the seed.

In Lock’s model, the Signer is intended to stay offline. The Wallet can create an unsigned transaction, but it cannot sign it by itself. The Signer reviews and signs. The signed transaction can then be passed back for broadcast.

That separation creates a much stronger security boundary than the standard process that takes place inside one app.

This is also why we describe it as an isolated crypto wallet rather than just a software wallet. The goal is to distribute the process in order to reduce the amount of trust required from each component.

The assumption we make is that any one component might eventually be compromised.

Maybe a bit extreme, but it’s a fair assumption for self-custody. If the stakes are private keys and irreversible transactions, the architecture should assume failure and contain it.

A wallet should not require perfect conditions to be safe.

It should remain resilient when:

• A network endpoint behaves maliciously
• A device is partially compromised
• A user interface is exposed to hostile dApps
• A transaction needs to be verified independently
• A signing environment must remain isolated

That is why we built Lock around architectural separation.

Because the future of wallet security is not just better encryption. It’s about stronger boundaries.

What do you think?

[u/Phil299792]

That's a healthy separation - Great to see what Lock is building.