Login with BLAC

Generates your signing key pair and writes .well-known/blac-session.json for you to host. That file is what lets BLAC Wallet verify your codes really come from your domain. Your private key never leaves your server.

$ npx @blaclabs/sessionkit init

Step 2

Add the kit

Load it from our CDN pinned to an exact version and its integrity hash, so the browser runs only the file you reviewed. Prefer bundling? The npm package carries full TypeScript types.

<script
  src="https://sessionkit.blaclabs.io/v1/0.2.1/sessionkit.js"
  integrity="sha384-k0P8kGYblTAtiBWRRKBJwDYcA6gPW+J3VMyDKLIZdB+Pa5Z+OvzwnR7F1X1S2OCG"
  crossorigin="anonymous"></script>

$ npm install @blaclabs/sessionkit

Step 3

Connect

Request only the scopes you need. Your backend signs the request with your domain key, SessionKit renders the BLAC Code, and the promise resolves when the user approves in the app. The quickstart has the signing endpoint.

const session = await BLACSession.connect({
  scopes: ["address:solana"],
  mount: document.getElementById("blac-connect"),
  sign: (input) =>
    fetch("/api/blac-sign", {
      method: "POST",
      headers: { "content-type": "application/json" },
      body: JSON.stringify(input)
    }).then((response) => response.json())
});

console.log(session.user.id);             // stable ID, unique to your domain
console.log(session.user.solanaAddress);  // only if granted