What is Logbook

Logbook is a platform for surveys, polls, and voting — with results that can't be faked. Built on Sui blockchain.

#The Problem

When you create a poll in Google Forms, run a vote in Discord, or collect feedback through any traditional platform, you're asking participants to trust — a lot.

Trust that responses aren't manipulated. The person running the poll has full access to the data. They can edit responses, delete inconvenient votes, or hide results entirely. You'd never know.

Trust that results are accurate. The platform shows you a number. Maybe it's correct, maybe it isn't. You can't access the raw data to count yourself. You just have to believe what you're shown.

Trust that records will exist tomorrow. Platforms shut down. Accounts get deleted. Polls expire. Six months from now, there may be no evidence the vote ever happened — no way to reference what was decided or prove the outcome.

This isn't a hypothetical problem. It's the default. Every traditional voting tool works this way: truth is whatever the platform — or the organizer — decides to show you.

#The Solution

Logbook takes a different approach: instead of asking you to trust, it gives you the ability to verify.

Every response is recorded on the Sui blockchain — a public, decentralized ledger that no single party controls. This changes everything:

Immutable records. Once a response is submitted, it's written to the blockchain permanently. The contract has no function that edits or deletes a response: not for the organizer, not for the platform, not for us. Two limits during the beta: Logbook holds the key that can upgrade the contract (see Smart Contract), and the test network it runs on can be reset (see Beta Testing).

Public verification. Every response has a transaction hash. Anyone can look it up on a Sui block explorer such as Suiscan and verify it exists. You don't have to trust the results we show you — you can check them yourself.

Permanent storage. Blockchain data doesn't expire when a subscription lapses or a company shuts down. As long as the Sui network exists, your records exist. Reference them years later as proof of what was decided. (During the beta Logbook runs on Sui Testnet, which can be reset: see Beta Testing.)

No central authority. There's no admin who can quietly change the rules mid-vote. The rules live in a smart contract — code that executes exactly as written, every time. Once the first response arrives, the questions can no longer be changed or deleted. One caveat during the beta: Logbook holds the key that can upgrade the contract. An upgrade is a public transaction on Sui, but it could change the rules, including who may decrypt what (see Smart Contract).

Restricted when it needs to be. Not every vote should be open to all. Campaigns can be limited to people with a password, to a list of addresses or to the members of a group, and answers can be readable by everyone, by everyone with access, only by voters, only by the creator, or by nobody until the vote ends and by everyone with access from then on. In every one of these the readers see each answer next to the address that gave it: none of them is anonymous, and none is a secret ballot. Restricted data is encrypted in the browser, and the smart contract checks the password or the list and decides who gets the decryption keys. Logbook's servers do not hold those keys, with one exception: for an app you connect through the remote MCP connector they hold that session's signing key, encrypted, and decrypt what the app reads. Logbook does hold the key that can upgrade the contract (the caveat above). See Privacy.

The result: a voting tool where trust is optional. Everything that matters is verifiable.

#Groups

People who decide together more than once can form a group: a house council, an organisation with its departments, a club. People join once, and every campaign for the group counts the members it had at the moment the campaign was created. Nobody can add or remove participants of a running campaign for a group. A campaign for a list of addresses is different: its creator can change the list at any time, also while it runs. See Groups.

#Use Cases

Community voting: Transparent governance decisions
Research surveys: Collect feedback with provable authenticity
Event registration: Immutable attendance records
Polls and opinions: Public sentiment with verifiable results
House councils and organisations: A group with a list of seats, one response per flat or per member
Votes whose interim result stays hidden: answers are sealed until the vote ends, then everyone with access reads them, each next to its address (this is not a secret ballot)
Feedback only the organizer reads: the organizer reads every answer next to the address that gave it (this is not anonymous)
Certification: Issue verifiable credentials and test results

#Works With AI Agents

Creating campaigns, responding and reading results can be done by an AI agent on your behalf: through a connector in claude.ai or another chat, through a local MCP server, or simply through a link the agent prepares and you approve in the browser. See API & SDK for the three ways and how they differ. An agent can also create a group, join one, apply, make an invitation link, decide applications and answer a campaign for the members of your groups; the rest of managing a group (its admins, its settings, a list of seats) is done on the site.