Server-side rendering

⚠️ Common Issue: If SSR is not set up correctly, you may see sessions resetting or users getting logged out unexpectedly. Make sure to follow this guide fully to preserve session state.

When using Smart Wallets in a server-side rendered setting, you may see inconsistencies in account state between the server and the client. This leads to flashes of content when logged in. To avoid this, load the account state optimistically on the server and pass it to the client.

To enable server-side rendering support, you need to set ssr: true when creating a config.

When using React, make the config a function so that you can call it once per request, which allows for request-based isolation of the account state.

import { createConfig } from "@account-kit/react";
import { sepolia, alchemy } from "@account-kit/infra";
 
export const config = () =>
  createConfig({
    // required
    transport: alchemy({ rpcUrl: "/api/rpc" }),
    chain: sepolia,
    ssr: true,
  });

This setting will defer hydration of the account state to the client after the initial mount.

To consistently pass the state between the server and the client, pass in a cookie storage to the config object created above. The cookie storage allows the client state to be serialized to a cookie which is passed to the server on each request. This gives the server access to certain parts of the account state when rendering, ensuring a consistent render between client and server (e.g. address displayed in the top nav). Instances that can only be created on the client are still not available on the server, however. This includes the authentication or smart wallet instances.

import { createConfig, cookieStorage } from "@account-kit/react";
import { sepolia, alchemy } from "@account-kit/infra";
import { QueryClient } from "@tanstack/react-query";
 
export const queryClient = new QueryClient();
 
export const config = () =>
  createConfig({
    // required
    transport: alchemy({ rpcUrl: "/api/rpc" }),
    chain: sepolia,
    ssr: true,
    storage: cookieStorage,
  });

Now, depending on your application, you can get the state from cookies and pass in the initialState to the AlchemyAccountProvider to hydrate the account state on the client.

If you are using Next.js App Directory, read the cookie state and pass it to the providers:

// @noErrors
import React from "react";
import { cookieToInitialState } from "@account-kit/core";
import type { Metadata } from "next";
import { Inter } from "next/font/google";
import { headers } from "next/headers";
import { config } from "./config";
import "./globals.css";
import { Providers } from "./providers";
 
const inter = Inter({ subsets: ["latin"] });
 
export const metadata: Metadata = {
  title: "Embedded Accounts Getting Started",
  description: "Embedded Accounts Quickstart Guide",
};
 
export default function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode;
}>) {
  // This will allow us to persist state across page boundaries
  const initialState = cookieToInitialState(
    // the config here is just used to compute the initial state
    config(),
    headers().get("cookie") ?? undefined,
  );
 
  return (
    <html lang="en">
      <body className={inter.className}>
        <Providers initialState={initialState}>{children}</Providers>
      </body>
    </html>
  );
}

import { createConfig } from "@account-kit/core";
import { sepolia, alchemy } from "@account-kit/infra";
 
export const config = createConfig({
  transport: alchemy({ apiKey: "ALCHEMY_API_KEY" }),
  chain: sepolia,
  ssr: true,
});

This setting defers hydration of the Smart Wallets state until you call the hydrate method on mount.

Now that you've set up your config for SSR, manually hydrate the state on the client. Call the hydrate method exported by Smart Wallets core.

import { hydrate } from "@account-kit/core";
import { config } from "./config";
 
const { onMount } = hydrate(config);
 
// when your component has mounted on the client, call the onMount method
// how you do this will depend on your framework, but here we'll just check for `window`
// to be defined
if (typeof window !== "undefined") {
  onMount();
}

import { createConfig, cookieStorage } from "@account-kit/core"; // Add cookieStorage import
import { sepolia, alchemy } from "@account-kit/infra";
 
export const config = createConfig({
  transport: alchemy({ apiKey: "ALCHEMY_API_KEY" }),
  chain: sepolia,
  ssr: true,
  storage: cookieStorage,
});

Now you can get the initial state from cookies and pass it to the hydrate method to hydrate the account state on the client or on the server.

import { cookieToInitialState, hydrate } from "@account-kit/core";
import { config } from "./config";
 
// this is an example of how to get the cookie on the client
// but on the server you might get it from the `req.cookies` object
// it all depends on your framework
const initialState = cookieToInitialState(config, document.cookie);
const { onMount } = hydrate(config, initialState);
 
if (typeof window !== "undefined") {
  onMount();
}

Server-side rendering

Update your config

Persisting the account state

Cookie storage

Next.js App Directory

Hydrate the account state

Persisting the account state