Solana login
Solana login, done right. On the web and on Seeker.
Sign In With Solana for every wallet in the browser, and one tap over Mobile Wallet Adapter on Seeker and every Android phone. The session stays, and a passkey or an email on the same account means a lost wallet is never a lost account.
- A message, never a transaction
- No gas, no RPC
- Every plan, the free one included
- Web, Android, React Native and Expo
The difference
Wallet login without the friction.
A typical dApp login asks for a wallet popup and a reconnect on every visit, loses the session in between, and has no way back once the wallet is lost. Synq signs people in once and keeps them signed in.
The usual dApp login: Connect, sign, and do it all again next visit
With Synq: One approval, and the session stays A returning person is still signed in: Synq’s SDKs keep the session and its refresh token, on your server with Next.js and in the phone’s secure storage in an app.
The usual dApp login: Popups, reconnect loops and lost sessions
With Synq: One tap in the wallet app on Android Mobile Wallet Adapter, on the connection your app already holds: no browser, no second connect.
The usual dApp login: Lose the wallet, lose the account
With Synq: A passkey or an email on the same account Or Google, Apple, Discord, Telegram and more. Any of them signs in to the same person.
The usual dApp login: A sign-in message nobody can read
With Synq: A plain message naming your brand Never a transaction. It costs nothing, and nothing in it can move funds.
The usual dApp login: Token checks you write, host and keep up
With Synq: Token gates set in the dashboard Synq reads Solana on its server, at every sign-in and refresh, and runs the Telegram and Discord bots.
On the web
Every wallet, signed in with a message.
Your users connect the wallet they already use and sign a message that names your brand. Synq checks the signature and the message line by line, and never asks for a transaction.
Every wallet that follows the standard
The sign-in page finds wallets through the Wallet Standard, with nothing bundled, and lists each with its own icon.
A message, never a transaction
Wallets that support Sign In With Solana show it as a sign-in. Others sign the same message. Nothing a person signs can move funds.
Checked line by line
A message for another domain, chain, nonce or time window is refused before its signature counts, and each request works once, for 5 minutes.
No email needed
A wallet is an account on its own. People can add a wallet to an account later, or add an email or a social account to a wallet.
No wallet here? Sign where it is
Telegram’s and Discord’s in-app browsers have no wallet. The page offers a link and a QR code to sign in the wallet’s own app, then carries on by itself the moment it signs.
- acme.auth.synq.build wants you to sign in with your Solana account:Your domain, checked by Synq and by the wallet
- 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsUThe address that signs
- Sign in to Acme.Your brand, by name
- URI: https://acme.auth.synq.build
- Version: 1
- Nonce: 8f2c41a07b9e4d1c9a3e5f60b2d71c84Works once
- Issued At: 2026-11-16T18:00:00.000Z
- Expiration Time: 2026-11-16T18:05:00.000ZGood for 5 minutes
Synq writes every line but the address. A signature counts only over exactly this text, for this sign-in, once.
Solana Mobile and Seeker
One tap on Seeker, over Mobile Wallet Adapter.
Android apps sign in with the wallet app on the phone, Seeker’s included: one approval, no browser, and a session that’s still there next launch. Built on @synqauth/react-native and @synqauth/solana-mobile, for React Native and Expo.
Tap Sign in with your wallet
Your app’s own button, on your own screen.
Approve in the wallet app
One approval on the authorization your app holds. No second connect.
Signed in, and it stays
The session and its refresh token go in the phone’s secure storage, so the app opens signed in.
One approval, no browser
The app asks the wallet app to sign the issuer’s request inside one Mobile Wallet Adapter session, on the authorization it holds. A returning person approves once, and Synq trades the signature for a session in place.
Keys stay in the wallet
The wallet app signs: on a Seeker, the Seed Vault Wallet, with keys kept in Seed Vault. Synq only ever gets a signature over its own message.
Connected, and kept apart
The wallet’s authorization stays in secure storage too, so the next request needs no new connect. Signing out never disconnects the wallet, and disconnecting never signs anyone out.
Seeker IDs as usernames
Someone who signs in with a wallet that has a Seeker ID, such as ana.skr, is offered it when they pick a username. A brand can turn this off.
React Native and Expo
@synqauth/react-native signs in through the system browser, Custom Tabs on Android, never a web view inside your app. @synqauth/solana-mobile adds the wallet layer on top.
Ready for the dApp Store
Ship an Expo or React Native app to the Solana dApp Store with wallet sign-in in place, and every other way in through the system browser.
In Chrome on Android
Your brand’s sign-in page lists the wallet app on the phone, beside any wallet the browser has, and reaches it over Mobile Wallet Adapter. Your own page can do the same: registerMobileWallet() from @synqauth/solana-mobile/web adds it as a wallet.
On iPhone
iOS has no Mobile Wallet Adapter, so an iPhone app can’t ask a wallet app to sign from its own screen. It signs in through your brand’s page in the system browser instead: passkeys, email codes, Apple, Google and the rest work as on any phone, and a wallet signs through a link that opens in Phantom, Solflare or Backpack, then the sign-in carries on by itself. A web page opened in a wallet app’s own browser signs in there, as on the web.
Token gates and communities
Gate access on what wallets hold.
Gate sign-in, a Telegram group or a Discord role on what people’s wallets hold and do. Synq reads Solana on its server, so your app has no chain code to write.
Gate a brand or an app
Hold enough of a token, pieces of a verified collection, one NFT, a place on an allowlist, or recent activity with a program or an address. Checked at sign-in and on every refresh.
Telegram groups and Discord roles
Point the same gate at a group or a role. Synq’s bot lets holders in, checks every member again every 6 hours, and takes access back after a grace period.
A clear reason, and a way in
Someone turned away sees each condition, what they hold, and the wallet to add. When the chain can’t be read, nobody loses access.
First on Synq
ROD.AI’s Telegram group is gated with Synq
ROD.AI, a Solana community, is the first to gate with Synq: holders of its token get in, and the members who were there before the gate have a year to verify.
The code
The code is this short.
Wallet sign-in from your own button, on the packages that are on npm today. Or link to your brand’s sign-in page and write no wallet code at all.
Next.js
npx synqauth init && npm install @synqauth/react @synqauth/solana
// synq.config.ts, with the account API on
import { defineSynqConfig } from '@synqauth/nextjs/config'
export const synqConfig = defineSynqConfig({ account: true })
// app/providers.tsx
'use client'
import { SynqProvider, type SynqProviderProps } from '@synqauth/react'
import { SynqWalletProvider } from '@synqauth/solana/react'
export function Providers({ children, ...props }: SynqProviderProps) {
return (
<SynqProvider {...props}>
<SynqWalletProvider>{children}</SynqWalletProvider>
</SynqProvider>
)
}
// app/sign-in.tsx: one signature, no page, no redirect
'use client'
import { useEffect } from 'react'
import { useWalletSignIn } from '@synqauth/solana/react'
export function SignIn() {
const { wallets, signIn, prepare } = useWalletSignIn()
useEffect(() => prepare(), [prepare]) // the request, before the tap
return wallets.map((wallet) => (
<button key={wallet.name} onClick={() => signIn(wallet)}>
{wallet.name}
</button>
))
}Turn on own-UI sign-in for the app in the dashboard. The browser never holds a Synq token: your server keeps the session. Read the guide.
React
npm install @synqauth/js @synqauth/solana
import { useEffect } from 'react'
import { createSynqClient } from '@synqauth/js'
import { type SolanaWallet, prepareSignIn, signInWithWallet } from '@synqauth/solana'
import { useSolanaWallets } from '@synqauth/solana/react'
const issuer = 'https://acme.auth.synq.build'
const clientId = 'app_…'
const synq = createSynqClient({ issuer, clientId, redirectUri: `${location.origin}/callback` })
const prepared = prepareSignIn({ issuer, clientId })
const signIn = (wallet: SolanaWallet) =>
signInWithWallet(synq, { issuer, clientId, wallet, request: prepared.take() })
export function SignIn() {
const wallets = useSolanaWallets()
useEffect(() => prepared.hold(), []) // the request, before the tap
return wallets.map((wallet) => (
<button key={wallet.name} onClick={() => signIn(wallet)}>
{wallet.name}
</button>
))
}
// On /callback
await synq.handleCallback(location.href)Register the app with a redirect URI on the page’s own origin. No wallet adapter, no web3.js and no RPC: signing in reads no chain. Read the guide.
React Native and Expo
npx expo install @synqauth/react-native @synqauth/solana-mobile @solana-mobile/mobile-wallet-adapter-protocol expo-secure-store expo-web-browser react-native-quick-crypto
import 'react-native-quick-crypto' // WebCrypto: Hermes has none
import { useEffect } from 'react'
import { Button } from 'react-native'
import { transact } from '@solana-mobile/mobile-wallet-adapter-protocol'
import * as SecureStore from 'expo-secure-store'
import * as WebBrowser from 'expo-web-browser'
import { SynqNativeProvider, createSynqNative } from '@synqauth/react-native'
import {
SynqMobileWalletProvider,
secureAuthorizationCache,
useWalletSignIn,
} from '@synqauth/solana-mobile/react-native'
const issuer = 'https://acme.auth.synq.build'
const origin = 'https://app.example.com' // the App Link your app claims
const synq = createSynqNative({
issuer,
clientId: 'app_…',
redirectUri: `${origin}/synq/callback`,
webBrowser: WebBrowser,
secureStore: SecureStore,
})
export function App() {
return (
<SynqNativeProvider synq={synq} issuer={issuer}>
<SynqMobileWalletProvider
transact={transact}
appOrigin={origin}
identity={{ name: 'Acme', uri: origin }}
authorizationCache={secureAuthorizationCache(SecureStore)}
>
<SignIn />
</SynqMobileWalletProvider>
</SynqNativeProvider>
)
}
// One approval in the wallet app, and no browser
function SignIn() {
const { signIn, prepare, pending } = useWalletSignIn()
useEffect(() => prepare(), [prepare])
return <Button title="Sign in with your wallet" disabled={pending} onPress={() => signIn()} />
}Android, Seeker included, with an https redirect URI the app claims as an App Link and own-UI sign-in on for the app. On iPhone, useAuth().signIn() opens your brand’s page in the system browser. Read the guide.
FAQ
What Solana developers ask first.
How do I add Solana login to my dApp?
What is Sign In With Solana?
Does it work on Seeker and Solana Mobile?
Does signing in cost gas?
Can users add an email or a passkey to a wallet account?
How do token gates work?
Which wallets work?
Read next
Ready for Solana login done right?
Free to start, with wallet sign-in on every plan. Or try the demo first, with no account.