> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/get-started/build-a-frontend/authentication.md).
# Authentication
Authenticating (connecting wallets) with a Stacks-supported wallet is a common task when building Stacks apps. On a web2 app, authentication usually means sending credentials to a central provider, which then verifies you and controls access. In web3, authentication uses a wallet and cryptographic signatures with libraries like stacks.js, letting users prove identity without a central party holding the keys.
{% hint style="info" %}
To learn more about how wallets and accounts work with Stacks, check out this [section](/learn/network-fundamentals/wallets-and-accounts.md) in Learn.
{% endhint %}
Below is a simple example showing how to set up front-end authentication with `@stacks/connect` and access user data in the UI. The stacks.js monorepo contains several underlying packages specific to different use cases. The package `@stacks/connect` is the main connectivity package used in Stacks.
## Authentication on the frontend
Using `@stacks/connect` on the frontend will allow our frontend app to authenticate wallets, call our contract functions, and interact with the Stacks network.
In the snippet below, you'll notice we have 3 functions setup to handle `connectWallet` , `disconnectWallet`, and for `getBns` . All 3 functions will be integral in how we want to display the 'Connect' and 'Disconnect' button in the UI.
{% hint style="info" %}
Retrieving a wallet account's associated [BNS](/learn/network-fundamentals/bitcoin-name-system.md) is a staple of Stacks and for web3 identity. Check out [BNSv2](https://www.bnsv2.com/) for more information and for availably public API endpoints you could use.
{% endhint %}
import { connect, disconnect } from '@stacks/connect'
import type { GetAddressesResult } from '@stacks/connect/dist/types/methods'
import { useState } from 'react'
function App() {
let [isConnected, setIsConnected] = useState<boolean>(false)
let [walletInfo, setWalletInfo] = useState<any>(null)
let [bns, setBns] = useState<string>('')
async function connectWallet() {
let connectionResponse: GetAddressesResult = await connect()
let bnsName = await getBns(connectionResponse.addresses[2].address)
setIsConnected(true)
setWalletInfo(connectionResponse)
setBns(bnsName)
}
async function disconnectWallet() {
disconnect();
}
async function getBns(stxAddress: string) {
let response = await fetch(`https://api.bnsv2.com/testnet/names/address/${stxAddress}/valid`)
let data = await response.json()
return data.names[0].full_name
}
return (
<>
<h3>Stacks Dev Quickstart Message Board</h3>
{isConnected ? (
<button onClick={disconnectWallet}>{
bns ? bns : walletInfo.addresses[2].address
}</button>
) : (
<button onClick={connectWallet}>connect wallet</button>
)}
</>
)
}
The `connect()` method comes with the ability to configure how you want the wallet selector modal to appear for your app. You can decide which wallets to have only appear as an option or allow any wallet that follows the SIP-030 standard to appear as an available Stacks wallet.
For the complete guides check out the [Stacks Connect](/stacks-connect/connect-wallet.md) section.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.stacks.co/get-started/build-a-frontend/authentication.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
