Demo Preparation and Demo Video Guidelines
Guidelines for live demos and recorded demo videos at ACM PQQS 2026.
Authors of accepted Demo Papers at ACM PQQS 2026 should prepare a live demonstration of their work and a short recorded demo video. The demonstration should focus on showing the system, tool, prototype, implementation, or experimental capability described in the accepted paper.
For camera-ready upload requirements (video and optional poster files), see the Camera-Ready Instructions.
1. Live Demo Preparation
Demo Content
The demonstration should clearly communicate:
- Problem: What problem does the system address?
- Solution: What system, tool, prototype, or technique was developed?
- Operation: How does it work in practice?
- Key capabilities: What are the most important features?
- Results: What does the demonstration show?
- Relevance: How does the work contribute to post-quantum or quantum-based security?
Authors should emphasize the working system and demonstration rather than giving a conventional paper presentation.
Prepare a Reliable Demo
Before the conference:
- Test the complete demonstration from beginning to end.
- Prepare all software, datasets, configurations, cryptographic keys/test credentials, and other required resources in advance.
- Verify that required software and dependencies work on the demonstration machine.
- Minimize reliance on external services or network connectivity where possible.
- If Internet access is required, prepare a reasonable offline or prerecorded fallback.
- Use only test/synthetic data, credentials, keys, and accounts appropriate for public demonstration.
- Do not expose confidential information, production credentials, private keys, personal data, or other sensitive material.
Keep the Demo Focused
Design the live demonstration so that attendees can understand the core idea within a few minutes. A useful flow is: Problem → System/Architecture → Live Operation → Key Result → Security Significance
Authors should be prepared to repeat the demonstration for different attendees during the demo session.
Equipment
A table/space may be provided for demos, and power strips will be provided. Presenters need to bring their laptop or other equipment required to run the demonstration, including as applicable:
- Laptop(s)
- Power adapters/chargers
- Required cables and adapters
- Mobile/IoT/embedded devices
- Hardware security or cryptographic devices
- Other specialized equipment required by the demonstration
Any unusual requirements for power, networking, display equipment, physical space, or other infrastructure should be communicated to the PQQS 2026 organizers in advance.
Demo Video Recording Guidelines
Authors of accepted Demo Papers should also prepare a short video demonstrating the accepted work.
2. Recommended Video Structure
The video should primarily demonstrate the system rather than reproduce the paper presentation.
A recommended structure is:
- Title and Introduction — Show the demo title, authors, and affiliations and briefly introduce the problem.
- System Overview — Briefly explain the system architecture, setup, or workflow needed to understand the demonstration.
- Actual Demonstration — Show the system operating. Walk through the important functionality and explain what the viewer is seeing.
- Results / Key Takeaway — Highlight the most important result, capability, or security benefit demonstrated.
- Conclusion — Briefly summarize the contribution and its relevance to PQQS.
The actual demonstration should constitute the majority of the video.
3. Video Length and Format
- Keep the video concise and focused.
- Recommended duration: 3–5 minutes.
- Accepted formats: MP4 (H.264) or WebM, with file size < 600MB.
- Avoid spending substantial time on background material that is already available in the paper.
4. Recording Quality
For good viewing quality:
- Record at 1080p (1920 × 1080) where possible.
- Use a 16:9 landscape format.
- Ensure that screen text, terminal output, diagrams, and application interfaces are readable.
- Use clear audio with minimal background noise.
- Use screen recording rather than recording a computer monitor with a phone/camera whenever practical.
- Zoom or enlarge terminal/interface text when necessary.
- Avoid rapid mouse movements or excessively fast transitions.
- Use captions/subtitles where practical to improve accessibility.
- For demonstrations involving physical hardware, ensure that the camera clearly shows the relevant device and its operation.
5. Security and Privacy Check
Before recording and submitting the video, carefully review it for accidentally exposed information.
The video must not reveal:
- Passwords or authentication credentials
- Private cryptographic keys
- API keys or access tokens
- Confidential or proprietary information not intended for publication
- Personal or sensitive information
- Internal network addresses or infrastructure details that should not be public
- Unrelated information visible in terminals, browser tabs, notifications, or the desktop
Use test environments and synthetic/test credentials whenever possible.
6. Final Video Check
Before submission, play the entire video from beginning to end and verify that:
- The correct title, authors, and affiliations are shown.
- The demonstration is understandable without additional explanation.
- The important functionality is clearly visible.
- Screen text is readable.
- Audio is clear and synchronized.
- No sensitive information is visible.
- The video plays correctly from beginning to end.
- The video satisfies the specified duration and format requirements.
7. Live Demo Backup
- Authors are strongly encouraged to keep the final demo video available during the conference as a backup for the live demonstration. If an unexpected hardware, software, connectivity, or environmental problem prevents part of the live system from operating, the recorded video can be used to help demonstrate the intended functionality.
- The recorded video should complement the live demonstration rather than replace it, unless otherwise instructed by the PQQS 2026 organizers.
Contact
For questions, please contact the Program Chairs at pqqs26-pcchairs@acm.org.