> For the complete documentation index, see [llms.txt](https://docs.lambda.markets/lambda-markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lambda.markets/lambda-markets/getting-started/authentication/wallet-authentication.md).

# Wallet Authentication

<figure><img src="/files/SCkUI50QbVaPx8EyamH1" alt=""><figcaption></figcaption></figure>

## Overview

Lambda stores zero passwords or usernames on the backend database. Given this fact, we ensure to perform **hard authentication** for each and every user each time that they login.

Your blockchain wallet is public and doesn't act so much as a password, tecnhnically anyone that possesses the right skillset could send a request, faking a wallet connection that is not theirs.

{% hint style="warning" %}
How do you know the user actually connected a wallet that belongs to them?
{% endhint %}

To ensure hard verification and that there is no foul play with the authentication when entering or interacting with the Lambda app, we make use of the core of what wallets are for, signing authorisation with your private keys, like you would during any real blockchain transaction!

### Key points:

* This doesn't mean you send your private keys - thats technically impossible.We use the signing functionality native in blockchains to sign a unique message so that we can verify the signature on the backend. This is called **signed message authentication.**
* For users with a ledger, it's a bit different: we create the smallest possible SOL transaction to yourself (no one else, you can verify this on the blockchain) - this way we can verify that it is  you trying to login, as you just created that transaction and signed it with your wallet.

This is how we perform hard authentication for absolute security of access when using Lambda 2.0


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lambda.markets/lambda-markets/getting-started/authentication/wallet-authentication.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.