Authentication Methods

Logbook supports two ways to authenticate: zkLogin with Google and traditional crypto wallets.

#zkLogin with Google

zkLogin is a technology developed by Mysten Labs that allows you to use your Google account as your blockchain identity.

#How It Works

1. 1You click "Continue with Google"
2. 2You sign in with your Google account
3. 3Behind the scenes, a unique blockchain address is computed from your Google identity
4. 4A zero-knowledge proof lets you sign transactions for that address without your Google account appearing on the blockchain

#Benefits

• No wallet needed: Use your existing Google account
• No crypto knowledge required: Works just like any other Google sign-in
• Secure: Your Google password is never shared with Logbook
• Consistent addresses: Your Google account gives the same account address at every sign-in, and from it this site derives the same address for each community (a group and the groups inside it): one address outside communities, and one in each community

#Address Uniqueness

Your zkLogin address is unique to each application. The same Google account will generate different blockchain addresses in different dApps, so different applications cannot link your accounts by comparing addresses.

Outside communities it is one address: every campaign that is not for a group shows it when you respond. In each community (a group and the groups inside it) you act under an address made for that community alone, which this site derives for you. What an address did is public, so anyone can put it together, and whoever learns your name for it in one place (a member card, a list) knows it for everything that address did.

#Privacy

zkLogin uses zero-knowledge cryptography. This means:

• Logbook never sees your Google password
• The blockchain doesn't store your email or your Google account

What it does not mean:

• Mysten Labs can tell which Google account has which address. Its Enoki service computes your address from your Google sign-in token, at every sign-in and for every proof. What Enoki keeps, and for how long, is Mysten's policy
• Google knows that your account signed in to Logbook, and when
• Logbook's server passes the token on to Enoki and does not store it (a finished proof is cached for 10 minutes). Your browser keeps the token, with your email in it, until you sign out
• A wallet instead of Google takes Mysten's sign-in service and Google out of this; then the wallet's own history says what it says

#Crypto Wallets

If you prefer using a traditional crypto wallet, Logbook supports many popular options:

#Supported Wallets

• Slush (formerly Sui Wallet)
• Phantom
• Suiet
• OKX Wallet
• Backpack
• Martian
• Nightly
• Any other wallet that supports the Sui Wallet Standard

#How to Connect

1. 1Click "Log in" on the homepage
2. 2Select your wallet from the list
3. 3Approve the connection request in your wallet

#Benefits

• Full control: You manage your own keys
• Use existing wallet: If you already have a Sui wallet, use it directly
• Advanced features: Access to all blockchain features

#Mobile Devices

On mobile phones, wallet browser extensions are not available. To connect with a crypto wallet on mobile:

1. 1Open the Logbook website using your wallet's built-in browser (not Safari or Chrome)
2. 2Most wallets have a "Browser" or "Explore" tab where you can enter the URL
3. 3Connect as usual — the wallet will detect the connection request automatically

Popular mobile wallets with built-in browsers: Slush, Phantom, OKX Wallet.

#Signing to Read Private Data

Private campaigns keep their content and answers encrypted. Private groups do the same with their name, description and card form, and every group with its member cards, the texts of applications and the admins' copy of a list. To decrypt them, your browser has to prove your address to the Seal key servers by signing a short message. This is not a transaction and costs nothing.

• Google users: the message is signed automatically in the background
• Wallet users: your wallet shows a "sign message" request the first time you open private data; the signature stays valid for 15 minutes

Each key server therefore sees which address asks for which key, when and from which IP address: who opens which campaign or group, and who reads whose member card. What the operators of the key servers keep is their policy.

#Your Address in Groups

A membership belongs to an address, like a response. Join a group and respond to its campaigns with the same account: the Google account or the wallet you joined with. Another account is another address and is not a member.

The Account page has two tabs for groups. My data shows the member cards your groups hold. Checks shows the email checks of your address, one per community, with the day each runs out and a Renew button. An email check holds for 90 days; renewing is signing in with Google again, with the same mailbox. Where the email check is not switched on for the site, the tab says so and offers nothing to press. The World ID check is not built (see Who Counts Once).

#AI Agents Acting as Your Account

An AI agent can act as your Logbook account for a limited time. Nothing of your Google password or your web session is shared: the agent receives a time-limited proof that only works together with a temporary key. There are two kinds of sessions, and they differ in where that key lives.

• Local agent (Claude Code, Claude Desktop, Cursor, your own agent): the agent opens a consent page on Logbook, you sign in with Google, and the proof goes to a listener on your own computer (127.0.0.1). The key never leaves your machine, so Logbook cannot act as you and cannot revoke the session either. It lasts 2 days by default (7 at most); signing the agent out deletes the key.
• Connected app (claude.ai and other chats with connectors): the app sends you to Logbook's consent page. With "Continue with Google", Logbook keeps the session key on its servers, encrypted, so the app can act as you without anything installed. Unlike with a local agent, private campaigns and answers your account may read are decrypted on Logbook's edge servers when the app asks for them. The session lasts at most 7 days and ends when its proof expires; you can end it at any moment under Connected apps on your account page (Settings), by disconnecting the app, or by asking it to sign out of Logbook. "Continue without an account" connects the app read-only.

In both cases the consent page names the app, says what it will be able to do and for how long. Only approve a sign-in you started yourself. Campaigns the agent creates are yours, and its response counts as your one response. The same holds for groups: a group the agent creates is yours, and when it joins a group, applies to one or answers a campaign for the members of your groups, it does so as you. Joining and membership are public and permanent, so the agent is told to ask you first, as it is for a response.

#Logging Out

To disconnect, click on your address in the header and select "Disconnect". This ends your web session only: agent sessions are ended separately, as described above. Signing out also removes what this browser kept for your session: the stored campaign passwords and keys, and the AI assistant's conversation (see Data Storage). It removes what the browser kept for you about groups as well: the draft of your member card, and for an admin the invitation links made in this browser and the encrypted copy of a list. Copy an invitation link you still need before you sign out: the chain keeps only its public half.