You're testing 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.

DocsViewing Results
5 min read

Viewing Campaign Results

See how responses are aggregated and displayed.

#Results Tab

Every campaign has a Results tab showing aggregated data:

#For Choice Questions

  • Vote counts: How many people selected each option
  • Percentages: What proportion chose each answer
  • Visual bars: Graphical representation of distribution

#For Text Questions

  • Response count: Total number of text responses
  • Response list: Individual text answers (click to expand)

#Response Details

The Responses tab is visible to everyone and shows:

  • Timestamps: When each response was submitted
  • Respondent addresses: Blockchain address of each participant
  • Transaction IDs: Links to verify on block explorer

#Real-Time Updates

Results of active campaigns refresh automatically:

  • The page re-reads the blockchain at a regular interval (you can change it in the settings)
  • Vote counts and charts update without a page reload
  • Use the refresh button next to "Updated" to reload immediately

#Results of Private Campaigns

When answers are not visible to everyone, they are stored encrypted and the results are tallied in your browser from the answers you are allowed to decrypt:

  • Everyone with access: open the campaign with the password or an allowlisted address and you see everything
  • Voters only: results appear after you have responded
  • Only creator: the creator sees everything; participants see only their own answer
  • After the end date: until the campaign ends you see only your own answer; afterwards everyone with access sees all results
If you are not signed in, or your wallet has not signed the decryption request yet, the Results tab shows a banner with a "Sign in" or "Sign & decrypt" button.

#On-Chain Verification

Every response can be verified independently:

  1. 1Note the transaction ID from the response
  2. 2Visit a Sui block explorer (like Suiscan)
  3. 3Search for the transaction ID
  4. 4View the complete transaction details
This proves:
  • The response was actually submitted
  • The exact timestamp of submission
  • The blockchain address that submitted it
  • The transaction cannot be modified

#Campaign Lifecycle

#Active Campaigns

  • Accept new responses
  • Show live results
  • End date in the future

#Ended Campaigns

  • No longer accept responses
  • Results are final
  • Data remains permanently on-chain

#Results Certificate

The creator can issue a results certificate from the Results tab: a JSON snapshot of the questions, the tally and every response with its transaction, meant for people who do not use Logbook, such as an auditor or the minutes of a meeting.

  • The file is stored on Walrus and its SHA-256 is recorded in the campaign on-chain, so it cannot be altered afterwards without detection
  • Every line in it can be checked against the blockchain: each response lists its on-chain object and transaction
  • For private campaigns the certificate is encrypted for the same audience as the answers
  • "Issue again" replaces it, for example after the campaign has ended
  • The file is kept for at least 50 days (Testnet beta); the on-chain record is permanent, and a downloaded copy stays verifiable after that. See Data Storage
Anyone who can read the answers can download the certificate from the Results tab.

#Verifying the document that was voted on

Every document of a campaign has a "Verification link". On the verification page anyone can choose a file from their computer and see whether it is the one the campaign committed to. The file is hashed in the browser and compared with the blockchain; nothing is uploaded and no storage is involved. The page also says whether the commitment is already frozen (the campaign has responses) or could still be replaced by the creator.

For private campaigns the link carries the salt of that one document. It lets the holder verify a copy they were given; it does not open the file or the campaign.

#Verifying a certificate

Use "Copy verification link" and send the link to anyone: an auditor, a board member, a journalist. The verification page needs no account and runs every check in the visitor's browser:

  1. 1It reads the record from the Sui blockchain: which document the campaign creator committed to, and when. Only the creator's address can make that record.
  2. 2It fetches the file (Walrus, or Logbook's cache) and compares its SHA-256 with the one on-chain. A file that does not match is never shown.
  3. 3For public campaigns it goes further and recounts the listed responses from the blockchain, so an inflated tally or a dropped response is caught.
  4. 4For private campaigns the link carries the key of this one document (after the #, so it never reaches a server). The visitor decrypts the very bytes whose hash is on-chain. The key opens the certificate only, not the campaign or its answers.
  5. 5A file received by email can be dropped on the page to check that it is byte-for-byte the committed document. This works even after the file is no longer stored anywhere, because the hash it is compared with lives on-chain.
What a certificate of a private campaign proves: the creator committed to exactly these results at that time and cannot change them later. It does not let an outsider recount encrypted answers; who responded and when is public either way.

#AI Analytics

Campaign creators can use AI Analytics to get intelligent insights:

  1. 1Go to your campaign
  2. 2Click the Analytics tab
  3. 3Click Analyze Responses
The AI will analyze all responses and provide:
  • Key findings and patterns
  • Sentiment analysis for text responses
  • Actionable recommendations
Learn more in the AI Analytics documentation.

#Exporting Data

Currently, you can:

  • View all responses in the app
  • Verify individual responses on-chain
  • Copy addresses and transaction IDs
Future updates will add CSV/JSON export functionality.