AI agents: Logbook can be used programmatically. Start at https://logbook.zone/llms.txt. Remote MCP server: https://logbook.zone/mcp. Read-only REST API: https://logbook.zone/api/v1. Local MCP server: npx -y @logbookprotocol/mcp.

Logbook Beta on Sui Testnet. Learn more →
Documentation

Learn Logbook

Everything you need to create blockchain-verified surveys, understand the technology, and get the most out of Logbook.

DocsBeta Testing
5 min read

Beta Testing

Logbook is currently in public beta. We appreciate your help in testing the platform and improving it before the mainnet launch.

#What Beta Means

During the beta phase:

  • Testnet environment: All campaigns and data are stored on Sui Testnet, which is periodically reset by the Sui Foundation. Your campaigns and responses may be deleted without notice during these resets.
  • Smart contract updates: The contract is upgradeable during the beta, and Logbook holds the key that upgrades it. An upgrade keeps existing campaigns; when it raises the contract version, the functions of the previous version stop working. A fresh deployment of the contract starts with an empty history in the interface: earlier campaigns and groups stay on-chain but are no longer shown. This has happened twice: after the security review of September 2026, and on 7 October 2026, when campaigns and groups were published together as a new package (see Smart Contract).
  • Free transactions: If you sign in with Google, Logbook pays the gas fees for you, within daily limits per account and per IP address. If you use a crypto wallet, you pay gas yourself with test SUI, which is free: use the "Get test SUI" button on the Account page. Group actions follow the same rule, with daily limits of their own (see Who Pays in Groups).
  • Experimental features: Some features may be incomplete, change significantly, or be removed based on user feedback.
  • Free AI features: All AI-powered features are completely free during beta. This includes the AI Campaign Assistant for creating campaigns through natural conversation and AI Analytics for getting intelligent insights from campaign responses.
  • Terms and privacy: The Terms & Privacy page puts the essentials on one page: what a beta on Testnet means, what is permanent, who can read what, and what is stored where.

#How You Can Help

We'd love for you to try out the core features and share your experience:

  1. 1Create a campaign — Set up a poll or survey on any topic you like
  2. 2Share it with friends — Send the link to a few people and ask them to participate
  3. 3Respond to a friend's campaign — Experience the participant flow firsthand
  4. 4Try different question types — Single choice, multiple choice, and text answers
  5. 5Test private campaigns — Try a password link, an address list, or answers that only voters or only you can read
  6. 6Attach a document — Vote on a text whose hash is fixed on-chain, then check a copy on the verification page
  7. 7Publish a results certificate — After the campaign ends, issue the certificate and open its verification link
  8. 8Connect an AI agent — Add https://logbook.zone/mcp as a connector in claude.ai, or ask any chat to prepare a draft link (see API & SDK)
  9. 9Create a group — Invite a few people, then create a campaign for "Members of a group" (see Groups)
The more you explore, the more feedback you can provide — and the better Logbook becomes for everyone.

#Known Limitations

  • Data persistence is not guaranteed until mainnet launch; files on Walrus testnet are kept for at least 50 days (their hashes stay on-chain, so a copy remains verifiable until a Testnet reset)
  • Groups: the World ID check is not built, so "one response per person" cannot be chosen. The email check ("one response per mailbox", and joining with an organisation mailbox) runs on a Logbook site only once its owner has switched it on; until then the forms show it as not available yet. A seat on a list works everywhere (see Who Counts Once)
  • Groups: the SDK client (LogbookClient) and the MCP tools create, join and leave groups, handle applications and invitations and answer campaigns for the members of groups, but not everything: transferring a group, appointing and removing admins, the tree of groups, a list of seats, the settings of a group, archiving and deleting are done on the site (see API & SDK)
  • Some UI elements may not render correctly on all devices
  • Performance may vary during high-load periods
  • Documentation may not fully reflect current functionality as features are actively being developed

#Reporting Issues

Found a bug? Have a suggestion? We want to hear from you!

When reporting issues, please include:
  • What you were trying to do
  • What happened instead
  • Your browser and device type
  • Screenshots if possible
  • Your wallet address (optional, but helps with debugging)

#Already Here

Things that were on the roadmap and are now live on testnet:

  • Decentralized storage: AI reports, results certificates and campaign documents are stored on Walrus, with their hashes on-chain (see Data Storage)
  • Access for developers and agents: a read-only REST API, the TypeScript SDK, and MCP for AI agents — remote connector, local server and draft links (see API & SDK)
  • Documents to vote on: attach the text a campaign is about; it cannot be swapped once the first response is in
  • Groups: lasting lists of people for campaigns, with subgroups, member cards, lists of seats and campaigns for their members (see Groups)

#What's Coming

After beta:

  • Migration to Sui Mainnet with persistent data, and a clear answer to who pays for storage and gas
  • Additional question types
  • Mobile app

#Thank You

Your participation in the beta helps us build a better product. Every bug report, feature suggestion, and piece of feedback makes Logbook more reliable and useful for everyone.